The Pointless Scrutiny
Dave’s neck was cramping, pressed against the cold aluminum housing of the monitor arm. It wasn’t the kind of deep, satisfying ache you get from hauling cinder blocks or solving a truly impossible problem. It was the shallow, repetitive strain of fiddling with minutiae-the exact kind of pain that whispers: this is pointless.
He wasn’t tracking down the missing parts shipment, which was the actual problem sinking the Q3 launch by three weeks. No. He was scrutinizing the hex code for a shade of slate gray that looked slightly more “serious” than the default PowerPoint template gray. He needed C2C2C2, perhaps, or was it D1D1D1? The project was dying, choking on bureaucratic neglect, but the deck-the tombstone that would explain its demise-had to look professional. It was 7:00 PM, and Dave was performing.
This is the dark secret of modern work. The output we are judged on is no longer the outcome itself, but the artifact detailing the outcome. We have substituted productivity with Productivity Theater, and the audience demands a five-star review, regardless of whether the structure holds.
The Allure of Legible Effort
It’s a simple, crushing dynamic: when real impact is complex, delayed, or invisible, we gravitate toward metrics that are immediate, legible, and easy to grade. Why spend 100 hours fixing the root cause when you can spend 10 hours generating a custom visualization that promises a 41% reduction in future friction?
The Friction Reduction Proxy
This performance culture actively, ruthlessly punishes quiet competence-the person who simply fixed the code and moved on, without generating an accompanying 17-slide narrative explaining the heroism of their commit, looks like they did nothing at all.
I catch myself doing it, too… I do it anyway. The pressure to conform to the visible standard is almost physically overwhelming.
The Beautiful Failure Report
It reminds me, annoyingly, of the physical world. Just yesterday, I nearly dislocated my shoulder trying to open a pickle jar. An utterly trivial task that somehow required brute, theatrical effort, ending in embarrassing failure. It felt like that jar was designed not to be opened, but to demonstrate my futile struggle. The corporate equivalent is spending eight hours trying to force a messy, ambiguous outcome into a clean, simple metric that fits neatly into the QBR template.
His reports were exquisite narratives of inevitable collapse. He didn’t use the default corporate template; he had a custom layout designed-minimalist, stark, serious. His analysis was always precise to the last dollar, down to an inventory error of $231… The quality of the post-mortem made the board feel better about the disaster. It made them feel handled.
– On Pierre E.S., Bankruptcy Attorney
He wasn’t saving the physical business, the building, or the jobs. He was saving the reputation of the people who oversaw the demise. He was proving, visually, that the collapse was a sophisticated tragedy, not just negligence. The documents themselves became the last, valuable product.
The Engine
Work is judged by running status. Artifact is the outcome.
The Deck
Work is judged by aesthetic rigor. Artifact documents the process.
Take, for instance, a place that deals in hard, undeniable reality. A broken engine. A dented frame. The work done by specialists like those at
Diamond Autoshop cannot be faked. When you repair a car, the measurable success is tangible: the engine runs, the door closes smoothly, the chassis alignment is 100%. You can’t present a deck about potential alignment; the car either drives straight, or it doesn’t.
The Void Where Ambiguity Lives
But we, the information workers, operate in the ethereal space of data and ideas, where success is often ambiguous and the timeline for impact stretches across years. In that ambiguity, performance rushes in to fill the void. We become actors on a stage designed by Slack notifications and Jira ticket statuses. We are perpetually generating proxies for production.
The Feedback Loop of Visibility
Daily Standup
10 people, 15 minutes, same status reported 5 times.
Metric Adjustment
Spending time adjusting axes for visual clarity (the blue axis).
I once implemented a system designed to reduce unnecessary internal emails by 51%. The actual reduction, measured by server logs, was 47%. […] The effort spent ensuring the story looked like a 61% win far outweighed the effort of achieving the actual 47% win.
It sounds cynical, but it is deeply practical. If your promotion depends on your boss *believing* you are busy, rather than your actual output being independently verifiable, then the rational choice is to maximize the signals of business. The best product manager isn’t the one who ships the product silently and perfectly; it’s the one whose Slack channel generates 11 new updates every hour, creating a steady stream of performative competence.
The Sensory Memory of Competence
What happens when we spend so long polishing the mirror that we forget what we look like? We lose the sensory memory of competence. The quiet satisfaction of solving a hard problem-the mental click of the right code or the right sentence-gets drowned out by the noise of having to prove, constantly, that the click happened.
Resource Allocation on Visibility vs. Reality
I worry that we are breeding a generation of workers who are brilliant stage managers and terrible mechanics. They can design the perfect dashboard showing the health of the machine, but they wouldn’t know which end of the wrench to use to tighten the bolt. They are masters of the proxy.
But the proxy always lies, eventually. The polished failure report doesn’t prevent the financial ruin; it just sanitizes the experience. The beautiful slide deck doesn’t ship the product; it merely documents its delay in high definition.
Dave, hunched over his monitor, finally settled on D1D1D1. He sighed, stretched his cramped shoulder, and exported the PDF. It looked incredible. He was three weeks behind, but he was undeniably performing. And that, in our current economy, is the only metric that truly counts.
What if the only thing we ever produced was the performance itself?