Search This Blog

CCE in brief

My photo
Recovering backpacker, Cornwallite at heart, political enthusiast, catalyst, writer, husband, father, community volunteer, unabashedly proud Canadian. Every hyperlink connects to something related directly or thematically to that which is highlighted.

Friday 29 June 2012

When Innovation Fails (by John Kotter)






First, we lacked enthusiasm. None of us went into the process with a sense of passion that we could, or even should, find something new and different. We were appointed, and as we all know, when you are tapped on the shoulder, you don’t say no, lest you jeopardize your next promotion.

Second, we were all senior. Way too senior. Yes, a senior leader’s perspective is useful, but much more important is that of the many customer-facing people who are dealing with these issues everyday, trying to fix what is broken, seeing what others are doing, and who know (almost without thinking about it) what is wrong with how the company does what it does. They have less to lose by challenging and questioning, and it doesn’t form the basis of what made them successful. Conversely, how eager are leaders to challenge that which made them successful in the first instance?

Third, no-one knew what we were trying to do. Who cared if we had spent 100 hours working on building something new and exciting? The other 14 people, maybe. And those who did know about our little initiative? They looked at us as though we had all the answers; by being placed on the “Innovation Board,” we were seen as the innovative thinkers — and, as a result, others were left feeling that they lacked what it took to generate fresh, game-changing ideas. How wrong.

The way we tried to create innovation — organizing, prescribing, and delegating it — didn’t work. Yes, these groups may improve things — maybe even a lot of things — but rarely is this “innovation.” Producing the next product (like the iPod) or creating a new market (Instagram, without a big team) that had never existed before — that is innovation. Microsoft creating the Surface — not so much innovation, and more catch up? Thinking once an innovator, always an innovator — not a path to success.


1) Use only volunteers. Who in your organization feels excited about trying to build that next product or market? Let THEM — the people on the front lines, who are doing their day jobs, who happen to know your business better than anyone else — into the process. Jim Whitehurst of Red Hat figured this out. Others have too.

2) Sponsor an environment that encourages risk-taking. It’s fantastic if an employee takes initiative and risks making innovation. What do you do if they fail? Are they punished? You can be certain if an employee is punished for taking a risk toward innovation, that other employees will not be taking any risks.

3) Make time for brainstorming. It takes time, and sometimes it takes creating a particular environment to get employees into an innovative mindset.
This approach will foster some truly transformative ideas, and there will be an enthusiastic base of supporters ready to turn those ideas into action.

Now that’s a novel approach. Maybe, dare I say, an innovation.


Russell Raath is a senior engagement leader at Kotter International, a firm that helps leaders accelerate strategy implementation in their organizations.

You can't blame me for enjoying it when what I say fits in with what smarter people are suggesting.  But either way, there it is.

No comments:

Post a Comment