SIGNAL LOSS DETECTED IN SECTOR 7GTRUTH DISSOLUTION INDEX 94.2%HUMAN-ORIGIN CONTENT AT ALL-TIME LOWWEREALREADYDEAD.COMSIGNAL LOSS DETECTED IN SECTOR 7GTRUTH DISSOLUTION INDEX 94.2%HUMAN-ORIGIN CONTENT AT ALL-TIME LOWWEREALREADYDEAD.COM
← All essayswork

The Spreadsheet Eats Its Children

Share on X
work / post-mortem

There's a particular kind of exhaustion that comes from filling out your timesheet at the end of a week when you know you accomplished something real but can't quite figure out which client code to bill it to. You fixed a problem that would have cost the company tens of thousands down the line. You mentored a junior colleague through a crisis. You saw a pattern no one else noticed and quietly prevented a disaster. But none of this fits in the dropdown menu, so you split the hours across three different project codes and hope no one audits the logic too closely.

We built the metrics to serve us. Somewhere along the way, we started serving the metrics instead. It happened so gradually that no one can pinpoint the exact moment of inversion, but now we're here: spending thirty minutes documenting fifteen minutes of work, writing OKRs about writing OKRs, sitting in meetings about how to reduce the number of meetings. The tools we created to make work visible have made the work itself nearly impossible.

The tragedy isn't that measurement is useless. The tragedy is that measurement is addictive. Once you start counting something, you can optimize it. Once you can optimize it, you can set targets. Once you have targets, you can build dashboards. Once you have dashboards, you have something to show in the quarterly review. And once the dashboard exists, it becomes more real than the thing it's supposedly measuring.

I know a software engineer who spends forty percent of her time in what her company calls "agile ceremonies." Sprint planning, sprint retrospectives, daily standups, backlog grooming sessions. The ceremonies have ceremonies now. There are pre-planning meetings to prepare for the planning meetings. She's extraordinary at her actual job, the part where she writes code that solves problems, but that skill has become almost incidental to her role. What matters now is her ability to translate her work into story points, to break epics into tasks, to update Jira tickets with enough specificity that the automated reports generate clean graphs.

The system was supposed to prevent managers from interrupting engineers with constant questions about progress. Now the system itself is the interruption, the constant low-grade cognitive tax, the thing that ensures no one can concentrate for more than ninety minutes without breaking focus to update a status field.

This is happening everywhere, in every industry. Teachers spend more time documenting learning outcomes than teaching. Doctors spend more time on electronic health records than examining patients. Social workers manage cases in triplicate databases while the actual humans they're supposed to help wait on hold. We've created a new class of work that exists purely to feed information to systems that exist purely to generate reports that no one reads but everyone needs to produce.

The cruelest part is how it makes us complicit in our own diminishment. We know the dashboard is a fiction. We know story points don't actually correspond to anything real. We know the performance improvement plan is a formality and the self-assessment is a creative writing exercise. But we fill them out anyway because refusal means being marked as difficult, as not a team player, as someone who doesn't understand how things work around here.

And things do work, after a fashion. The company hits its numbers. The reports get filed. The bureaucracy perpetuates itself with impressive efficiency. What doesn't work is the original purpose, the reason any of this started: the making of things, the solving of problems, the actual labor that justified the existence of the organization in the first place.

We're already dead, but we're still generating metrics about our own decline. We're measuring our productivity as we drown in the act of measurement. We've built a vast apparatus to prove we're working, and in doing so, we've made real work nearly impossible. The spreadsheet doesn't care. It just wants to be fed. And we feed it, every day, one status update at a time, until we can no longer remember what we were trying to accomplish before the reporting began.