The Price of Gravitas
I’m watching the blue cursor blink on the shared screen, a rhythmic, mocking heartbeat. It’s pulsing at the center of a cell in a Gantt chart that has no business being this colorful. Marcus, our project lead, is currently explaining why the ‘Phase 2 Alpha’ bar needs to be shifted by exactly 48 hours to account for ‘strategic alignment.’ He says this with a level of gravitas usually reserved for heart transplants or peace treaties. Meanwhile, in the bottom right corner of my second monitor, the Slack notifications from our lead engineer, Nina P.-A., are firing like a localized civil war. She’s not on the call. Or rather, her avatar is there-a grainy photo of her dog-but her microphone has been muted for 28 minutes. She’s actually working. She’s fixing a recursive loop in the authentication layer while Marcus spends $1888 of the company’s hourly burn rate discussing the hex code for ‘progress.’
Vibration vs. Value
“
Nina P.-A. […] once told me that the most dangerous thing in any negotiation isn’t a lack of money, but a surplus of ‘meaningless movement.’ She calls it the ‘dance of the 88 veils.’ It’s the tendency for people who have nothing to contribute to create complex rituals to justify their presence at the table. In her world, if you aren’t moving toward a contract, you’re just vibrating. In the corporate world, we call that vibration ‘synergy.’
We’ve built entire careers out of this high-frequency trembling, a collective humming that sounds like progress but produces exactly zero joules of actual output.
We have reached a point where the artifacts of work-the dashboards, the status updates, the Jira tickets with 18 nested sub-tasks-have become the work itself. I recently saw a manager spend 38 minutes of a 60-minute meeting ‘re-organizing the flow’ of the meeting’s own agenda. It was a recursive nightmare. We were having a meeting to discuss how to have the meeting, while the actual problem we were supposed to solve sat in the corner like a neglected houseplant, slowly turning brown.
[The dashboard is not the engine; it is merely a picture of the engine, often painted by someone who has never opened the hood.]
There is a specific kind of exhaustion that comes from pretending to be busy while you are actually being prevented from doing your job. It’s different from the exhaustion of a hard day’s work. […] He became the red sedan. He was so busy parking that he forgot he had a car.
1,008
Ways to Track Time
(But zero ways to track the soul-crushing impact of a pointless meeting)
This culture of theater is fueled by a desperate need for visibility. In a remote or hybrid world, management is terrified of silence. Silence is interpreted as vacuum, and vacuum is interpreted as laziness. But silence is where the work happens. Silence is Nina P.-A. staring at a stack trace for 128 minutes until she finds the one misplaced semicolon that’s crashing the server. Management doesn’t want silence; they want the ‘ping.’ They want the notification. They want the visible artifact. So, we give it to them. We create the Gantt charts. We send the ‘just checking in’ emails. We perform the digital curtsey to prove we are still on the payroll. We’ve replaced trust with telemetry.
I’ve been guilty of it too. Last Tuesday, I spent 48 minutes formatting a PowerPoint slide to make the ‘ROI’ font look more aggressive. Why? Because I knew that if the slide looked ‘professional,’ nobody would ask me the 18 difficult questions about the actual data that I hadn’t had time to verify because I was too busy formatting the slide. It’s a self-perpetuating cycle of bullshit. We produce theater because we are judged on theater, and we judge on theater because we’ve forgotten how to measure actual value.
(Endless Sales Calls)
(Gets the Job Done)
There’s a directness we’re missing… It’s refreshing to find a path that cuts through that, like getting an RDS CAL without having to sit through a 58-minute webinar on the ‘future of connectivity.’ We need more hammers and fewer charts.
The Silence of Resolution
28 Minutes Muted
Recursive Loop Fixing
Commit Pushed
Architecture Redundant
The Follow-up
Marcus looked disappointed.
Nina P.-A. eventually unmuted herself […] She simply said, ‘The bug is fixed. I’ve pushed the commit. We can skip Phase 2 Alpha entirely because the architecture I rebuilt this morning makes it redundant.’ The silence that followed was heavy. It was the sound of a theater suddenly losing its lights.
The Binary Cost
We are terrified of the ‘Nina’ approach because it’s binary. It either works or it doesn’t. You can’t hide a failed commit behind a beautiful slide deck. Theater, on the other hand, is infinitely scalable. You can be the top performer in a company that is circling the drain, simply by being the best at the digital curtsey.
Finding the Hammer
I’m going to make a mistake today. I’m going to go to another meeting at 2:38 PM. I’ll probably even share my screen and show a spreadsheet. I’ll participate in the theater because the alternative-absolute honesty-is a fireable offense in most zip codes. But I’ll be thinking about Nina. I’ll be thinking about the quiet efficiency of a system that doesn’t need to explain itself.
Maybe the answer isn’t to abolish the meetings, but to start treating them like the expenses they are. If every meeting had a ticker in the corner showing the real-time cost in salaries, we might see a lot more ‘Ninas’ and a lot fewer ‘Marcuses.’ We might finally stop valueing the maneuver and start valueing the destination.
The next time someone steals my parking spot, I’ll try to remember that they probably just really, really need someone to notice they’ve arrived, because they haven’t actually done anything since they left home.