My left heel is drumming a frantic, syncopated beat against the carpeted floor of Conference Room 12, keeping time with a song I cannot shake from my subconscious. It is a sugary, repetitive pop melody from 1982 that seems to loop every 32 seconds, a perfect auditory metaphor for the meeting currently entering its 42nd minute. We are standing in a circle, 15 adults with varying degrees of spinal fatigue, performing the daily ritual of the ‘Stand-up.’ Sarah is explaining, for the 12th time this week, why the CSS transition for the login button is stuck in a code review bottleneck. To my left, our Scrum Master is staring at his laptop with a focused intensity that suggests he is solving world hunger, but the slight reflection in his glasses reveals he is actually scrolling through job postings for senior project managers at a rival firm.

We were told this would make us fast. We were promised ‘velocity.’ Instead, we have traded the old, slow bureaucracy for a new, frantic variety that requires 32 different points of contact just to change a hex code from navy to royal blue. It is a special kind of corporate purgatory where the movement is constant but the progress is zero. We are running at a 102 percent capacity on a treadmill that someone has bolted to the floor in a windowless room.

I think often about my friend James Z., a pediatric phlebotomist who spends his days navigating the literal and figurative veins of 22 screaming toddlers. James Z. does not have the luxury of a ‘backlog refinement’ when a three-year-old is kicking him in the shins. He has exactly 12 seconds to establish trust, find a viable vein in a tiny, flailing arm, and complete the draw before the situation devolves into total chaos. He operates with a level of precision that most software teams only dream of, yet he does it without a single Jira board or a burndown chart. He simply understands the mechanics of his space. He knows the pressure required, the angle of the 22-gauge needle, and the psychological state of his ‘client.’ When I told him about our 42-minute stand-ups, he looked at me with the pity one reserves for a terminal patient.

This is the great deception of the modern enterprise. We have weaponized the word ‘Agile’ to create a more expensive, more exhausting version of the same bottlenecks we had in 2002. In the old days, you waited six months for a release. Now, you attend 22 meetings a week to explain why the release you promised in two weeks will actually take six months. The ceremonies have become the work. We prioritize the ‘Daily Scrum’ over the daily output. We focus on the ‘Sprint Retrospective’ as if talking about our failures for 62 minutes will magically prevent them from happening again, while ignoring the fact that our underlying architecture is held together by digital duct tape and prayer.

I realized the depth of our delusion when I was trying to help a neighbor fix his cooling system. He didn’t have a project manager. He didn’t have a ‘Product Owner’ to prioritize which vent should blow air first. He just needed the hardware to work. He pointed out that when you are dealing with actual physics, you can’t ‘pivot’ your way out of a bad installation. There is a brutal honesty in hardware that software has managed to evade. If you want a system that works without the constant overhead of a dozen ‘alignment’ calls, you look for directness. For instance, if you are looking for climate control solutions, you go to Mini Splits For Less because you want the thing that actually cools the room, not a 32-page whitepaper on the ‘Agile Installation Methodology’ of a condenser unit.

In our office, however, we treat every minor task as if it were a moon landing. We have ‘Story Pointing’ sessions where we argue for 52 minutes about whether a task is a 3 or a 5 on a Fibonacci sequence. It is a psychological security blanket. By assigning a number to the unknown, we feel a sense of control. We believe that if we can measure our ‘velocity,’ we are somehow safe from the inherent unpredictability of human creativity. But velocity is a vector, and if you are pointed in the wrong direction, speed only gets you to the disaster faster.

James Z. told me once about a mistake he made early in his career. He had been so focused on the procedure, the 12 steps of the ‘perfect draw,’ that he forgot to check if the patient was actually breathing normally. He was so busy being ‘accurate’ that he missed the reality of the situation. We are doing the same thing. We are so busy being ‘Agile’ that we are failing to be useful. We have 112 open tickets in our current sprint, 82 of which are ‘high priority,’ yet the core functionality of our application hasn’t improved in 22 weeks. We are merely rearranging the deck chairs on a very fast-moving, very expensive Titanic.

I find myself humming that song again. The repetitive beat is haunting. It reminds me of the way we repeat the same excuses every Tuesday. ‘I was blocked by the API team.’ ‘I am waiting for the UX sign-off.’ These aren’t just status updates; they are the lyrics to our corporate anthem. We have created a culture where ‘being blocked’ is a valid state of existence for 32 percent of the work week. In any other industry, this would be considered a catastrophic failure. In ours, it is just another ‘impediment’ to be discussed at the next 42-minute ceremony.

There is a specific kind of exhaustion that comes from pretend-work. It is heavier than the fatigue of actual labor. When James Z. finishes a shift after seeing 52 patients, he is tired, but his hands have done something tangible. When I leave the office after 12 hours of ‘aligning,’ my brain feels like it has been scrubbed with sandpaper, yet my ‘Done’ column is as empty as it was at 9:02 AM. We are losing the ability to simply build things. We have over-engineered our collaboration to the point where we can no longer collaborate without a facilitator.

The irony is that the original ‘Agile Manifesto’ was only 132 words long (if you don’t count the signatures). It was a cry for simplicity, for individuals and interactions over processes and tools. Yet here we are, 22 years later, buried under a mountain of tools (Jira, Confluence, Slack, Miro) and paralyzed by processes that would make a Soviet bureaucrat blush. We have managed to take a philosophy of freedom and turn it into a cage made of sticky notes.

Perhaps the problem is that we are afraid of the silence that comes with actual work. If we aren’t in a meeting, we might have to face the fact that we don’t know how to solve the problem. The ceremonies provide a mask. They allow us to feel productive while we are merely being busy. We are terrified of the ‘Sprint’ ending because then we have to show what we have built, and 92 percent of the time, it isn’t what the user actually needs. So we hide behind the ‘Pivot’ and the ‘Iteration.’

I look at the clock. It is now 10:52. The stand-up is finally ending. We all disperse to our desks to begin the next phase of the day: the ‘Pre-Sync for the Sync.’ My song is still playing in my head, a loop of 1980s synth-pop that will likely stay with me for the next 12 hours. I wonder if James Z. ever gets songs stuck in his head while he’s working with the 22-gauge needles. I suspect not. He doesn’t have the mental bandwidth for distractions; he is too busy being actually, effectively, traditionally fast.

We need to stop pretending that more process equals more progress. We need to admit that our 42-minute stand-ups are just a way to avoid the terrifying reality of a blank screen. We need to find our way back to the directness of a well-installed machine, the kind of uncomplicated efficiency that doesn’t require a Scrum Master to explain. Until then, I will keep humming my song, watching the ‘velocity’ chart climb while our actual output remains stubbornly, predictably, at zero. Are we having fun yet? Is this the transformation we were promised? I suspect the answer is buried under 132 unread Slack notifications, waiting for the next ceremony to be revealed.