My finger hovered over the red ‘end call’ button for 19 milliseconds too long, and then, in a fit of clumsiness that could only be described as a subconscious cry for help, I clicked it. I hung up on my boss right as he was asking for the 49th time why the ‘user story’ for the login button wasn’t in the ‘done’ column. The silence that followed in my home office was heavy, thick with the smell of cold coffee and the realization that I didn’t actually care to call him back. It was a mistake, technically, but it was also the most honest thing I’ve done in a sprint. My trackpad has been acting up, or maybe my soul has. Either way, the Zoom window vanished, leaving me staring at my own tired reflection on the glass.

1. The Cargo Cult of Process

Pierre K.-H., a friend of mine who describes himself as a meme anthropologist, often watches my career with the detached fascination of a man observing a slow-motion train wreck. Pierre believes that modern corporate Agile is actually a form of ‘cargo cult’ behavior. He points out that we build the runways and wear the headphones, waiting for the planes of productivity to land, but the planes never come because we forgot that the runways need to actually lead somewhere.

Confession, Not Collaboration

During our stand-ups, we don’t collaborate; we confess. It’s a secular confessional where we tell the priest-the Project Manager-what sins of inactivity we committed the day before. ‘I worked on the CSS,’ someone says. Translation: ‘I stared at a hex code for three hours and then took a nap.’ The Project Manager, Dave (there is always a Dave, and he always looks like he’s perpetually waiting for a flight that’s been delayed), types these snippets into a spreadsheet. He isn’t listening to the technical hurdles. He’s looking for keywords to satisfy a dashboard that

89 stakeholders

in upper management look at once a quarter and never understand.

“

When the methodology of empowerment was co-opted by a culture of absolute control, it became a weapon. It’s a micromanagement system disguised as a ‘community-driven workflow.’

This is where the trust died. We are told we are autonomous, yet we cannot change a font size without a 39-point checklist and a peer review from someone who hasn’t coded since 2009. I once saw a developer spend 19 hours defending a two-line change because it ‘didn’t align with the sprint goals,’ even though it fixed a bug that was costing the company $1499 an hour. The goal was the process, not the product.

2. The Documentation Becomes the Work

I remember when Pierre K.-H. showed me a meme of a dog in a burning house, but the dog was wearing a ‘Scrum Master’ hat and the speech bubble said, ‘But did we update the Jira?’ It hit too close to home. We’ve reached a point where the documentation of the work is more important than the work itself. If a feature is released but there isn’t a corresponding ticket with a ‘Story Point’ value of at least 5, did the feature even exist? Probably not in the eyes of the 29 managers who live and die by their velocity charts. They want to see the line go up. They don’t care if the line represents quality or just a bunch of people inflating their estimates to avoid being yelled at during the retrospective.

The Nirvana of Disengagement

Speaking of retrospectives, they are the most surreal of all the ceremonies. We sit in a virtual room and pretend to be ‘vulnerable’ about our failures. We use digital sticky notes. I watched Pierre K.-H. pull up a high-definition stream on a massive screen, the kind you’d find at Bomba.md, just to show me the pixelated despair in a ‘success story’ corporate video. He pointed at a woman smiling in the background. ‘She’s thinking about her grocery list,’ he said. ‘She has reached Nirvanna through total disengagement.’

That disengagement is the hidden cost. When you treat experts like factory workers who need to be monitored every 24 hours, they stop acting like experts. They start thinking about the ticket. I’ve seen brilliant engineers turn into ‘ticket-closing machines.’ They don’t care if the architecture is crumbling as long as their individual velocity is high. It’s a survival mechanism. If the system rewards the appearance of progress over actual progress, you get a lot of shiny, broken things.

3. The Coup: Measurement as Control

4. The Ghost in the Machine

I’m waiting to see how long it takes for someone to notice I’m gone. In an ‘Agile’ environment, you’d think it would be immediate. But because I’ve already updated my tickets for the day with vague, optimistic progress bars, the system thinks I’m still there. I am a ghost in the machine, and the machine is happy as long as the data looks consistent. My ‘Story Points’ are assigned. My ‘Tasks’ are in progress. For all the dashboard knows, I am a model employee.

We have traded the joy of craftsmanship for the safety of the schedule. It’s a recursive loop of inefficiency. I once made a mistake and accidentally deleted a staging database. I felt more alive in the 29 minutes it took me to fix it than I did in the three months of ‘successful’ sprints that preceded it. At least then, the stakes were real. The feedback was immediate.

The Way Back: Quiet Work

We need to stop. We need to burn the digital sticky notes and look at each other. If we have nothing to say, we shouldn’t say anything. If the process is getting in the way, we should kill the process. But that requires trust, and trust is hard to scale. It’s much easier to buy a software subscription that promises ‘Full Visibility’ for $9999 a month than it is to actually trust your developers to do their jobs.

✓

It will be found when we realize that the most ‘Agile’ thing you can do is often to just sit down, shut up, and build something worth having.