The projector hums at a frequency that feels like it’s trying to vibrate my molars out of my gums. On the screen, a Jira board stares back at us-a digital graveyard of ‘completed’ tasks that, as of 4 minutes ago, no longer matter. We just finished a sprint. We delivered. We did the thing. But Gregory, a man whose primary contribution to the company is a collection of $344 vest-and-tie combinations and an uncanny ability to speak for 44 minutes without saying anything, just leaned back in his ergonomic chair. He didn’t look at the data. He didn’t look at the 14 user testing reports. He just squinted, and said, ‘This is great, but I think the market is moving toward a decentralized, AI-first, hyper-local experience. Let’s pivot the entire architecture by Monday.’
I can feel the collective spirit of the engineering team leave their bodies. It’s a silent, spectral exodus. We are ‘Agile,’ which in Gregory’s lexicon is a synonym for ‘I have no plan and I expect you to compensate for my lack of vision with your weekends.’
The Physics of Preparation
Pearl R.J. knows this feeling, though her stakes are physical. Pearl is a car crash test coordinator. In her world, if you change the parameters of a test while the vehicle is hurtling toward a concrete barrier at 44 miles per hour, people-even if they are just dummies filled with sensors-get obliterated. Pearl doesn’t ‘pivot’ mid-impact.
She spends 234 hours calibrating sensors for a test that lasts less than a second. She knows that if the foundation of the experiment is shaky, the data is a lie.
Modern software development has developed a pathological fear of the word ‘foundation.’ We’ve convinced ourselves that because code is ethereal, it doesn’t need the same structural honesty as a bridge or a car frame. We use Agile as an excuse to avoid the hard work of thinking. Planning is seen as ‘Waterfall,’ a dirty word whispered in the hallways like a Victorian-era scandal. But you cannot iterate on a void. You cannot pivot if you haven’t first planted your feet.
The Digital Equivalent of Clumsiness
I’m currently staring at my phone, my thumb hovering over the screen in a state of mild trauma. I just liked my ex-girlfriend’s photo from three years ago. It was a picture of a sourdough loaf she made during the first lockdown. Why? Because I was scrolling too fast, looking for a distraction from the 1004 unread Slack messages, and my motor skills betrayed me.
This is the digital equivalent of Gregory’s pivot. It is an impulsive, unplanned action that creates a cascade of unintended consequences. Now, the ‘strategy’ of our post-breakup silence has been shattered by a clumsy double-tap.
We pretend that the ceremonies-the stand-ups, the retrospectives, the point estimations-are the substance of Agile. They aren’t. They are just the clothes. You can put a tuxedo on a goat, but it’s still going to eat your garden. Most companies are just goats in tuxedos. We use the ‘sprint’ to justify a permanent state of emergency.
The Debt Ratio: Permanent Insolvency
We aren’t just in debt; we are bankrupt, living in a house made of cardboard and ‘quick fixes.’
If you want to build something that actually survives the elements, you need to stop treating your roadmap like a mood board.
Geometry of Stability
Think about the physical spaces we inhabit. When you look at the structural integrity required for something like Sola Spaces, you realize that you cannot simply ‘decide’ to move a load-bearing wall because you had a dream about an open-concept kitchen. There is a geometry to stability.
“
You want the light to come in, but you don’t want the roof to fall on your head. In software, we’ve forgotten that our code has a ‘weight.’ Every unplanned pivot adds a layer of complexity that acts like a grain of sand in a gearbox. Eventually, the machine just stops.
The Cost of Secondary Impact
The external event.
The secondary impact.
That’s what Gregory’s ‘pivots’ are. They are secondary impacts. Every unplanned pivot adds a layer of complexity that acts like a grain of sand in a gearbox.
I admit I’ve been part of the problem. I’ve nodded along in meetings when I knew the timeline was a fantasy. I’ve practiced ‘False Agile’ because it was easier than fighting a VP who thinks ‘velocity’ is something you can just demand by shouting.
The Need for Courage, Not Flexibility
The courage to say ‘no’ to a change that hasn’t been thought through. The courage to demand a stable foundation before we start stacking bricks.
They need to realize that every time they throw away a week of work, they aren’t just losing money; they are losing the trust of the people who build their products. And once that trust is gone, no amount of ‘Agile coaching’ or free snacks in the breakroom is going to bring it back.
We need to return to the actual principles of the Manifesto. Not the buzzwords, but the discipline. Excellence in craft. Sustainable pace. The idea that the best architectures emerge from self-organizing teams, not from the whims of a man who just read a Medium article about a new JavaScript framework while sitting on the toilet.
Pearl R.J. doesn’t pray for the car to survive the crash. She builds the car so it *can* survive the crash. She relies on the 44 sensors and the 4 types of reinforced steel. She relies on the plan. We should try doing the same. We should try building something that isn’t designed to be thrown away the moment someone in a vest gets a new idea.