Sweat is pooling in the small of my back as the Jira notification pings on a screen I shouldn’t even be looking at while suspended 318 feet above the dirt. My harness is digging into my thighs with the weight of a dozen specialized tools, and the wind is whipping around the nacelle with a 48-mile-per-hour ferocity that makes the entire structure groan. But my phone, tucked into a secure pocket, vibrated with that specific, insistent pulse that signals a ‘high priority’ update. I shouldn’t have checked. I know I shouldn’t have checked. I’m currently trying to diagnose a bearing failure that could cost the grid $8,888 in downtime every single day it remains offline, yet here I am, looking at a digital sticky note from a project manager who hasn’t seen a sky clearer than an office window in 18 years.

I’m still thinking about it as I reach for a wrench, my thumb accidentally twitching over the screen. It’s the same thumb that, 58 minutes ago, accidentally liked a photo of my ex-partner from 2018. The shame of that digital slip-up-that tiny, irreversible evidence of lurking-is currently competing with the frustration of this Jira ticket. I am 318 feet in the air, and I am still haunted by the ghosts of administrative performance and social media blunders.

Productivity Theater: The Ritual of Busyness

It’s Friday afternoon, and while I’m up here battling literal grease and gravity, the rest of the team is likely huddled in a conference room or a Zoom square, spending 488 minutes a week discussing how to be more efficient. They are updating tickets, filling out color-coded spreadsheets, and preparing slide decks that summarize the progress of other slide decks. This is the heart of Productivity Theater. It’s the ritualized performance of being ‘busy’ to mask the terrifying reality that we have forgotten how to measure actual output. We have traded the tangible for the representational. A middle manager’s value is often tied to the volume of reporting they generate, not the problems they solve. If they stop asking for updates, they stop having a function. So, they create more layers of visibility, which in turn forces the people doing the actual labor to stop working so they can report on why they aren’t working.

Greta P.-A. is my name, by the way. I’ve spent 1008 days of my life climbing these white pillars. I know the sound of a failing yaw drive better than I know the sound of my own mother’s voice lately. To me, productivity is a spinning blade. It’s a closed circuit. It’s a humming transformer. But to the system I report to, productivity is a ‘Completed’ status on a task that says ‘Investigate Noise.’ I could spend 18 hours actually fixing the noise, but if I don’t click that button, the system registers me as a failure. Conversely, I could do absolutely nothing but update my status every 48 minutes, and the system would see me as a model of consistency and engagement. We are incentivizing the theater, and then we wonder why the stage is collapsing under the weight of the props.

The Economy of Metrics

This shift from an outcome-based economy to a performance-based one is a slow-motion car crash. In an outcome-based world, you either fix the turbine or you don’t. In a performance-based world, you attend the ‘Turbine Fix Planning’ meeting, you contribute to the ‘Maintenance Synergy’ Slack channel, and you document your ‘Continuous Improvement Journey.’ You can be highly ‘productive’ in this ecosystem without ever touching a piece of hardware. It’s a hall of mirrors where we justify our existence by creating work for each other. I’ve seen 8 different project management methodologies implemented in the last 28 months, and each one claimed to ‘streamline’ our workflow. Each one actually added an average of 78 minutes of administrative overhead to my daily routine.

You’re probably reading this while ignoring a notification yourself. Maybe it’s a Slack ping, or an email with ‘URGENT’ in the subject line that actually just contains a link to a survey about office snacks. We are all complicit in this dance because we’re afraid of the silence that comes when the theater stops. If we aren’t performing, are we even working? The irony is that the more we track, the less we know. We have more data than ever, but we have less understanding of the ground truth. We know the ‘velocity’ of our Jira tickets, but we don’t know why the morale is in the basement.

I remember a specific instance, about 38 weeks ago, where I was told to stop a critical repair because the ‘reporting protocol’ hadn’t been established for that specific fault code. I sat in my truck for 48 minutes, staring at a broken machine I knew how to fix, while three people in a different time zone debated which category it should fall under in the database. That was the moment the veil lifted for me.

I realized then that my expertise wasn’t the product; my compliance with the tracking system was the product. My actual skills-the ability to climb, to diagnose, to repair-were just the raw material used to feed the administrative machine. When you find a partner like

Done your way services, you realize that there are still corners of the world that prioritize the actual fix over the paperwork. They understand that a result isn’t a checkmark on a screen; it’s a physical reality that stays fixed long after the laptop is closed.

Transparency as Weaponry

We’ve reached a point where ‘transparency’ has become a weapon. It’s not about seeing what’s happening to help; it’s about surveillance to justify a layer of management that has lost touch with the craft. They want to see my GPS coordinates, my wrench torque settings, and my heart rate, not because they care about the turbine, but because data is the only language they speak. If it isn’t quantified, it didn’t happen. But how do you quantify the intuition of a technician who hears a vibration and knows, instinctively, that a bolt 18 feet above her is loose? You can’t. So you ignore the intuition and focus on the data point that shows she spent 8 minutes ‘idle.’ That idleness was actually the work. That was the thinking, the listening, the diagnosing. But the theater demands action. It demands clicking. It demands movement, even if that movement is just spinning in circles.

The Digital Abyss

I’ve spent 58 percent of my time this week on ‘internal coordination.’ That is a fancy way of saying I’ve been talking about work instead of doing it. And I’m a technician! Imagine what the ratio is for someone in a creative or analytical field. They must be drowning in the noise. It’s like trying to run a marathon while someone is constantly stopping you to ask for a status update on your heart rate and your distance covered. You’ll never finish the race because the reporting on the race has become the race itself.

There is a deep, resonant exhaustion that comes from this kind of theater. It’s different from the physical fatigue I feel after climbing 18 turbines in a week. That physical tiredness is honest. It’s the result of effort expended on a real object. The exhaustion from Productivity Theater is a hollow, draining sensation. It’s the feeling of being a cog that isn’t actually turning anything.

Reclaiming the Red Dashboard

If we want to fix this, we have to start by admitting that visibility is not the same as productivity. We have to stop rewarding the people who are best at the software and start rewarding the people who are best at the job. We need to cut the 18-minute ‘quick syncs’ that turn into 48-minute ‘deep dives.’ we need to give people the space to be ‘idle’ so they can actually think. But mostly, we need to stop being so afraid of what happens when the dashboard isn’t perfectly green.

A perpetually green dashboard is a sign of a well-rehearsed play. It’s a sign that the actors have learned how to hide the flaws to keep the audience-the stakeholders-from getting restless.

The Final Rotation

I’m coming down from the nacelle now. My hands are stained with a mixture of grease and dust that won’t come off for 8 days. I have fixed the bearing. I have ensured that 2800 homes will have power tonight. I still haven’t updated the Jira ticket. I think I’ll leave it ‘In Progress’ for another 48 hours, just to see if anyone notices the turbine is spinning before they notice the digital light hasn’t changed. I want to see if the outcome still carries more weight than the performance.

In the end, the wind doesn’t care about our status reports. The turbine doesn’t care about our synergy. The only thing that matters is the rotation.

Does your current workload actually produce something, or are you just a very busy actor in a very expensive play?