
The Hidden Cost of Consensus: How Committee Culture Kills Innovation Velocity
I watched a brilliant innovation die in a conference room last month. Not from lack of funding or technical impossibility. It died from consensus.
The project had everything going for it. Clear market need. Solid business case. Enthusiastic sponsor. But eighteen months later, it was still circling the drain of "stakeholder alignment." Every decision required another workshop. Every workshop spawned three more review meetings. Every review meeting generated a list of "considerations" that sent the team back to square one.
Sound familiar?
The Consensus Trap
Here's what happens when you design innovation around committee culture. You optimise for agreement instead of progress. You mistake process for rigour. You confuse consultation with collaboration.
The result is what I call innovation theatre. Lots of activity, lots of engagement, lots of PowerPoint. But nothing ships.
At NASA, we learned this lesson the hard way during the early shuttle programme. Too many voices in the room meant too many requirements. Too many requirements meant too many compromises. Too many compromises meant a vehicle that tried to be everything to everyone and ended up being optimal for no one.
The same pattern plays out in every large organisation I work with. Innovation projects that should take months stretch into years. Not because the problem is complex. Because the decision-making process is broken.
Why Consensus Kills Speed
Consensus-driven innovation fails for three behavioural reasons:
The lowest common denominator effect. When you need everyone to agree, you end up with solutions that offend no one but excite no one. Innovation requires bold bets. Committees make safe bets.
Analysis paralysis by committee. More stakeholders means more questions. More questions means more research. More research means more delay. Meanwhile, your competitors are shipping.
Diffused accountability. When everyone owns the decision, no one owns the outcome. Without clear ownership, there's no urgency to act. Projects drift.
I've seen teams spend six months debating the perfect solution while their startup competitor captures the market with a good-enough product they built in six weeks.
The Real Cost of Committee Culture
It's not just time. Consensus culture creates three hidden costs that destroy innovation capacity:
Talent flight. Your best innovators get frustrated and leave. They didn't join a big company to spend half their time in alignment meetings. They joined to build things that matter.
Risk aversion spiral. When every decision requires group approval, teams start proposing only ideas they know will get unanimous support. Innovation becomes incremental by design.
Opportunity cost blindness. While you're workshopping the perfect solution, market conditions change. Customer needs evolve. Technology moves on. The window closes.
At ING, we saw this pattern clearly. Their most successful digital products came from small, autonomous teams with clear decision rights. Their biggest innovation failures came from cross-functional committees with shared ownership.
Three Ways to Restore Innovation Velocity
1. Use the "Informed Captain" model instead of consensus. Designate one person as the decision-maker for each innovation stream. Everyone else provides input, but the captain decides. The key is choosing someone with both domain expertise and political capital to make decisions stick.
2. Time-box consultation periods. Give stakeholders exactly two weeks to provide input on innovation proposals. After that, the decision gets made with available information. No extensions. This creates urgency and forces people to prioritise their feedback.
3. Create "fast lanes" for small experiments. Any innovation test under £10k and 30 days gets automatic approval. No committees required. This keeps the innovation pipeline moving while bigger bets go through proper governance.
The magic number seems to be around seven stakeholders. Below that, you get speed. Above that, you get theatre.
Speed as a Feature
The companies that win at innovation treat speed as a feature, not a bug. They understand that market timing matters more than perfect solutions. They'd rather be approximately right and fast than exactly right and slow.
Amazon's approach is instructive here. For reversible decisions, they use a lightweight process optimised for speed. For irreversible decisions, they use heavyweight governance optimised for quality. The key is knowing which type of decision you're making.
Most innovation decisions are reversible. Most committees treat them as irreversible.
That's the gap that's killing your innovation velocity. Close it, and watch what happens to your time-to-market.
"Innovation dies in committees, not in markets."
