Customer Review

97 of 100 people found the following review helpful
3.0 out of 5 stars 100% correct but not really new, November 11, 2010
This review is from: The Other Side of Innovation: Solving the Execution Challenge (Harvard Business Review) (Kindle Edition)
As a consultant who believes the emphasis on idea generation is wildly overblown, and that there is far too little focus on idea execution, I was glad to hear that VJ Govindarajan and Chris Trimble were developing a book focused on "solving the execution challenge". Frankly, all the flash and sizzle of trend spotting, understanding customer needs and idea generation is interesting, but it's in the idea management, evaluation, selection, prototyping and commercialization where all the heavy lifting gets done, and the real value added.

I've really struggled to wrap my head around The Other Side of Innovation. What can you say about a book that is correct in all its recommendations yet doesn't seem to add anything new to the discussion. Everything that the authors talk about is absolutely correct, and perhaps needs to be rehashed again and again.

In the introduction the authors use a mountain climbing metaphor to think about the focus on the exciting "summitting" but point out that achieving the summit is only half the job. What's left is the less interesting but equally important dismount. Similarly, innovation requires both the generation of ideas and the evaluation and implementation of ideas, with implementation usually receiving the short shrift. This assertion is absolutely correct, but is it new? Implementation, whether it is focused on new ideas or an update to an existing product or service, is always the "hard part". The authors pursue a consistent definition of innovation, looking at several different models:

* innovation = ideas + execution
* innovation = ideas + motivation
* innovation = ideas + process

But they don't seem to have a definitive answer. Again, interesting, but does this add to the conversation?

Next, the authors note that there are two kinds of "teams" in most firms. The Performance Engine, which is the portion of the business focused on the day to day execution of the business - creating products, shipping products, etc. This is the portion focused on earning profits, doing things consistently and efficiently. In many organizations, an innovation team will be formed. The authors call this the Dedicated Team, and they note that many of the things the Dedicated Team does is in direct conflict with the Performance Engine. The Innovation Team talks about "breaking all the rules" which "sounds like breaking the Performance Engine". There is direct conflict between the goals and expectations of the two teams. Again, this is 100% correct but not a new observation. Anyone who has created a new project and attempted significant change within an organization with a strong executional culture knows about this conflict.

Having convinced the reader, and themselves, that innovation is different from standard operations, the authors then divide the rest of the book into two sections: building a team and running an disciplined experiment.

In the section on building a team, the authors examine the needs and requirements of the Dedicated Team (the people who are full time on an innovation effort) and the relationship between those people and Shared Staff (and yes, the authors capitalize all of these teams, as if they are new or different). The authors talk about the dilemma an organization faces - to continue efficient operations while managing the possibilities and distractions of an innovation project. Their conclusions:

* Because ongoing operations are repeatable, while innovation is nonroutine, innovation leaders must think very differently about organizing
* Because ongoing operations are predictable, while innovation is uncertain, innovation leaders must think very differently about planning

The authors provide descriptions as well about how to decide what work belongs in a Dedicated Team and what work can be accomplished in Shared Services. They also identify a number of "traps" when building an innovation team:

* Having a bias for insiders. Recommendation: hire more outside people
* Adopting existing definitions for roles. Recommendation: new titles and new innovation space
* Reinforcing the dominance of the Performance Engine.
* Assessing performance based on established metrics. Recommendation: new metrics
* Failing to create a distinct culture. Recommendation: Choose the best aspects of the culture.
* Using existing processes. Recomendation: Invent new processes
* Succumbing to conformity.

Finally, in the first section, the authors talk about managing the relationship (partnership) between the innovation effort and the Perfomance Engine. They say:

"..the Performance Engine has more power than you do. It is larger. Not only that, it has the stronger case for spending resources. Its arguments are more quantifiable, with shorter-term and more predictable returns on investment. You, on the other hand, can do no better than promise the possibility of a big, long-term payoff."

That, again, is 100% accurate and fairly obvious, as are the proscriptions the authors make to solve that dilemma.

Section Two of the book argues that one of the challenges of innovation is that creating a new product or service should be thought of, and managed like, a scientific experiment. The authors go so far as to break this into three sections: formalize the experiment, break down the hypothesis and seek the truth. This, again is correct but perhaps overly emphasized, as we've found that planned "experiments" using rapid prototyping that engage prospects and are conducted in an iterative fashion are exceptionally valuable.

Strangely, I found the most valuable contribution of the book to reside in the conclusion, where the authors address the attributes of a good innovation leader, what they call a "supervising executive". They state that the individual must possess four attributes: must be able to get the initiative off to a good start, must monitor interactions with the Performance Engine, stay closely engaged in the learning process and finally, shape the initiative's endgame. To accomplish these goals and to innovate successfully, the authors argue that the "supervising executive" must be: 1) powerful 2) broadly experienced and 3) in a position to serve the long-term interests of the company as a whole. Note that they don't think you should assign the role to just anyone - but someone who has respect and power across the organization, who has a "breadth" of experience. They prefer people who have experience preferably in several business units if not in several markets or industries.

The last part of the conclusion reviews what seems almost de riguer for most innovation books - a debunking of a list of innovation myths. Scott Berkun did this better in his Myths of Innovation.

Strangely, while the book addresses many topics that are necessary, it skims over items we've found to be exceptionally important in idea execution. Several that come to mind that aren't discussed in any detail include:

* Defining and publishing an innovation process that describes how ideas will be evaluated
* Defining and publishing a set of evaluation criteria so people understand how ideas will be evaluated and the critical criteria
* The importance of rapid prototyping and active customer engagement in this effort
* How to select the best people for idea execution
* What skills an idea execution team needs and how to train them effectively
* How to transition an idea from a Dedicated Team to a product or service development team

These are all critical factors in the execution phase of an idea, yet are brushed over or not mentioned in the book.

As I said earlier, this book was a real struggle for me. For what the authors decide to focus on, the book is 100% accurate but doesn't seem to break any new ground. Yet there are many factors within the idea execution phase that the authors either ignored or chose not to focus on, which seems strange, and they overly emphasize the importance and commitment to experiments.

I'm sure this book will take its place on the shelf with many other books about innovation. It is true that there are far fewer books about execution, so that in itself may propel this book to increased popularity, but I'd have to argue that books like Robert Tucker's Driving Growth through Innovation or Davila and Shelton's Making Innovation Work are just as good.

This review is cross-posted from the review on my blog Innovate on Purpose
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No

[Add comment]
Post a comment
To insert a product link use the format: [[ASIN:ASIN product-title]] (What's this?)
Amazon will display this name with all your submissions, including reviews and discussion posts. (Learn more)
Name:
Badge:
This badge will be assigned to you and will appear along with your name.
There was an error. Please try again.
Please see the full guidelines here.

Official Comment

As a representative of this product you can post one Official Comment on this review. It will appear immediately below the review wherever it is displayed.   Learn more
The following name and badge will be shown with this comment:
 (edit name)
After clicking the Post button you will be asked to create your public name, which will be shown with all your contributions.

Is this your product?

If you are the author, artist, manufacturer or an official representative of this product, you can post an Official Comment on this review. It will appear immediately below the review wherever it is displayed.  Learn more
Otherwise, you can still post a regular comment on this review.

Is this your product?

If you are the author, artist, manufacturer or an official representative of this product, you can post an Official Comment on this review. It will appear immediately below the review wherever it is displayed.   Learn more
 
System timed out

We were unable to verify whether you represent the product. Please try again later, or retry now. Otherwise you can post a regular comment.

Since you previously posted an Official Comment, this comment will appear in the comment section below. You also have the option to edit your Official Comment.   Learn more
The maximum number of Official Comments have been posted. This comment will appear in the comment section below.   Learn more
Prompts for sign-in
 

Comments

Tracked by 3 customers

Sort: Oldest first | Newest first
Showing 1-2 of 2 posts in this discussion
Initial post: Sep 9, 2011 12:14:37 AM PDT
Thank you for the great review. I actually read it after I finished reading "Other Side," and I'm glad I did. While I found this book to be, like you said, spot-on, it didn't really stir anything new for me. I wasn't underlining or thinking about how I'd bust down the doors to work the next day to tell everyone what we needed to do to stay ahead in the game. Granted, very few ideas CAN make you do that.

I don't want to throw The Other Side of Innovation: Solving the Execution Challenge (Harvard Business Review) under the bus. It's a wonderful book. I just think we need more NEW, more "look at this!" I've been searching all over for that, and, even though I've put together a great innovation Hall-of-Fame (1: Brainstorming and Creativity Software - Thoughtoffice Innovation Suite - Mac OSX - Windows XP-7, 2: Ideafisher, 3: Best Practices Are Stupid: 40 Ways to Out-Innovate the Competition), I'm still looking. And, unfortunately, this book just didn't hit it. I'd go into more detail, but you've already hit everything (and more) above.

Let me ask this of all the innovation-minded brilliants out there: What other books/software come highly recommended? Who's going to lead us into the teen years of the 2000s?

Posted on Oct 19, 2012 9:12:20 AM PDT
Jeffrey, thanks for the review of this book. You recommended books like Robert Tucker's Driving Growth through Innovation or Davila and Shelton's Making Innovation Work that are just as good. Are there newer books about innovation on the market that you can recommend?
‹ Previous 1 Next ›