The phone didn’t actually make a clicking sound when I disconnected, but in my head, it was the sound of a guillotine. I had just hung up on Sarah. It was 10:47 AM, and she was in the middle of a sentence about ‘synergistic alignment’ when my thumb, slick with a cold sweat I hadn’t noticed developing, slipped across the glass. Silence. Not the meditative silence of a focused workspace, but the heavy, vibrating silence of a professional disaster. I stared at the black screen for 17 seconds, watching my own reflection-pale, slightly older than I remember being yesterday, and distinctly panicked. I didn’t call back. To call back is to admit a clumsy hand; to stay silent is to invite a mystery. Instead, I turned my attention back to the glowing rectangle of my monitor, where a Google Doc titled ‘Strategy_Final_V27’ was currently being cannibalized by 7 people who had no business being in the same digital room.

But looking at this document, I didn’t need software. I could feel the stress in the typeface. I could see the institutional anxiety bleeding through the margins in the form of 87 unresolved comments. Most of them were ‘drive-by’ feedback-those little grenades of opinion tossed by people who have spent a total of 7 minutes thinking about the project but feel the existential need to leave a digital footprint.

The Violence of Bike-Shedding

There is a specific kind of violence in collaborative editing that we don’t talk about. We call it ‘transparency’ or ‘democratization,’ but it’s actually a slow-motion assassination of intent. I watched as a cursor belonging to someone named ‘Linda (Compliance)’ highlighted a paragraph I had spent 47 hours refining. She left a comment: ‘Not sure about the tone here. Can we make it more inclusive of the Q3 goals?’ The Q3 goals were about cost-cutting. The paragraph was about human empathy. You cannot make empathy ‘inclusive’ of cost-cutting without turning it into a lie, and yet, the system demands I try. This is the bike-shedding effect in its purest, most digital form. People who cannot contribute to the structural integrity of the nuclear power plant will spend hours arguing over what color to paint the bike shed, because they actually understand paint.

I’ve noticed that the frequency of comments increases as the deadline approaches, but the quality of those comments drops by roughly 67 percent. It’s a performance of engagement. If you don’t leave a comment, do you even work here? If you don’t suggest a comma change on page 17, are you providing value? We have replaced actual leadership with a rolling committee of the uninformed.

The Bloat of Compromise

I think about the physical toll of this. My neck has been locked in a 27-degree tilt for the last three hours. I am analyzing the stress in others, yet I am a walking knot of cortisol. This document, which started as a sharp, 7-page manifesto, has bloated into a 37-page monster of compromises. Every time someone adds a comment like ‘Let’s workshop this,’ a little piece of the original vision dies. It’s the death of a thousand cuts, or rather, a thousand ‘suggestions.’ The problem with tools that allow everyone to speak is that they rarely provide a mechanism for anyone to listen. We are all just shouting into the margins, hoping our highlighted text will be the one that survives the final cull.

The Authority of Singular Focus

There is a profound difference between collaboration and a free-for-all. True expertise is singular. It is focused. When you are dealing with something that requires precision-like the way I isolate a single frequency in a crowded room-you don’t want a committee. You want the person who has spent 27 years perfecting the craft.

I saw this clearly when a friend of mine went through a complex medical procedure. He didn’t want a ‘collaborative’ approach where 17 different nurses voted on where the incision should go. He checked the Wimpole clinic reviews because he needed specialists who understood the micro-details of a single, life-altering outcome. In surgery, as in strategy, there is a point where ‘more opinions’ actually leads to a failure of the system. You trust the specialist because they have the authority to say ‘no’ to the noise. In my Google Doc, ‘no’ is a forbidden word. Everything is a ‘yes, and,’ which is how you end up with a strategy that looks like a bowl of grey oatmeal.

I once analyzed a recording of a 47-minute meeting where nobody spoke for more than 7 seconds at a time. The ‘jitter’ in that room was off the charts. It was a room full of people terrified of being the only one not talking, yet nobody had anything to say.

Detecting the Trivial Tremor

I decided to perform an experiment. I went to page 27 of the document, a section that had been reviewed by all 7 stakeholders. I changed the font color of a single sentence to a very dark navy blue-almost black, but technically #000087. Within 17 minutes, I had a comment from Brian. ‘Is this font different? It feels aggressive.’ Aggressive. A color shift of three degrees was perceived as a threat, yet the fact that we had completely lost the core objective of the project by page 7 was ignored. We are tuned to detect the trivial. We are hyper-aware of the surface-level tremors because the deeper tectonic shifts are too frightening to acknowledge.

[we are drowning in the shallow end of the pool]

Resolving the Fake Progress

I’ve spent the last 37 minutes deleting my own responses to the comments. I had written a very clever, very biting rebuttal to Linda’s ‘inclusivity’ remark, but I realized it would only trigger a 17-email thread. Instead, I clicked ‘Resolve.’ I didn’t change anything. I just clicked the button. And you know what happened? Nothing. Nobody noticed. The resolution of a comment is often more important to people than the actual resolution of the problem. They just want the little yellow box to disappear so they can feel a sense of completion.

My boss Sarah finally messaged me. Not a call, but a Slack message. ‘Hey Marcus, got cut off there. Just saw your edits on the Strategy Doc. Great stuff, really feels like we’re getting to a consensus.’ Consensus. The word sounded like a flatline on an EKG in my head. Consensus is what happens when nobody has the courage to be right. It’s the 217-Hz hum of a stagnant pond.

I looked at the document one last time. It was a masterpiece of mediocrity, a 57-page monument to the ego of the middle-manager. I closed the tab. The relief was instantaneous, a drop in blood pressure that I could actually feel in my temples. Maybe the answer isn’t better collaboration tools. Maybe the answer is fewer people in the room. Maybe we need to return to a world where we trust the person with the scalpel, the person with the microphone, or the person with the pen, and let the rest of the 7 billion people on this planet just watch in silence. I think I’ll go for a walk. It’s 12:57 PM, and for the first time today, I’m not listening for the stress in the air. I’m just listening to the wind, well, nothing. And it’s the most honest thing I’ve heard all week.