I’ve been thinking lately about why some of the best ideas I’ve seen came from two or three people sitting around a whiteboard, while some of the most frustrating decisions came from rooms full of intelligent, experienced people. At first I thought it was because small teams simply acted faster. The more I’ve thought about it, though, the less convinced I am that’s the real reason.
I think the difference is that small teams tend to optimize for ideas. Large committees tend to optimize for people. That isn’t meant as criticism. Most organizations intentionally build cultures where everyone is heard, disagreements stay respectful, and people feel comfortable contributing. Those are good things. I’d much rather work in an environment where people respect one another than one where the loudest voice wins.
The trouble is that somewhere along the way, many organizations begin treating equal participation as if it should produce equal influence. Those aren’t the same thing.
If ten people are discussing a new product feature, every one of those people deserves to be heard. That doesn’t mean every suggestion improves the solution. Yet there is often an unstated pressure for everyone to leave some fingerprint on the final design. Sometimes those changes make it better. Sometimes they don’t. More often than not, they simply make it different.
I’ve started wondering whether this is why ideas seem to lose something as teams get larger. Nobody is intentionally making the solution worse. Everyone is trying to help. But every compromise is made for a social reason as much as a technical one. Before long, the conversation shifts from “What’s the strongest idea?” to “How do we make sure everyone feels represented?”
Those are very different goals.
What’s interesting is that this problem grows almost invisibly. Add one more person to a discussion and very little changes. Add five, and the number of relationships between people grows dramatically. More personalities. More perspectives. More opportunities for misunderstanding. More hesitation before saying, “I don’t think that’s the right approach.”
That last part is important because healthy disagreement is surprisingly difficult. It asks two things of people that don’t come naturally. The first is someone willing to criticize an idea without criticizing the person who proposed it. The second is someone capable of hearing that criticism without taking it personally. Either one is hard. Finding both consistently across a large committee is remarkably uncommon.
As a result, criticism often becomes softer than it should be. Instead of questioning assumptions directly, people suggest small additions, gentle compromises, or changes that allow everyone to contribute. None of those are bad on their own. The problem is that ideas are rarely improved by avoiding the uncomfortable questions.
I’ve found that the most productive conversations don’t begin with, “That won’t work.” They begin with inquisitiveness.
“What happens if twice as many people use it?”
“What assumption are we making here?”
“What’s the downside if we’re wrong?”
Questions encourage people to think alongside you rather than defend themselves against you. They make it easier to improve an idea without making someone feel like they have to defend their reputation.
That also means accepting that every good idea has flaws. I’ve never seen a proposal without tradeoffs. Finding one isn’t a reason to discard it. The real question is whether the advantages outweigh the disadvantages. Some flaws are fundamental. Others are simply the cost of getting something much more valuable in return. If every imperfection becomes grounds for rejection, innovation slows to a crawl.
None of this is an argument that dictators make better decisions than committees. History gives us plenty of reasons to reject that idea. Different viewpoints matter, especially when evaluating risk or exposing blind spots. The question isn’t whether one person or twenty people should make the decision. It’s what the group is optimizing for while they make it.
The best teams I’ve worked with weren’t the ones that agreed quickly. They were the ones where disagreement may have led to some healthy tension, but ultimately mutual respect won the day. People challenged ideas freely, were open-minded enough to rethink their first thoughts, and had no problem saying, “Your approach is better than mine.”
Maybe that’s the real lesson? Great teams aren’t built around consensus. They’re built around the belief that ideas should compete honestly, criticism should make them stronger, and the best outcome isn’t the one that contains a little bit of everyone. It’s the one that survives after everyone has left their pride at the door and looked at the solution as objectively as possible.