Innovation 1.0, Served Here

Riveting article on Bloomberg / Businessweek about how leaders really don’t want employees to innovate. Rather: “Businesses need most of their workers to carry out their primary duties with enthusiasm and consistency,” writes Pat Lencioni

As to how organizations should lead and execute, the article opines in two seperate areas:

“What should leaders do? Be more open to new ideas from employees? Probably not. Better yet, they should stop overhyping innovation to the masses and come to the realization that only a limited number of people in any company really needs to be innovative

As heretical as that may seem to those who want to believe that “innovation is everyone’s business,” consider that even the most innovative and creative organizations need far more people to be dutiful, enthusiastic, and consistent in their work than innovative or creative.”

If you’ve read this blog before, you’ll know that I’m all for respecting the realities of how organizations operate today and finding a more decisive and surgical approach to leveraging the benefits of open collaborative and flatter organizational structures based on performance acceleration opportunities for client organizations. So I’m not opposed to Pats overarching message that managers need to ensure focus in innovation when it comes to meeting performance goals that have been promised to shareholders.

But here’s where this thinking goes off the rails and conforms hopelessly to the status quo (or Innovation 1.0):

Innovators vs. Innovation Cultures

There’s a difference. By organizations embracing and encouraging innovation, that really doesn’t equate to every factory worker walking off the line and putting on a lab coat. That would no doubt be asinine. Building Innovation cultures come in many flavors (see this by Hutch Carpenter on the many incarnations). It really means opening up the participatory funnel on not only suggesting but more importantly, refining the good ideas and getting the kinks out. In practical terms this means getting the big brains hidden in the corners of your enterprise to contribute unique data points (validation, rebuttals, refinement, oversight) to remove risk and enrichen outcomes. Far away from the lab or mahogany row where ideas have traditionally been hatched lies two complementary flavors of talent: practical front line customer centric views (customers, support, sales, partners, marketing) as well as deep deep component level knowledge (product developers, suppliers). Both these camps bring a heavy dose of insight that can shape execution outcomes.

Balancing The bird in hand vs. Two in a Bush

Other than that visionary CEO, when’s the last time you’ve heard leaders tout their innovation wins? They generally talk about operational and revenue wins because they manage people and products (development or sales). The problem with mahogany row innovation is that those same management realities of preferred top down innovation that Pat touts, bring along another, ugly, truth. Management systems of the last 4 decades have rewarded people managers more than subject matter experts. If you manage large numbers of people you get rewarded. If you continue to remain an individual contributor that wants to contribute deep deep subject matter expertise, theses very little room for you in the leadership ranks at most organizations. The fact is that beyond long range directional moves and high level innovation requirements to get there, operational leaders often can’t sweat the details of what might be, at the cost of managing where the dollars and cents come from today. They need the best minds across the organization to come together and execute on business innovation, whilst they keep Wall Street satiated during the next earnings call.

Ideation vs. Idea Execution

Innovation cultures support execution. The germination of innovation can often be really top down directional in many cases but with the best of the best when it comes to sourcing talent across the ecosystem (customers, employees, partners and suppliers). Citing one of our own examples, were working with one of the world best known traditional software companies facing what looks like a very dark cloud computing overcast on their core bread and butter business landscape. The realization to innovate comes decisively from the top yet together were leveraging those very core assets in place today (product know how, market positioning, incumbent customer segment needs) to innovate a shift in service delivery model, market engagement and value proposition to embrace the new opportunity.

In line with what our work covers (and the byline of this blog), I was naturally drawn to this Economist book review of “The Other Side of Innovation: Solving the Execution Challenge” by Vijay Govindarajan and Chris Trimble of the Tuck School of Business at Dartmouth College. The book offers a reasonable approach to executing innovation that would in fact be embraced by many many leaders. This snippet of examples gets to the crux of the issue:

Nucor Corporation, a steelmaker, gives its workers bonuses if they can produce steel more efficiently. Deere & Company, a maker of farm machinery, has produced a detailed playbook on how to design new tractors.

These are distinct execution outcomes of an innovation culture – different from some notional wild west format. And I believe in sharp contrast to recent concentrated innovation efforts that were high profile failures. And beyond the few forward thinking organizations who can let innovation run loose but still reel in the big fish (for the record, I don’t have a problem with this and we work with partners and customers that live this management theory), the flavor of innovation sold by many theorists offer this often impractical mode of innovation design:

Many would-be innovators deal with the trade-off between efficiency and innovation by rejecting traditional management entirely. They repeat mantras about “breaking all the rules” and “asking for forgiveness rather than permission”. They set up skunk works (small, autonomous units with a remit to innovate) and mock the boring corporate types who write their pay-cheques. But again this is counter-productive. Mocking the corporate establishment only encourages it to starve you of resources.

In the Power of Pull by John Hagel III, John Seely Brown and Lang Davidson, we see definite data how our efforts to date (which includes how we have innovated to-date) is keeping us on track to approaching a big zero when it comes to return on assets. So I would suggest that we rethink unnecessarily top loading our ideation and as important, feasibility and execution. We need all big brains on deck to collaborate in more agile ways (read: wrap around new concepts more fluidly) and this book gives data on why it needs to be done ASAP. And if its decisive innovation examples you are looking for when success would have been a pipe dream without a well orchestrated concert of surgical business decisions, supplemented by a coalition of the brightest, there’s plenty in The New Polymath by Vinnie Mirchandani on both do’s and don’ts referencing the Telco, Healthcare, CleanTech and other business sectors.

In my assessment, in practical terms, many oftoday’s leaders have little choice but to encourage some degree of an innovation culture that allows them to test, validate, dispute and confirm large scale directional changes with a broader set of talent that transcends hierarchy. Customer and market expectations and the effects of globalization are more dynamic than ever these days and the ability to see the best innovation come through whilst still delivering results today will in fact require all hands on deck. So, as leaders, before you unleash the Kidons of innovation, make sure your differentiating between decisive innovation execution and wild west idea festivals. That disciplined approach to seeing ideas through will in big part dictate the odds of long term viability.

Continue reading » · Rating: · Written on: 08-30-10 · 3 Comments »

No Context? No Collaboration. Goodbye, Google Wave

The innovation zealot in me felt instant disappointment today upon reading that Google Wave is no longer. The official word from Google:

The use cases we’ve seen show the power of this technology: sharing images and other media in real time; improving spell-checking by understanding not just an individual word, but also the context of each word; and enabling third-party developers to build new tools like consumer gadgets for travel, or robots to check code.

But despite these wins, and numerous loyal fans, Wave has not seen the user adoption we would have liked. We don’t plan to continue developing Wave as a standalone product, but we will maintain the site at least through the end of the year and extend the technology for use in other Google projects.

One one hand, its startling when a behemoth such as Google cannot use its deep tentacles in the developer and user community to shepherd a product to critical mass. That’s a lesson for many others that think they can win just on sheer scale and marketing wallet. It doesn’t matter if you are a Cisco or Microsoft –  today’s end user in the enterprise has more ability to vote with their clicks than they ever did.

Mike Arrington at TechCrunch suspects: “Maybe it was just ahead of its time. Or maybe there were just too many features to ever allow it to be defined properly.” That’s definitely part of it – I personally felt there was way too much happening in Wave to encourage a wholesale leap off of the email cliff.

But there’s a more important issue at play here. My sense is that the primary culprit here is lack of context.  No matter how sexy, the use case for silo’ed, dumb “un-smart” collaboration still generally goes like this:

  • Think up/get notified of a process problem or event
  • Remember that a bunch of tools and metaphors (email, phone, the conf room or water cooler, software) exists that can help decision facilitation and brainstorming
  • Group/find the right people to collaborate
  • Pick a collaboration metaphor that works for everyone
  • Solve the problem
  • Go back to the system of record or powers that be (a boss, a customer, a supplier etc), to deliver the outcomes.

That’s a lot of steps and frankly a lot to expect from the average business user. If you want to hear more voices on this, the comments on Lifehacker are especially enlightening. And there’s parallels to be drawn from the consumer world as well: Think about the scores of of tools and nifty web apps introduced by Robert Scoble. We rush to try them, fall in love instantly, and then proceed to forget about them, pronto. Why? Because most of them require stepping out of our daily routines or are predicated on pre built, evergreen network effects to see value.

This is a conversation I’ve had with more vendors and customers than I care to remember but its working and many of them are understanding the value of associating collaboration with performance drivers (more in a subsequent post). Organizations still need to understand how to design work processes that blend optimal process and collaboration but its a hell of a lot easier when the software choose to plays nice.

On the other hand, far too many product teams continue to pile on whiz-bang collaboration features when end users are still struggling to understand the basic applicability of these new tools to meeting their performance requirements in a better/faster/simpler way. Organizations on the other hand often have a huge gap between declaring big picture strategic collaborative intent and tool selection. It’s in that gap where the “why” and “how” gets figured out and where the magic truly happens.  Putting the onus on the user to decipher when to use enterprise 2.0 or collaboration will almost never lead to business results.

You have to give Google credit for trying and failing fast though. I had high hopes. The good news is that Google promises to inject some of Waves core technology into its other products. That hopefully will provide the necessary context that will celebrate some of the most amazing innovation that the core Wave team developed.

Continue reading » · Rating: · Written on: 08-04-10 · 22 Comments »