Why research labs fail at innovation

Research labs are an old idea. Edison’s Menlo park lab in the 1870s had most of the elements innovation labs and R&D groups try to emulate today. But that doesn’t stop companies today from starting from scratch, assuming they’re the first to try. In researching the book the Myths of Innovation I studied how research labs in established companies work, and why they fail.

Here’s why in simple terms:

  • Ideas are easy. It’s not hard to find interesting ideas. They’re everywhere. Many corporate R&D (research and development) groups and universities know how to develop an idea into a prototype. But developing a prototype into a complete, and marketable product is much harder. A research lab at a large company could discover perpetual motion and it would still be hard to get release it as a product.
  • Creating an R&D group, or Innovation Team, alienates everyone else. This is the killer – the limits of sociology kills innovation more often than the limits of technology. The jargon is technology transfer, which means “how do we get ideas from the R&D group into products?” Product teams are very busy with their own projects and have little natural interest in wanting to follow someone else’s plans. R&D, by design, sets goals unapproachable for product team’s 3/6/12 month horizons and wonder why they’re ignored 90% of the time, while product teams look at R&D and think they’re insane (10 year horizons? Will we be alive then?). Managers love to couch this problem with jargon like “innovation pipelines” and “invention waves” but they’re missing the real challenge – they don’t see the problem as sociology. R&D groups and product teams naturally resent each other, primarily because the leaders of each group have very different belief systems about what is valuable. Until those issues are addressed little else matters: great ideas will go nowhere.
  • R&D never has a service arm. One obvious way to build camaraderie with product teams is to dedicate 10% of R&D as a service to Product team engineers. What problems are too big for release schedules, but too tactical for typical R&D ambitions? That’s the sweet spot where technology transfer starts and grass roots level bonds can be made. Any R&D manager who invests in closing the culture gap buys trust that will help when R&D has a breakthrough idea that ordinarily would scare product teams. The problem is that R&D ego would see this role as a concession to product team “superiority”, which is why its never been done.
  • The politics are broken. Conflicts start at the VP level. R&D is directed at satisfying VPs, and R&D managers bet that when they deliver a great innovation the VP, or CEO, will do the radical shift from old ideas to new ones. There are often big egos at work in anyone interested in leading an innovation lab and the hubris is hard to hide. They underestimate how hard politically these moves are and how rarely they happen. VPs may have the most power but often that means they are least likely to adopt change since they have the most to lose (it’s likely rising middle managers on product teams that are at the leverage point of power, ambition and risk taking, not their boss).
  • Everyone wants to feel creative. Would you want to be told to only work on other people’s ideas? Any R&D group faces the challenge of being in the ivory tower: they’re resented as soon as they walk in the door, especially if they throw their PhD’s and research pedigrees around at engineers with different values. Innovation is a social process that smart motivated people want to participate in – if you propagate the belief that only special people in special roles can do it, something is broken (see questioning VPs of Innovation).
  • At the end of the day someone has to make the bet. Good R&D minimizes risk but never eliminates it. It produces explorations and potentials, but someone has to say “I’m betting my successful and profitable division on new thing X”. That’s a hard thing to say: I’ve never said it, have you? Most R&D managers despite their confidence have never said it either and part of why they’re “in research” is their lack of aptitude or interest in business thinking. In the end every failed R&D effort has a Product VP, or CEO, who was unwilling to take the risk, either for good reasons (the ideas were not worthy) or bad (they didn’t believe or didn’t have the the courage). No one likes to risk their career based on someone else’s bet.

References:

  • This Booz-Allen report evaluates R&D spending and supports the notion that pure R&D matters less, in a business context, than transfer.
  • Mark Stefik’s book Breakthrough: Stories and Strategies of Radical Innovation was the best R&D management book I found. It’s interview-centric to a fault and not the typical list of do’s and don’ts found in most management books – it attempts to provide a framework for how leaders of R&D should think about innovation with many supporting stories.
  • There is a shortage of good books on managing R&D – trade secrets or unwillingness to write about failure? Who knows. The closest thing to a recommended reference I found was The human side of managing technological research edited by Ralph Katz, a collection of papers that covers performance, process, invention and human nature.
  • book-myths_of_innovation-280wThe primary reason research labs fail is that successful innovation depends on variables beyond our control – you can do everything right and still not deliver the breakthrough everyone expects – a theme explored in depth in the Myths of Innovation.

 

I will write you an essay – for free!

Confession: I am in serious essay debt and I need your help to get out.

The story: I made a commitment when I quit MSFT in 2003 to publish an essay a month on the website. That’s 12 a year. Here are my stats:

2006: 5 (!)
2005: 12
2004: 10

So I owe the universe or myself (whomever cares more), 9 essays. That’s right. Not to mention the 3 so far this year that haven’t materialized yet.

I have plenty of ideas, but I’m bored with my ideas. I want yours. That way I’m guaranteed at least one person other than myself will give a shit when I post the thing.

So here’s your chance: If you could rent my brain to write something, what would the title of the essay be? What topic do you think I’m chicken to write about? What mean scary question do you want me to answer?

Lets get it on!

Why you should treat contractors / temps well

One habit many managers have is to dump the boring, unpleasant work of their team onto contract workers. The thinking is that full timers deserve the best treatment and contractors are mercenaries: they deserve whatever they get since they won’t be around long.

It’s a mistake – good managers finds a way to treat everyone well. And there are some reasons contractors deserve special attention:

Here are three reasons why:

  1. Contracts are scouting missions. Smart companies hire interns since they know the one in five chance of finding a future employee are worth all the overhead. It costs an amazing amount of energy to hire a good employee. Any contractor you hire should be thought of as a potential full time employee – possibly not even for the skill they’re contracting for. If you treat them like idiots in a box,  you’ll get idiots in a box. But give them a chance to outperform your expectations and your next star recruit might already be in your office. Sure this is uncommon, but it costs you nothing – tell them if they exceed your expectations you’ll consider, or refer, them for hire and see what happens.
  2. Contract hires create your network. While you’re climbing the corporate ladder, every contractor has a long sequence of future companies and bosses ahead of them. What stories of you will they tell? If you ping them in 6 months about job openings on your team, will they recommend you to their peers in their new company? Contractors are true worker bees. They fly from place to place spreading reputations – will they be your ambassador or detractor?
  3. They bring new ideas. Forget what job you hired them for – they bring experience your team might not have, and exposure to ideas new to you. If you constantly push their heads down into the pidgeon hole, never letting them advise  based on their unique perspective, you’re cutting yourself off from potential knowledge. Give them a voice – it costs nothing. If the three times they speak up with recommendations they sound insane, ask them to stop. But if you get some good ideas and reward them, they’ll be happy and so will you.

I’ve seen dozens of smart people sequestered away in the worst offices, never asked for an opinion and given no opportunity to shine, simply because they wore the label “contractor” – what a waste for everyone. Some contractors run circles around their FT counterparts – in fact that’s why they’re contractors: they’re good enough to make a living freelancing and taking part of the year off something many full-timers (FT) don’t have the talent, or the guts, to do.

The fear managers have is that treating contractors the same as employees raises legal issues, or threatens the full timers, but that’s nonsense – you don’t have to treat them the same in order to treat them both well. And if your team is threatened by talent, you’re in trouble for different reasons.

Bay area/Seattle book tour: venues wanted!

The Myths of innovation book is wrapping up fast and it’s time to put together another crazy kick-ass no-frills book tour.

Stop 1: I’m planning to hit the bay-area for a few days in mid-May. For the last tour I spoke at Google, Yahoo, Adobe, Sun, Macromedia & Baychi. Do you have a venue and want me to come by? Now is the time to let me know.

Stop 2: I’ll also be doing local (Seattle) talks where-ever I can around the same time.

I can’t promise to stop everywhere, but if you can get a good, fun, (and hopefully book-purchasing minded) crowd together, I’ll definitely consider it.

Patents 2.0? Public patent review

Most people I respect have little respect for software patents – they’ve either read one, have their name on some, or have paid attention to who is most served by their creation (IBM has more patents in it’s name for each of the last 14 years). In all my research for the book I found little hope that the patent office was due for reform, especially for software, and had little hope for change.

So I was stunned when I read that the U.S. Patent office is piloting a new process for patents.

The news so far is thin and I can’t find official comments yet (couldn’t find a thing on the USPTO site):

Washington Post
ZDNET
Interview w/Jon Dudas from USPTO

(Note: Dudas’ full job title is the Under Secretary of Commerce for Intellectual Property and Director of the United States Patent and Trademark Office – his business cards must be 8×11).

How to start meetings on time (the honest answer)

Starting and stopping on time is easy. One person with power simply has to decide to care, the rest follows.

Having recently survived a tragicomic 8 way international conference call, an experience worthy of the 4th level of hell, I’m here to offer 5 honest tips that would have saved the day:

      • If you called the meeting, do your %*?@?! job. Everyone claims they know about facilitation, but few do it. If you called the meeting, it’s your job to 1) get there on time 2) write a bullet list agenda on the wall 3) Manage the conversation so no one hogs the floor and the right people get a voice at the right time 4) make sure side issues get delegated out of the room. If you don’t do all 4, any meeting problems are your fault.
      • Meetings start when royalty arrives. Watch the behavior of the senior person on a team. Most meetings won’t start until they arrive and people know it. If the VP is never late, no one else will be either. If the VP is always 10 minutes behind, everyone else will follow. If you’re a team manager, and meetings always start late, know (and blame) thyself. If you need a VP/VIP find out what they’re doing before your meeting if you can.
      • Someone must enforce the clock. Every meeting should start with someone assigned to watch the clock. I don’t know that you need a giant clock like Google is claimed to use, but it’s someones job to say “We’re 20 minutes in”, “we have 15 minutes left”, “we have 5 minutes, so lets wrap up”. You’d be amazed how many meetings ramble for half the allotted time on topics not central to the reason for the meeting. Three breakpoints are all you need to remind everyone to stay on track.
      • Plan to end 5 minutes early. It’s insane but in all our infinite wisdom we continually plan meetings back to back with zero alloted time to get from meeting A to meeting B. Whose idea was this? If you always go to the last second, or go over, guess what you’re doing? You’re screwing over the next batch of meetings people need to get to. You’ll make unexpected friends by always ending early, which is easy if you watch the clock.
      • Only have meetings that matter . If you had a meeting called “Lets discuss how awesome you are and how we can triple your salary” people will arrive right on time – the concept of a meeting isn’t bad, it’s what you fill it with that matters. If everyone is always late they’re telling you: this meeting is not important. Either learn how to make the meeting worthy of their time or don’t have the meeting. Ask for opinions at perennially late or poorly attended meetings: why does this meeting suck? How can this be more useful? Is there a better way to |insert why you think you need a meeting here|?

Also see, The 22 Minute Meeting.

How to kill innovation hype

You know a big word is in trouble when it’s used repeatedly (inconcievable!) – it means the person saying it doesn’t know what it means or isn’t saying anything at all.

In a recent Ford TV ad, the word innovation is used once every 8 seconds, a sure sign that the i-word has seen better days.

Today the word innovation is a common placeholder – Instead of saying “we are smart”, “we are good” or “we are willing to try new ideas”, messages that can be examined for truth, the word innovation is thrown down ambiguously, as if it were a replacement for having a message, or stating one clearly.

The goal of my upcoming  bestselling book, The Myths of Innovation is to bring honor back to the word by exploring the history of true innovations, and demystifying the breakthroughs of the past and the present.

Along the way I’ve learned some easy ways to diminish innovation hype:

  1. Challenge the word. Never allow the word to be used in conversation without asking “what do you mean by innovation?”. If it’s not clear to you as a listener how the word is being used, the speaker probably doesn’t know either: call them on it.
  2. Pick your meaning. Innovation is frequently used to mean one of: something new, something better, something new and better, or something that will win. If that’s what you mean, say that instead. If you’re not sure what you mean, say that, or just keep quiet.
  3. Avoid compound usage. As soon as you’re throwing hyphens around you know you’re in trouble. Innovation is a strong enough word to stand alone. Replace incremental Innovation, with improvement. Disruptive innovation with big change. Never have a slide or diagram that depends on multiple uses, with different meanings, of the same word (tip: you can use the words incremental and disruptive on their own – they’re grown up words too).
  4. Remember Edison. Most great innovations took place before there were business books on the subject. Edison didn’t need an innovation pipeline or an innovation infrastructure to invent the phonograph or perfect electric lights, and you don’t either. Somehow Da-Vinci, Tesla, and Picasso innovated without using the word: you and your company can too. Edison laughed at the hype-mongers, cursing rule makers and secret seekers, preferring to work hard at creating things rather than just talking about it.
  5. Competence trumps innovation. If you suck at what you do, being innovative will not help you. I don’t care how innovative Burger King might be, their food sucks. Business is driven by providing value to customers and often that can be done without innovation: make a good and needed thing, sell it at a good price, and advertise with confidence. If you can do those 3 things consistently you’ll beat most of your competitors, since they are hard to do: many industries have market leaders that fail this criteria. If you need innovations to achieve those 3 things, great, have at it. If not, your lack of innovation isn’t your biggest problem. (See Good Beats Innovative Nearly Every Time)
  6. Call bullshit. Asking for examples kills hype dead. Just say “can you show me your latest innovation?” Most people that use the word don’t have examples – they don’t know what they’re saying and that’s why they’re addicted to the i-word. Keep pressing and most hype-philes concede what they’re doing isn’t new. The fastest way to detect BS is to look at facts and at the present. True innovators rarely need the word: they just show their work.

First interview about Myths of Innovation

I had a blast speaking at Adaptive Path’s MX conference recently about the Myths of Innovation book. I had the closing slot which can be tough, but the crowd was great and gave me a chance to have some fun (podcast of this talk is coming)

One highlight was being interviewed by Sarah Nelson, a design strategist for AP.

To give a taste, and stumble into the postmodern idiocy of quoting someone quoting me:

SN: One of the things I’ve been wondering about is the idea of “source of innovation” within a company. Do you think it’s actually possible to create an environment in which innovation occurs?

SB: I think that you can create an environment, and it’s very simple… whoever has power over a budget, and whoever has power over what features are included in a product or go up on the website, they enable innovation by saying “yes.” That’s really the fundamental thing that they have to be willing to do.

When someone shows up with an idea — “Hey, why don’t we change the navigation system from this older design to this new design I’ve been thinking of? Can I get some money to go and prototype this?”

All that has to happen is the person with power says, “Yes, I will give you a week to go and prototype that and we will review it when you have the prototype, and then we’ll consider actually making those changes.” And once everyone witnesses the person in power saying “yes” to a new idea, then they’ll be comfortable bringing another idea, or a third idea. And then all of a sudden, you have an environment that is very receptive to new ideas and innovations.

Sounds obvious, but as I explain in the book these environments are rare.

Link to the full expletive free interview.

Do headlines make us dumber?

In the parade of mis-represented research that is modern journalism, we have this short article from MSNBC, titled “Do meetings make us dumber?“.

The article starts with:

People have a harder time coming up with alternative solutions to a problem when they are part of a group, new research suggests.

Which people are these exactly? Articles, and research, treat people as uniform, while we all know the goodness or badness of meetings depends on who is there. If you had a conference call with Bono, Einstein, Dostoevsky, and Susan Sontag, I guarantee the meeting wouldn’t make you dumber.

While folks of their caliber aren’t clambering to join our meetings, it does stand that who controls the invite list holds the fate of the meeting in their hands.

And doesn’t the goal of a meeting impact the quality of what happens? As the articles states:

Scientists exposed study participants to one brand of soft drink then asked them to think of alternative brands. Alone, they came up with significantly more products than when they were grouped with two others.

Wow. I can’t think of a task more inspiring for creative thinking than listing brands of soda, can you? Isn’t that what Mozart, Walt Whitman and the Beatles did?

How can anyone think this is representative of what goes in in “creative” meetings, or is a viable, as science, to use in comparison to how people make decisions, or work in groups, in real life?

Two points of refutation:

  1. The value of meetings hinges on who is running the thing. A good facilitator can convert most meeting horror shows into productive and near-fun experiences if given the power to do their thing.
  2. There are well known techniques for creative thinking and tactics any meeting leader can use to minimize the negative effects of groups, while amplifying the positive ones. Good facilitators know these things.

The notion of group behavior harming creative thinking has a long history – the term groupthink coined in 1972, and it offers a more useful analysis that the MSNBC or the research study.

For reference:

How to run a brainstorming meeting

(Link from Flee)

Research help: how many species have there been?

As proofreading goes on chapter by chapter, I get my last chance to review references and properly site cite sources. It’s slow, tedious, and so little fun, I thought I’d throw some of it at you.

The question: How many species in the history of the planet have gone extinct?

The web has been surprisingly stingy. The wikipedia entry for extinction pointed me back at mediocre sources I already had.

Obviously I don’t need hard data as there isn’t much: but a ripe quote from an expert, or a summary of expert opinions would be perfect.

The prize: find me a reference that I’m willing to use in the book, and I’ll put your name in the book’s acknowledgments.

Seattle: Ignite, Tuesday 8:30pm

The best new tech sector event in Seattle is the Ignite series Brady Forest started a few months ago. It’s an open submission series of 5 minute talks, and it’s fun. The fact that it takes place in a bar on capital hill doesn’t hurt, and if you can get there early you can take part in a fun Make magazine competition (think flying eggs) run by Bre Petis.

Details, directions and agenda here.  Unless you have plans, go.

 

The life of a book: part 2

Months ago I described my experiences with book sales called the life of a book. Almost a year has gone by since then: time for an update for those curious about what it’s like on this side of the book.

Here are 12 months of amazon rankings for artofpm (courtesy of rankforest):

2907thumb.jpg
The bad news:

  • Essays proved to be good traffic and sales spikes, but I’ve only written 3 essays since last April. My goal is one a month, so I’m in essay debt. Book writing drains my interest in longer pieces – I can do the blog thing w/a book in progress, but essays are harder to motivate.
  • I’ve struggled to balance book writing, blog posting, and essay writing. If you have any self-discipline pills, please send.

The good news:

  • Blog traffic has been on a steady climb. But correlation to sales data is harder to prove.
  • Amazon sales spiked for 6 weeks, from 12/15-1/30.
  • Artofpm returned to O’Reilly’s best seller list two weeks ago at #21, which is unusual for a book two years old.

Analysis:

  • The sales spike is hard to explain: project management seems an unlikely holiday gift. (Here honey -Have fun!)
  • My consulting and public speaking activities have been steady: I can’t correlate sales with those activities.
  • The spike lasted about 6 weeks, but now has trailed off, with amazon rankings around 7000.

What does all this mean? I don’t know. I though writing this post would help sort it all out: but there’s no easy explanation.

Thanks are due to anyone out there who has recommended the book to others. At this point the book is on its own, and its continued success comes from people telling others about it: so thank you.

The continued sales makes it easier for me to write more online, and defend the time for more books. I can’t tell you how much I’ve appreciated the support. Hope y’all like the myths of innovation book when it’s out: I think you will :)

If you have questions about life on this end of the book, fire away.

The book: the myths of innovation

If you’ve been reading here for awhile you know I have some questions about innovation history. Well the book I’ve been working on for the last two years has some answers.

The book is called The myths of innovation and it has 3 goals:

1) Identify the myths we have about new ideas and innovation
2) Explore why they’re popular and how they came to be
3) Use lessons from history to replace myths with knowledge

I’m taking big swings in this book: I take on meaty concepts like creativity, revolution, history and progress, telling great stories from innovations past, while delivering advice at a fast pace. It’s a shorter book than artofpm but the challenge to readers, and the value, is much greater. (But what do I know – I’m just the writer).

Over the next few weeks leading up to the book’s April release (date tba) (book is out now and a bestseller)  I’ll dig in on some of these themes, shed light on the myths, and give you a preview of what’s to come. A book tour like last time (west coast and east) is in the works, and I’ll post more details as I have them.

Thanks to all of you who have commented here along the way: Its made a difference and I’m grateful.

Footnotes vs. Endnotes: the debate

One of the little details authors fret about is footnotes vs. endnotes. It’s a style choice: should you keep a slot at the bottom of every page for notes, or collect them all at the end of the book (or chapter)? A quick survey of 10 books from the library shows:

Endnotes: 4
Footnotes: 4
No notes(!): 2

Sure, its fair to say who cares – what is in the notes matters more than where they are, but still. Don’t you have an opinion? Many folks do and get quite passionate about it. Here are the main arguments:

Footnotes. The pros: You can quickly check the note without leaving the page, and the author can stuff funny things in there. The cons: it’s distracting if there are lots of notes and can be visually ugly.

End-notes: The pros: Saves research questions to the end and keeps pages clean. Cons: the footnotes are rarely read and if they are, it’s hard to know what the author is referring to. You also have to jump back and guess where the note came from.

I ask because my book is at that stage. If you have any bright ideas, or entertaining rants, I’d love to hear them now.

Update: Decision was made and you can read about it here.

Book review: Founders at Work

Founders at workatwork is a collection of interviews with, surprise, founders of tech-sector companies. The goal is to capture their recollections of the early days of their successful ventures, and share stories that were often overlooked.

The interview list is first rate: founders from Hotmail, Adobe, Excite, Firefox, Yahoo! and more than 20 other well known companies are included.

The upside is that these stories read honest: there’s struggle, failure, fear, mis-steps and changes of direction, all the things often glossed over by high level mainstream interviews of success stories. If you’ve wished you could have a chat with some of these folks, you’ll be happy with this book. Livingston does a good job of staying out of the way and tries to cover similar territory with each interview (however it has the minor effect of making the book more readable in separate sitings, as the repetition of questions tires after 5 interviews in a row).

The other risk for those with dreams of entrepreneurship is that the stories come across as ordinary: there are few magic moments, radical breakthroughs, or amazing coincidences: its mostly hard work, and fantasies of what starting a company is like will fade by the 8th interview.

This book is inspiring at times: mostly because it makes the stories of these startups real. These were human beings doing these things, not omnipotent geniuses. Anyone expecting triumphant, and replicable, vision for why these folks succeed will be forced to look elsewhere, or perhaps more to the value of this book, reconsider what it takes to found a successful company.

Buy Founders At Work at Amazon.com.

The author, Jessica Livingston, is a partner at Y Combinator, a venture firm for early startups with some novel ideas on what venture firms should do.

Difference making: darfurwall.org

darfur.jpgI recently met Jonah Burke, one of the directors of the darfur foundation, to chat about innovation. I came across his project, darfurwall.org, at Ignite Seattle, a local tech-sector meetup.

Months ago I wrote a preechy essay about difference making: well, here’s an example of someone doing the real thing.

Not only is darfurwall.org a clever piece of design and engineering, it serves a purpose: all the money people chip in for lighting up the digital wall goes straight to helping people in need. Like a physical monument, it gives a sense of both the impact of what has happened, but also offers a way to participate. Check it out.

Book review: Designing Interactions

Disclaimer: I met Bill Moggridge (the author) when he volunteered as a judge, with Brenda Laurel, and Andrew Dillon, in the CHI.

di.jpgDesigning Interactions is a book of stories. It takes the novel view that the people behind the designs can teach us more about design than the designs themselves. Although there are plenty of ID-magazine style photographs, they’re not the centerpiece: the people and their design stories are.

If you’re fond of interviews, and want to hear first person stories about how various famous designs were made, this book is for you. I’m a story guy so I was happy, finishing most of the book in one sitting (More theory-driven readers would be happier elsewhere).

The book’s content is well described on the companion website, including a chapter overview exposing an emphasis for tech-design history: From the mouse, to the PC, to PalmPilot, Moggridge starts at the beginning and works his way, one person at a time, to the Internet, gaming and the future. While there is some predictable designer-self worship, and a shortage of stories of failure, many of the stories are humbling, refreshing and inspiring.

One warning is that the book has a San Francisco & IDEO centricity: more a reflection of the author’s network than an objective history of tech-design. IDEO, which Moggridge co-founded, is mentioned often and if this annoys you either filter it out or look elsewhere.

The book is a bargain, coming in at a hefty 800 pages, many amazing color photos (including archival), and a companion DVD (although it overlaps with the published interviews). I can’t think of another book like it.

Interview list includes: Bill Atkinson • Sergey Brin • Stu Card • Gillian Crampton Smith • Jane Fulton Suri • Bill Gaver • Bing Gordon • Rob Haitani • Jeff Hawkins • Matt Hunter • David Kelley • Brenda Laurel • David Liddle • John Maeda • Tim Mott • Joy Mountford • Takeshi Natsuno • Larry Page • Mark Podlaseck • Larry Tesler • Bill Verplank • Terry Winograd • Will Wright

Sample chapter and interviews. Buy from Amazon.

A favor: helping the good guys at etoner.com

I have an unusual request: been blogging for years but this is my first personal post.

The best person I know runs a business called etoner.com. It’s a customer service centric mail-order shop, that sells printer toner, copier toner and other office supplies.

I can put my good name 100% behind him and his company because he shares that name with me: he’s my older brother.

The problem: Recently his competitors began using various search engine manipulation techniques: fake pages, link farms, link doorways, all sorts of things to deceive search engines. Its unfair and it has nothing to with the quality of the service they provide or products they sell.

The favor: If you need toner or other office supplies, give etoner.com and their prices a shot. They sell all the popular models like HP toner, Ricoh SP C410DN, Ricoh CL7200, HP P4005 and Okidata C5100, take special orders, and my brother, the owner, the main man, takes pride in dealing with customers directly. 1-800-365-5566, or go www.etoner.com.

And of course if you feel so motivated, throw a link up on your site to etoner.com out of respect for one of the good guys, a small business owner focusing on customers.