How Innovation Happens — Lesson #3: Never Let a Committee Touch a New Idea

I've been covering the link between future trends and innovation strategies for 30+ years. I went back through my blog posts, stretching to 2002, to dig out the nuggets of innovation insight I've discovered along the way. This series revisits those stories, tests what still holds up, and turns them into practical lessons for what comes next.


"Form a Committee. An absolute surefire way of shutting down ideas!"

I've watched this pattern for over twenty years, across some of the biggest companies in the world: a great idea surfaces, someone gets excited about it, and then someone else says, "Let's put together a committee to look into it." That's the moment the idea dies. Not with a rejection, but with a slow, quiet suffocation.

Committees don't kill ideas on purpose. They kill them structurally. Herd mentality takes over. Decisions get deferred because deferring feels safer than deciding. Uncertainty becomes a virtue and indecision becomes an asset. By the time the committee reports back, the market's moved on, or the original spark has been diluted into something nobody's excited about anymore, including the person who thought of it.

The organizations that actually innovate treat a new idea completely differently: fast, small-group ownership, a real deadline, and someone senior enough to protect it from the herd.

If committees are where ideas go to slow down, the answer is to redesign how decisions get made. Here are three places to start.

Action Items:

  • Look at the last new idea that went to a "committee" or "working group" in your organization. Is it still alive? Be honest.
  • The next promising idea that surfaces, assign it to one accountable owner and a hard 2-week decision deadline. No committee, no exceptions.
  • If a committee is unavoidable, cap it at three people and give it a mandate to decide, not to study.

Explore the full How Innovation Happens series.


Real-World Examples

These researched examples show the lesson at work in the real world.

Buurtzorg: Thousands of nurses without a conventional management ladder

When a Dutch home-care service grew, its leaders faced a familiar choice: hire supervisors, build reporting layers, and create more committees to coordinate the work. Buurtzorg went in another direction. Founded in 2006, it organized care around small teams of nurses who take responsibility for their patients and much of their daily operations.

Teams have substantial authority over schedules, care coordination and local decisions. A small group of coaches and purpose-built information systems provide support, rather than a conventional hierarchy of middle managers. The scale is what makes the example so startling.

A 2025 academic study described an organization with more than 14,000 employees and over 900 self-managing teams, without conventional supervisors or middle-management layers. It did not eliminate the need for standards, technology, accountability or professional judgment. It redesigned the way those needs were met.

Its experience does not prove every organization should copy the model, particularly in high-risk environments where independent review is necessary. It does demonstrate how much routine approval machinery is an organizational choice rather than an unavoidable law of growth. Buurtzorg did not ask a bigger committee to solve its coordination problem; it challenged the premise that it needed one.

Why it matters: Before adding another approval gate, ask whether the people closest to the customer could make a better decision with clearer boundaries and better support.

Sources:

Haier: The appliance manufacturer that broke itself into microenterprises

Haier makes household appliances, a business where global scale might appear to demand layers of purchasing, production, product and sales management. Chairman Zhang Ruimin decided the management structure itself was getting in the way of responding to customers. Under the company's RenDanHeyi approach, many conventional functions and hierarchical boundaries were reorganized around small entrepreneurial units.

In an interview with McKinsey, Zhang said Haier had removed an intermediate layer of more than 12,000 employees and operated approximately 4,000 microenterprises. These units were expected to connect directly to user needs, form collaborations and bear responsibility for outcomes rather than simply execute a direction passed down through the hierarchy.

This was not the absence of coordination: microenterprises had to connect to one another, often in what Haier calls ecosystem microcommunities. Nor is it a plug-and-play formula that would work unchanged at a bank or utility.

But it exposed a crucial assumption: that an idea must travel through functional committees before anyone can test whether a customer wants it. Haier tried to replace organizational permission with customer accountability. The radical part was not a new refrigerator. It was who was authorized to make decisions about the refrigerator.

Why it matters: Eliminating a committee is not enough. Decision rights need to move somewhere useful, closer to evidence, customers and accountability.

Sources: