The Liturgy of Inefficiency

Mark’s neck is turning a specific shade of arterial red that I’ve only ever seen in failed crossword grids when the 11-letter word for ‘despair’ refuses to cross with ‘hope.’ He is being interrogated. We are 31 minutes into what was supposed to be an 11-minute stand-up, and the Scrum Master is currently demanding to know why ticket #401 hasn’t moved from ‘In Progress’ to ‘Done.’ The air in the room is heavy with the scent of lukewarm espresso and the collective, silent prayer of 11 exhausted adults who just want to sit back down.

I am leaning against a whiteboard that hasn’t been properly erased in 21 days. My lower back is pulsing. I’ve reread the same sentence on my phone 11 times now, a Slack message from a developer who is currently standing 1 foot away from me but refuses to make eye contact. We are participating in a ritual. It is not a meeting; it is a liturgy. We have traded the messy, unpredictable brilliance of human creativity for the comforting, rigid architecture of a process that we no longer control. We are practitioners of a cargo cult, building wooden airplanes on a dirt runway, waiting for the gods of productivity to deliver the cargo of ‘efficiency’ that never quite arrives.

The Cathedral of Bureaucracy

I’ve spent most of my life as a crossword constructor, which means I understand the beauty of constraints. A 21×21 grid is a holy thing. It gives you boundaries. It tells you where you can go and where you cannot. But the difference between a crossword grid and the current iteration of ‘Agile’ project management is that the grid is designed to be solved by a human mind. Our current process seems designed to solve the humans themselves. We have fetishized the methodology until it became a religion, and in doing so, we have forgotten why we started building things in the first place.

In the beginning, back in 2001-a year that feels like it belongs to a different geological epoch-there were 17 men in a ski resort in Utah. They wrote the Agile Manifesto. It was a beautiful, radical document. It prioritized individuals and interactions over processes and tools. It prioritized working software over comprehensive documentation. It was a breath of fresh air in an industry that was suffocating under the weight of ‘Waterfall’ planning, where projects were mapped out 21 months in advance and almost always failed to meet the actual needs of the user.

But look at us now. We have taken those 41 words of wisdom and built a cathedral of bureaucracy around them. We have ‘Certified Scrum Masters’ who treat the daily stand-up like a high-stakes confession. We have ‘Sprint Planning’ sessions that last for 31 hours of cumulative human time, where we argue over ‘Story Points’ as if they were a real currency backed by gold, rather than arbitrary numbers we assigned to tasks while we were half-asleep. We have turned ‘responding to change’ into ‘perpetual chaos,’ and ‘customer collaboration’ into ‘constant, soul-crushing interruptions.’

The Prisoner’s Dilemma

I hate the process. I truly do. And yet, I find myself checking the Jira board 11 times an hour, making sure my little digital card is in the right column so that I don’t get ‘called out’ during the next prayer circle. It is a strange contradiction to live in a world where you despise the very thing that gives your day its structure. I criticize the rigidity of the 21-day sprint, but the moment a project doesn’t have a deadline, I float away into a sea of indecision. I am a prisoner who has fallen in love with the bars, or at least, a prisoner who has learned how to use the bars to keep from falling over.

There is a specific kind of exhaustion that comes from pretending to be ‘agile’ when you are actually stuck in a 101-car pileup. We use the language of speed-sprints, velocity, burn-down charts-while we are moving at the pace of a tectonic plate. We have 21 different Slack channels for a single project, and yet no one knows who is actually responsible for the final decision. We are so busy documenting our ‘agile journey’ that we have forgotten to actually walk the path.

The Drowning Analogy

I watched a junior developer, let’s call him Leo, try to explain that he couldn’t finish his task because the API documentation was wrong. The response from the manager wasn’t ‘Let’s fix the documentation,’ but ‘How did this affect your velocity for the current sprint?’ It was like watching a man drown and asking him if he’d properly logged his swimming hours in the 11-point font required by HR. The air in the office is stagnant, filtered through 11 different vents that haven’t been cleaned since 2001, making the briefest window of escape for a delivery from Auspost Vape feel like a pilgrimage to a holy site. It’s the only time we aren’t being tracked by a green dot on a screen.

Magical Thinking and the Lie of Effort

As a crossword constructor, I often have to deal with ‘dead ends.’ You place a word, and it seems perfect, but 11 steps later, you realize it has made the bottom-right corner impossible to solve. In a crossword, you have the humility to erase. You admit you were wrong, you pull back, and you start again. In the corporate ‘Agile’ world, we never erase. We just add more ‘Spikes.’ We add more ‘Refinement’ meetings. We layer more process on top of the broken process, hoping that if we just hold enough 11-minute ceremonies, the fundamental flaws in our architecture will magically resolve themselves.

It is a form of magical thinking. We believe that if we follow the rituals perfectly, we will be rewarded with success. If we stand up, we will be fast. If we use Post-it notes, we will be creative. If we have a ‘Retrospective,’ we will be better. But a retrospective is only useful if people are allowed to be honest, and in a culture of high-velocity performance, honesty is often seen as a ‘blocker.’ So we lie. We say everything is going great, we just had a few ‘unforeseen dependencies.’ We report that our 101% effort is being maintained, even as we are staring blankly at our monitors, rereading the same email 11 times because our brains have been fried by the sheer performative weight of it all.

I remember a time when ‘Agile’ meant that a small group of people who trusted each other sat in a room and solved a problem. There were no boards. There were no points. There was just the problem and the solution. Now, the problem is often secondary to the ‘Status’ of the problem. We have become accountants of our own effort, spending 31% of our time reporting on the other 71% of our work. The math doesn’t even add up, but that doesn’t matter as long as the chart is green.

The Category Error

We have turned software development into a factory floor, but we are trying to use the tools of a philosophy that was designed to liberate us from the factory. It’s a category error of the highest order. You cannot force ‘agility’ from the top down. It is something that happens in the gaps between the rules, in the moments when the ’11-minute stand-up’ breaks down into a genuine conversation between two people who actually care about the work.

I think about the year 2001 a lot. I think about those 17 men and whether they realize what they’ve done. They didn’t mean to start a religion. They meant to start a conversation. But conversations are hard to scale. They are hard to sell as a ‘Productivity Solution’ for $501 per seat. Rituals, on the other hand, are very easy to sell. You can package a ritual. You can certify someone in it. You can measure it. You just can’t use it to actually build something meaningful if the heart has been cut out of it.

The Uncontrolled Wind

Every morning at 9:21 AM, we gather. We stand. We recite our three questions: What did I do yesterday? What will I do today? Are there any blockers? We say the words, but we aren’t listening. We are just waiting for our turn to speak so we can prove that we aren’t the reason the project is failing. We are all holding our breath, waiting for the 31st minute to strike so we can return to our desks and finally, maybe, if we’re lucky, get 1 hour of actual work done before the next 11-person meeting starts.

Is this the way we were meant to create? Are we just units of ‘Value’ to be moved across a digital board, or are we still allowed to be the people who find the 11-letter word that makes the whole grid work? I look at Mark, whose neck is still red, and I realize that he isn’t the enemy. The Scrum Master isn’t the enemy. Even the Jira board isn’t the enemy. The enemy is our own desire to be in control of a process that is inherently uncontrollable. We are trying to map the wind. We are trying to grid the sea. And in our desperation to feel safe, we have built a church that no longer remembers the name of its god.

How many more ‘sprints’ will it take before we realize that we are just running in circles?