How To Kill Ideas (Part 53)

Many organisations act as inhibitors of innovation.

Rules and protocols are put in place, often for very good reasons, that preserve the status quo.  Over time, organisations develop a set of social norms – ‘the way we do things around here’ – that can quell any creativity or dissent.

Organisations can quickly develop an autonomic immune response that kills ideas – without any conscious effort. This immune system builds up easily and quickly spreads, but is far harder to dismantle.

One of the ways you can begin to repel these idea antibodies is , as Chris Bolton has outlined, to deploy a sort of ‘immunosuppressant agent’. This may simply be strong leadership saying ‘all new ideas are welcome’.

In my last post I shared how Bromford are attempting to democratise innovation by asking the 50 most senior leaders in the organisation to develop their skills by daring to disagree with each other and becoming more receptive and open to challenge.  

Working with my LD50 colleagues we established a Developing Ideas Group where we encourage colleague to submit ideas that save us money or improve customer or colleague experience. We are trying to distinguish between simple ‘ideas’ that lend themselves to a ‘crack on and try it approach’ with a complete acceptance of failure, and the more complex/higher risk problems.

The more complex problems are presented through a colleague pitch.

Asking colleagues to pitch ideas is a high risk venture. There is a glorification of the pitch in business today. Startup events and innovation challenges are popping up everywhere. Hacks are common, with 24 hour business creation marathons where strangers connect and form solutions together. Every such event revolves around the pitch and the skills and strategies required for an effective pitch.

Asking people to pitch ideas can fail as it forces people to rush to solutions. Which hastily assembled pitch should we bet on? The answer should often be: none of the above.

Pitching ideas is often just innovation theatre. Too many Executives fancy themselves as budding Dragon’s Den investors – waiting to show their business acumen by outwitting the person pitching. Many years ago I took part in a innovation challenge that followed the Den format so closely you could almost guess which Dragon the Executives were pretending to be. It was a dispiriting experience, with colleagues emerging either crushed or with a lot more work to do – often with no more resources.

At Bromford we are trying to do something slightly different – asking colleagues to pitch really great problems rather than firm proposals.

We’ve been coaching some of the Leadership team using nemawashi principles – so the rule of the pitch is that you can’t shoot any idea down – or even criticise it – you can only ask questions.

As I have previously written Nemawashi is a Japanese phrase translating into ”an informal process of quietly laying the foundation for some proposed change or project, by talking to the people concerned, gathering support and feedback, and so forth.” In Nemawashi the potential solution is prepared in very draft form but this time we check in with any colleague with a significant organisational position, not just bosses, to build consensus.

As David O’Gorman has written the nemawashiringi process is grounded in the need to maintain harmony within the organisation while at the same time make sound decisions.  An advantage of the nemawashiringi process is that once a proposal is approved it can be rapidly implemented because all the relevant parties are on board. This is in contrast to Western processes, which can encounter obstacles during implementation, even from parts of their own organisation.

Ideas are easy to kill – problems aren’t

Simply unleashing ideas just isn’t enough. They are too vulnerable, too easy to kill off. If we anchor ideas in truly great problems you’ll find that colleagues build on the initial idea rather than attempt to destroy it.

A problem shared really IS a problem halved. Most problems do not fit neatly into one team or function and require input from a variety of perspectives. That’s why attempting to solve them in operational meetings with the usual suspects is a waste of time.  By harnessing the creativity, expertise, and ingenuity of the wider organisation as willing volunteers, we can solve problems in a more inclusive, efficient, and effective way.

And here’s the point: people don’t resist an idea they have helped define.

So don’t criticise ideas. Just learn to ask better questions.

Three Reasons Why We Fail To Solve Problems

Why do some problems get solved whilst others stick around? Here are three examples of why we sometimes fail and what we could do differently.

At the beginning of April 2020 the World Health Organisation made a public declaration of collaboration that attempted to unify hundreds of scientific communities around one single goal: to speed the availability of a vaccine against COVID-19.

The pandemic is far from being ‘solved’, and may indeed remain unsolvable. However, one particular part of the problem was addressed just eight months later with people getting the very first vaccines, a process that normally takes years.

So how come we’ve not solved , or even made decent inroads, into problems that have beset us for decades like the housing or social care crisis?

How come you’ve likely got the same problems in your organisation that you’ve always had?

Or you thought you’d solved a problem but it just returned, in a mutated form?

The Importance of Constraints

One of the most recurring reasons for a problem not getting effectively solved is that it was never clearly defined in the first place. We’ve been doing some work at Bromford around effective team collaboration, and my colleague Carl Sautereau often talks of the ‘freedom of a tight brief’. In my language – he’s talking about the importance of a really well defined problem.

“Give me the freedom of a tight brief” was originally invoked by advertising legend David Ogilvy, as a requisite requirement for unleashing creative brilliance. Innovation thrives when we have constraints – as it shows us where to focus and, more importantly, where not to.

It reminds me of the work of Dr. Caneel Joyce, who says that “giving people too much choice limits creativity, just as giving them no choice at all does… just enough constraint incites us to explore solutions in new places and in new ways.”

She uses the analogy of a playground as a starting point for understanding the whole concept of constraints. Research found that when a fence is put up around a playground, children use the entire space to explore and play; the fence giving them a sense of safety and security. On the other hand, if that fence is removed from the playground’s border, the limits become unclear and the children stay toward the middle because that’s where they feel safe. Importantly, in team work within organisations Joyce found that the absence of clear constraints actually created conflict stemming from the unarticulated assumptions that people brought to the table.

One of the reasons for the rapid vaccine development is it had the tightest of tight briefs before it was deployed to multiple teams to solve.

Failure to Build Consensus

Another reason problems continue is where we fail to get sufficient support and don’t build a coalition around a solution. The housing sector , for example, has struggled for years to get traction behind what is a compelling argument for more affordable housing. In that case there are multiple actors involved in solving the problem , the same as vaccine development, but people have many different views on what the solution should be. Should it be more home ownership, shared ownership or rented? What’s the right mix? What does affordable even mean? Isn’t this just about too much immigration anyway? It’s a subject that can get very political very quickly, particularly in such a class conscious country as the UK.

You’ll have similar issues at organisational level, where barriers emerge at every step of the way. There are a number of ways to build consensus, but one I have found personally useful is the Japanese concept of nemawashi which means quietly laying the foundation for some proposed change or project.

A typical western approach would be to work up an idea or project, propose it to the boss or executive and if the idea is good enough, it will be chosen. Even assuming that approach is successful it then has numerous barriers ahead as you’ve got to negotiate the organisational antibodies designed to repel anything new or foreign.

In nemawashi the potential solution is prepared in very draft form but this time we check in with any colleague with a significant organisational position, not just bosses, to build consensus.  It takes patience and highly developed political nous but:

  • It reduces the risk of the idea by involving key people, and developing it, in the process of making it real.
  • Although there’s an upfront investment it time it reduces the time required overall, as it moves any potential conflict to the front end.
  • It increases people’s involvement in the idea, they are then personally invested in making it work as it is ‘theirs’
  • It increases the likelihood of success, because the idea has been refined by the many rather than the few

We’ve all resisted ideas because we weren’t asked or it landed outside our front door without us granting it permission. It’s a natural human reaction.

The Timing Isn’t Right

Timing is everything. A few years ago I remember doing Lab experiments on the use of QR codes for getting information to colleagues and customers. It failed.

At the time, QR readers were not built into most smartphones – it required the download of an app. Additionally, QR code use was so infrequent people were not in the behaviour of using the scanners. It had too much friction.

COVID changed all that. After a decade of mockery and dismissal, it took a period when nobody wants to touch anything apart from their phones to bring them into widespread use. I don’t know who invented the QR code , but they probably spent 10 years wondering why no-one was listening to their bright idea.

A tight brief that nails the problem and builds constraints around it , the building of consensus on a solution and the timing of the execution – all necessary components of solving problems.

Innovation isn’t about ideas. It’s about the right solution, for the right people, at the right time.


Photo by Toa Heftiba on Unsplash

%d bloggers like this: