Hollow Rituals

The squeal of a smoke detector at 2:03 AM has a specific, jagged frequency that bypasses the rational mind and goes straight for the lizard brain. I was standing on a kitchen chair, half-blind from sleep, fumbling with a plastic casing that refused to yield. By the time I swapped the battery, my heart was hammering at 83 beats per minute, and the silence that followed wasn’t peaceful; it was heavy with the residual adrenaline of a false alarm. Fast forward to 9:03 AM, and I’m sitting in a circle of 13 people, feeling that same jagged irritation. It’s the daily stand-up. We are performing the ritual of the ‘three questions,’ but the atmosphere is as hollow as that empty battery casing. Everyone is lying. Not the malicious kind of lying, but the corporate kind-the glossing over of 43-hour delays and the pretending that ‘no blockers’ actually means we aren’t currently sinking.

We go around the circle. Mark says he’s working on the API integration. Sarah says she’s waiting on feedback. Both of them know that the decision we need from leadership has been sitting in an inbox for 23 days, unread. But we don’t say that. We say ‘no blockers.’ We play the part. This is the Agile Masquerade, a performance art piece funded by a $153-an-hour burn rate per developer, where the goal isn’t to move fast, but to look like you’re moving fast.

Yuki J.P., a dark pattern researcher I’ve followed for years, once pointed out that the most effective traps are the ones you build for yourself. She calls them ‘voluntary cages.’ Yuki argues that these rituals, when stripped of their underlying trust, become a form of psychological dark pattern. They give the illusion of autonomy while reinforcing a rigid, top-down control that would make a 1923 factory foreman blush.

Agency vs. Illusion

I’m staring at the Jira board on the screen. There are 233 tickets in the backlog that will never see the light of day. They are ghosts of ideas we had three months ago, preserved in digital amber. We talk about ‘pivoting’ and ‘sprints,’ but the reality is a slow, grinding crawl through molasses. The contradiction is what kills you. You’re told you are ’empowered’ to manage your own work, yet you have zero agency to change the systemic failures that make that work impossible. It’s like being given the keys to a car but finding out the steering wheel is just a plastic toy glued to the dashboard. You can turn it all you want; the car is still going where the invisible driver wants it to go.

This creates a specific kind of cognitive dissonance. It’s the stress of the ‘pretend’ empowerment. When you are a cog in a machine, you know you’re a cog. There’s a certain grim honesty in that. But when you are told you are an ‘owner’ while being treated like a child who can’t be trusted to manage their own time without a 9:03 AM status check, your brain starts to misfire. I found myself grinding my teeth during the retro yesterday. We spent 53 minutes talking about how to improve our ‘velocity’ without once mentioning that the product owner hasn’t shown up to a meeting since 2023.

“

autonomy without agency is just a fancy word for gaslighting

– Observation

Somatic Cost

My neck is a column of tension. It’s that same feeling I had on the kitchen chair at 2:03 AM-the sense that something is wrong, but the tools I have to fix it are inadequate. This isn’t just a management problem; it’s a physiological one. The body doesn’t know the difference between a smoke detector and a failing project if both trigger the same sense of helplessness. We carry these corporate scripts in our trapezoids and our jawlines. I’ve noticed that after these ‘rituals,’ I spend the next 13 minutes just staring at my monitor, unable to code a single line because the mental energy required to maintain the lie of the stand-up has drained my battery.

It’s fascinating how we’ve turned ‘transparency’ into a weapon. In the original Agile Manifesto-which, let’s be honest, almost no one in this room has actually read in its entirety-the focus was on individuals and interactions over processes and tools. Now, the process is the only thing that survives. We have tools that track every 3-second movement of a cursor, yet we can’t have a 3-minute honest conversation about why the project is failing. We’ve optimized for the appearance of progress at the expense of actual movement.

Yuki J.P. once joked that the most successful Agile transformation she ever saw involved a team throwing their Jira board into a digital incinerator and just talking to each other over coffee. They didn’t have a stand-up; they had a conversation. They didn’t have a retro; they had a post-mortem with actual consequences. I think about the physical cost of this theater. The way the shoulders hitch up toward the ears whenever someone says the word ‘synergy’ or ‘alignment.’ We are literally shaping our bodies around the stress of pretending. In the tech world, we often ignore the somatic reality of our work. We think we are just floating heads in Zoom boxes, but the tension is real. It’s why so many of us end up seeking out practitioners like those at acupuncturists East Melbourne, trying to unknot the physical manifestations of 43 unaddressed blockers and 13-minute status reports that should have been emails. You can’t ‘sprint’ if your muscles are permanently locked in a fight-or-flight response.

The Silent Betrayal

There was a moment during today’s stand-up where I almost broke the script. The Scrum Master asked if anyone had any ‘impediments.’ I looked at the 13 faces on my screen, all of them slightly pixelated, all of them wearing that same mask of tired compliance. I wanted to say, ‘Yes, the impediment is that we are all pretending this timeline is realistic when we know it’s 73 days behind schedule.’ I wanted to say, ‘The impediment is this meeting.’ But I didn’t. I looked at the clock-it was 9:23 AM-and I said, ‘No blockers from my side.’ I watched the little green checkmark appear next to my name in the software. I felt a wave of nausea, a tiny betrayal of my own integrity that I’ve committed at least 33 times this month.

Why do we do it? Because the alternative is ‘not being a team player.’ So we keep sewing the invisible clothes, and we keep complimenting the thread count. It’s a survival mechanism. If you can’t change the system, you learn to mimic its sounds so the predators don’t notice you.

We’ve traded the messiness of human collaboration for the cleanliness of a dashboard that tells us nothing but lies we want to hear. What happens when the spirit dies but the ritual remains? You get a ghost. A ghost ship of a company, sailing toward a destination that no longer exists, manned by a crew that is too busy updating their tickets to notice the water rising in the hold. We need to stop equating ‘activity’ with ‘progress.’ A hamster on a wheel has high velocity, but its displacement is zero. Most of our ‘sprints’ are just wheels. We are running as fast as we can to stay in the exact same place, fueled by caffeine and the fear of being the first one to stop running.

Addressing the Sensor

The 2:03 AM smoke detector incident taught me something about false alarms. When the alarm goes off and there’s no fire, you don’t just leave it be. You fix the sensor. You change the battery. You address why the system is screaming at you for no reason. In the corporate world, we’ve gotten so used to the screaming that we’ve just started wearing earplugs. We’ve accepted the ‘high-priority’ alerts and the ‘urgent’ stand-ups as a baseline background noise. But that noise has a cost. It erodes the ability to distinguish between a minor glitch and a total system failure.

By the time the real fire starts, we’ll probably just mark it as a ‘blocker’ and go back to our 9:03 AM status update, waiting for the 13th person in the circle to tell us that everything is fine.