There is a particular kind of meeting that should make any product leader nervous: the one where everyone agrees.
Anyone who has led a project of moderate complexity knows the exact opposite situation well enough; the loud, confident voices that slow everything down without moving anything forward. Those that offer shallow alternatives with great conviction, that make agreeableness feel almost attractive by comparison. Almost.
Because the room that agrees too readily has its own quiet damage, less visible but often more lasting.
I’ve been fascinated by consensus since the first standard (grade). My default as a kid, was to build consensus before acting. So when my small group of friends laid down new rules for the group that required taking turns picking the day’s game, when it was my turn, I suggested we each suggest a sport or game, and go with the most popular vote.
My two buddies found this unacceptable, and promptly removed me from the group. I could easily have smoothed it over. Instead, I found myself quietly realizing something: if they valued their preference for simplicity over a reasonable process, and over me, perhaps the group wasn’t the loss it appeared to be. I made a new friend that day. The consensus instinct has stayed with me, though the years and the complexity of more chewy projects have taught me to hold it more lightly. People, generally speaking, are not fond of the effort that genuine agreement requires. They will defer, go along, and wait to either celebrate the success or completion, or to assign blame.
Which is precisely what makes unanimous agreement in a leadership room so worth examining.
Consensus feels like progress, it has the texture of momentum, the relief of resolution. But it could easy either mean that the right answer has been found, or that the right questions were never asked. Someone deferred. Someone decided the moment wasn’t worth the friction. Someone looked around, read the room, and chose alignment over accuracy. The decision that emerges from that room isn’t a strong one, it’s an unchallenged one, which is a very different thing.
These are places many large organizations tend to falter most visibly: decision-making becomes slow, layered, and hedged, not because people aren’t capable, but because the system has accumulated so many filters and sign-offs that genuine thinking gets processed out entirely. What remains is a procedure that produces decisions without producing insight. The less comfortable observation, though, is that the startups which will become those same lumbering giants are already forming their habits right now. The speed that feels like an advantage in the early stages, deciding quickly, iterating before anyone has fully understood what they’re iterating on, is not discipline. It is the absence of it, dressed up as agility. Tomorrow’s sluggishness is being quietly assembled today.
Speed in the decision-making phase is frequently overrated, and the cost of it rarely appears on the same balance sheet as the decision itself. It shows up months later, in products that solved the wrong problems efficiently. In the feature set that made perfect internal sense and left users cold. Or in the hire that ticked every visible box and disrupted every invisible one. The case for building deliberate, slower inquiry into product and organizational strategy, especially when timelines are tight, is not a case for caution. It is a case for not paying twice: once to make the decision, and then to undo it.
These are the kinds of questions I explore with product leaders and co-founders in my virtual strategy sessions. If any of this has struck a chord, I’d be glad to hear about what you’re working on. [https://www.productinnovator.in/consult]