The red marker squeaks against the whiteboard, a sound that feels like a needle dragging across the 103 neurons I have left dedicated to this project. Marcus is mid-swing, drawing a jagged arrow that points toward a future we didn’t know existed until 13 minutes ago. We just spent 53 hours-true, grueling, caffeine-soaked hours-polishing the ‘Phase One’ release. It was beautiful. It was functional. It was, according to the Slack message Marcus received 3 minutes before this meeting, completely irrelevant. A VP on the 23rd floor had a dream, or perhaps a particularly vivid hallucination involving a competitor’s feature set, and now our ‘Agile’ workflow demands we incinerate our progress.

I’m sitting there, watching the ink dry, feeling that familiar, low-grade heat behind my eyes. It’s the heat of a won argument. Earlier this morning, I spent 43 minutes shouting down the lead architect about the database schema. I told him he was being too rigid, that he didn’t understand the ‘fluidity’ of our current roadmap. I was wrong, of course. I knew I was wrong by the time I hit the 23-minute mark of my monologue, but I had the momentum of a runaway freight train. I bullied him into a design that is objectively worse because it felt more ‘adaptable.’ Now, looking at Marcus’s new arrow on the board, the irony tastes like copper. We are so adaptable that we’ve lost the ability to actually arrive anywhere.

If you don’t know where you’re going, you might as well go there fast, right? That seems to be the logic in the ‘War Room,’ which is currently littered with 33 empty sparkling water cans and the shattered dreams of a dozen engineers. We call it ‘Iterative Development,’ but it’s really just ‘Management by Attention Deficit.’ We aren’t building a cathedral; we’re just moving a pile of bricks around the yard every morning because the foreman likes the way they catch the light in the southeast corner.

The Toxic Waste of Indecision

Natasha D. looked at that supervisor and told him that if he moved the tape one more time, she’d leave him in the splash zone without a respirator. In her world, ‘pivoting’ without a plan leads to 13-car pileups and environmental lawsuits. In our world, it just leads to burnout and 43-page post-mortems that nobody reads. But the damage is similar. You’re eroding the trust of the people who actually do the work. When you tell a team that their ‘top priority’ is a moving target, they eventually stop aiming. They just start firing into the air, hoping something falls.

Weaponizing the Manifesto

We’ve weaponized the Manifesto. We’ve taken the phrase ‘responding to change over following a plan’ and interpreted it as ‘having no plan whatsoever.’ It’s a convenient lie for leadership. It allows them to avoid the hard, terrifying work of making a choice and sticking to it. Strategy is about saying ‘no’ to 193 good ideas so that you can say ‘yes’ to one great one. But Agile, in its corrupted form, allows a company to say ‘yes’ to everything for 3 days at a time. It’s a revolving door of priorities that leaves everyone dizzy and nothing finished.

The Stability of Real Progress

It’s funny how we crave the ‘new’ and ‘flexible’ in tech, yet we ignore the fact that real progress usually looks like the opposite: boring, reliable, predictable systems. Think about something as traditionally fragmented and chaotic as booking a boat in a foreign country. For decades, that was a mess of handshakes and 23 different middlemen.

But when you look at how a platform like Viravira operates, they didn’t succeed by being chaotic. They succeeded by taking that chaos and wrapping it in a transparent, reliable, technology-driven process. They gave the user a predictable outcome in an industry that used to thrive on ‘playing it by ear.’ That’s the irony: the most successful companies are the ones that use technology to eliminate the very chaos that most managers use ‘Agile’ to justify. They use the speed of software to create stability, not to amplify the tremors of an indecisive executive.

Viravira

But back in the glass-walled conference room, stability is a dirty word. Marcus is now talking about ‘Velocity.’ Velocity is the favorite metric of the strategically bankrupt. It sounds like progress, but velocity is a vector, and a vector requires direction. If your velocity is 103 points per sprint but you’re running in circles, your displacement is zero. You’re just a very fast, very tired hamster.

The Theater of the Absurd

I look at the 13 people in the room. Most of them are staring at their laptops, likely polishing their resumes or playing 3-dimensional chess. They’ve checked out. They know that whatever we decide today will be overturned by 3:00 PM on Wednesday. The ‘Agile’ process has become a theater of the absurd. We have the Stand-ups, the Retrospectives, the Poker Planning with its little cards-3, 5, 8, 13-as if we can quantify the uncertainty of a leadership team that doesn’t know what it wants. It’s a ritual without a religion.

Natasha D. once told me that the hardest part of her job isn’t the chemicals; it’s the people who refuse to acknowledge the nature of the mess. You can’t ‘sprint’ your way out of a toxic spill. You have to contain it, neutralize it, and systematically remove it. You need a 53-point checklist and the discipline to follow it when things get messy. Software isn’t that different. Every time we ‘pivot’ without a strategic reason, we’re just creating technical and emotional debt-sludge that someone, eventually, will have to clean up.

The Final Stance

Marcus finally puts the cap back on the red marker. He looks at us with a beaming, 103-watt smile. “Any questions?” he asks. Silence.

There are 13 questions I want to ask. I want to ask if the VP has actually talked to a single user in the last 43 days. I want to ask if we’re ever going to stop running and start walking toward something real. Instead, I just look at my notebook, where I’ve doodled a small, 3-legged dog.

“Great,” Marcus says. “Let’s update the Jira board and hit the ground running. We’ve got 3 days until the end of the sprint.”

I walk back to my desk, passing a trash can that contains 33 discarded sticky notes from last week’s ‘brainstorming’ session. I open my IDE. I start deleting the code I spent 53 hours writing. It feels like cleaning up a spill, but without the satisfaction of a clean floor. It’s just making room for the next mess. And as I type, I wonder if Natasha D. has any openings on her crew. At least in her world, when you’re done for the day, the waste stays in the drums. where it belongs.