The Sound of Silence and Yawning
The dry-erase marker squeaks in a way that sets my teeth on edge, a high-pitched protest against the 21st minute of silence that has descended upon the conference room. I am looking at Miles P., a corporate trainer whose posture suggests a man who has spent far too many hours in chairs designed by people who hate human anatomy. He is pointing at a diagram on the whiteboard-a bold, jagged line representing a new logistical path-but the VP of Risk is already unsheathing a red pen. I find myself staring at the dust motes dancing in the overhead fluorescent light, and before I can stop it, I yawn. It is a deep, soul-baring yawn that happens right as the Director of Operations is explaining the importance of ‘cross-functional synergy.’ The room freezes. I try to mask it as a sigh of profound contemplation, but we all know the truth. I am bored, and the idea we are here to protect is already dying.
Observation: The Steering Committee is a burial ground. We create these structures under the guise of building consensus, but consensus is often just a polite word for the lowest common denominator. When you take a sharp, brilliant, 101-degree idea and subject it to the friction of 11 different departmental agendas, you don’t get refinement. You get beige.
The Diffusion of Responsibility
Miles P. once told me that the most dangerous phrase in the English language is ‘let’s run this by the committee.’ He’s a man who has seen 41 separate initiatives withered by the cold breath of middle management. He describes the process as a slow-motion car crash where everyone is trying to grab the steering wheel, and as a result, the car just idles in the middle of the intersection until it’s hit by the reality of a changing market. We are terrified of individual responsibility. If a single leader makes a bold choice and it fails, there is a neck for the guillotine. But if a committee approves a mediocre plan and it fails, the blame is diffused into a harmless fog. No one is responsible because everyone was involved.
“
The committee is where organizational courage goes to die.
– A seasoned observer
The Cost of Assurance: Project Alpha-1 Bloat
I remember a project back in 2001-let’s call it Project Alpha-1. It was a simple, elegant solution to a recurring customer pain point. The original pitch was 11 slides long. By the time the committee was done with it, the presentation had swelled to 91 slides, including 31 pages of ‘contingency maps’ that addressed scenarios with a 0.01% chance of occurring. The original budget was a lean $10,001, but the committee insisted on adding external consultants and ‘validation phases’ that ballooned the cost to $200,001. The result? A product that the customers didn’t recognize and the staff couldn’t explain. We spent a year polishing a stone until it turned into dust. This is the tax we pay for the illusion of safety.
The Micro-Vetoes of Self-Preservation
There is a fundamental dishonesty in the way we approach these meetings. We pretend we are there to ‘improve’ the work, but most attendees are actually there to protect their own silo. The Head of Engineering isn’t looking at whether the idea is good; he’s looking at whether his team has the ‘bandwidth’ (another word that makes me want to yawn again) for the next 41 weeks. The Marketing lead isn’t worried about utility; she’s worried about whether the font choice aligns with a brand guide that hasn’t been updated since 2011. It’s a series of micro-vetoes that slowly strip the soul out of the work. It’s a tragedy of the commons played out in a room with a view of a parking lot.
I allowed myself to be sucked into the ‘consensus trap,’ believing that if I just listened a little longer, we’d find a way to make everyone happy. But you cannot make everyone happy while doing something that matters. Innovation is, by its very nature, an act of aggression against the status quo.
In some sectors, this kind of bureaucratic inertia isn’t just a nuisance; it’s a failure of duty. They need decisive, focused advocacy. This is why some organizations thrive-they maintain the ability to act with the speed and precision of a single, determined mind. For instance, if you look at the way suffolk county injury lawyer handle their cases, you see the opposite of corporate stalling. It’s about the individual, not the process.
Feedback vs. Interference
Why do we keep doing this to ourselves? Part of it is a genuine, if misguided, desire to be inclusive. We want people to feel ‘heard.’ But hearing someone is not the same as letting them edit your vision. There is a difference between feedback and interference. Feedback informs the vision; interference seeks to control it. Most committees don’t know the difference. They operate on the assumption that more opinions automatically lead to a better outcome, ignoring the fact that 11 people who don’t understand the core problem will never provide a better solution than one person who does.
Consensus is the graveyard of the extraordinary.
The Unspoken Fear of Obsolescence
I’ve started a small rebellion in my own work. When I’m asked to join a committee now, I ask one question: ‘Who has the final veto?’ If the answer is ‘the group,’ I decline. I’d rather be wrong on my own than be part of a group that is ‘right’ in the most boring way possible. We need to empower the ‘One.’ The one person who is obsessed with the outcome. The one person who has stayed up until 2:01 AM thinking about the details. Give that person the resources and the authority, and then get the hell out of their way. This is the unspoken fear that keeps the committee alive. It’s a job-preservation scheme disguised as a quality-assurance process.
Risk Mitigation vs. Opportunity Cost
Launch Probability
Launch Probability
I told him that every time we added a new stakeholder to the review process, the probability of the project actually launching decreased by 21%. We are building a world where it is impossible to fail because it is impossible to do anything at all.
The Sad Word: Manageable
As I left that conference room, I saw Miles P. in the hallway. He looked like he’d aged 11 years in an hour. ‘What now?’ I asked him. He shrugged and looked at his notes. ‘I’ll go back to the office and try to incorporate their feedback. I’ll make it smaller. I’ll make it safer. I’ll make it… manageable.’ It was the saddest word I’d heard all day. We had taken something that could have been a wildfire and turned it into a candle, and then we spent 11 minutes worrying if the candle was too bright.