The Cost of Performance Theater

Pressing the ‘Mute’ button feels like a small mercy, a tiny digital sanctuary where I can exhale the stale, recycled air of the boardroom without being heard by the 177 other participants. On the screen, a consultant with a remarkably symmetric face is explaining the ‘Five Pillars of Agile Resilience.’ It is the 47th minute of a presentation that was supposed to take 17. The irony is so thick I can almost taste it-a metallic, bitter flavor reminiscent of a penny held under the tongue. We are currently spending approximately $10007 in collective hourly wages to talk about how we can save five minutes on Monday mornings. It’s a performance, a high-stakes theater of productivity that ignores the fact that our actual operational software looks like it was coded in a basement in 1997.

I look over at Carter R., who is currently toggling between three different screens. Carter is a virtual background designer by trade, a man whose entire career is built on the necessity of hiding reality. He’s meticulously touching up a ‘modern loft’ aesthetic for the VP of Logistics, blurring the pile of laundry and the unwashed coffee mugs in the background. Carter once told me that 87% of his clients don’t actually want a better office; they just want to look like they have one. That’s the corporate condition in a nutshell. We spend millions on the ‘background’ of our workflows-the consultants, the workshops, the team-building retreats-while the actual ‘desk’ where the work happens is collapsing under the weight of legacy code and manual data entry.

The Rooster in the Chapel: Friction as Ritual

We do this in business every single day. We set up these solemn, sacred processes-the ‘Standard Operating Procedures’ that span 247 pages-and then we act surprised when the rooster crows. The rooster, in this case, is the fact that our team is still manually reconciling invoice data across two separate, non-integrated systems. We spend 37 hours a week on ‘data integrity’ meetings, but we won’t spend the capital to buy a system that integrates the data automatically. We blame the user. We say Bob in accounting needs to be ‘more detail-oriented.’ We say Sarah in dispatch needs to ’embrace the new workflow.’ We never stop to ask why the workflow requires Sarah to have the patience of a saint and the data-entry speed of a cyborg.

It’s psychologically easier to talk about changing human behavior than it is to commit to changing the technological infrastructure that shapes that behavior. If we blame the tool, the problem is systemic. It requires a budget. It requires an admission that the leadership made a poor investment five years ago. It’s a terrifying prospect for someone whose entire identity is tied to being a ‘shrewd decision-maker.’ So, we keep the broken tools and try to ‘optimize’ the humans using them. It’s like trying to win the Indy 507 by teaching the driver how to meditate while they’re sitting in a 1987 Yugo.

The Infrastructure Blind Spot

The friction is where the profit dies. In transportation logistics, this is a terminal illness. You have companies that move 777 loads a month, yet their back-office staff is drowning in manual verification. They’ll hire a ‘Workflow Specialist’ for $97 an hour to tell them their filing cabinets should be color-coded, but they won’t look at a platform like

best factoring software that actually automates the bottleneck. It’s a strange form of blindness. We are so focused on the ‘how’ of the work that we forget the ‘with what.’

Carter R. finally finishes the virtual background. The VP now looks like he’s sitting in a glass-walled office overlooking a digital Tokyo. In reality, I know he’s in a spare bedroom with a leaking radiator. We’ve become experts at this digital camouflage. We use Slack to announce that we’re ‘circling back’ on a project that hasn’t moved in 17 days because the software crashed and deleted the progress. We use Trello boards to track the ‘velocity’ of a team that is currently stuck in the mud of a manual billing process. We have all the ornaments of a high-functioning, modern enterprise, but the engine is seized.

The Developer’s Dilemma: Time vs. Capital

I remember a conversation with a developer who had been tasked with ‘optimizing’ a legacy database for a major shipping firm. He found that the average search took 37 seconds. He proposed an indexing strategy that would bring it down to 7 seconds. The management was thrilled. But he told me, privately, that if they just replaced the 27-year-old server, the search would take 0.007 seconds. When he suggested the hardware upgrade, he was told it ‘wasn’t in the budget.’ They would rather pay a developer $127,000 a year to shave off 30 seconds than spend $7,000 on a server that would solve the problem entirely.

This is the ‘sunk cost’ of human effort. We value the struggle. But there is no nobility in manual labor that can be done better by a machine. That’s not work; that’s a tax on existence. It’s a drain on the creative energy of your best people. Eventually, the Sarahs and Bobs of the world realize that their talent is being used to bridge the gaps in your shitty software, and they leave. They go to the companies that have already figured out that tools define the ceiling of human potential.

I’ve made this mistake myself. Years ago, I tried to manage a team of 17 writers using a complex system of spreadsheets and manual check-ins. I was ignoring the fact that the writers hated the spreadsheet. I was trying to optimize their compliance with my bad tool instead of just getting a project management app that they actually liked using. I was the rooster crowing at the funeral, and I didn’t even know it.

The Cumulative Tax on Existence

The cost of this friction is cumulative. It’s the 17 minutes lost here and the 7 minutes lost there. Over a year, for a company of 107 people, that’s thousands of hours of human life poured into a void. If you saw that much money being physically burned in the parking lot, you’d call the fire department. But because it happens silently, one mouse click at a time, we call it ‘the cost of doing business.’ We’ve normalized the broken tool.

Conclusion: Defining Potential

As the ‘Agile Resilience’ meeting finally wraps up (at the 107-minute mark), the consultant asks if there are any questions. The silence is heavy. Carter R. has his camera off now, probably actually doing the work he was supposed to be doing two hours ago. I want to ask why we are training people to be better at using bad software instead of just getting software that works. But I don’t. I just click the ‘Leave Meeting’ button. I start the manual reconciliation process, one line at a time, wondering if anyone else can hear the rooster crowing.