The sharp scent of ozone from the overworked laser printer hits me just as the third yellow sticky note of the morning flutters off the whiteboard and settles on the carpet. It’s a neon orange rectangle, meant to represent a ‘high-priority’ user story, but now it’s just debris. I am currently staring at a room of 13 people who are all trying to look busy while simultaneously waiting for someone else to explain why we are abandoning the work we started 23 hours ago. The project lead, a man who wears expensive sneakers to compensate for his lack of a concrete roadmap, claps his hands together. It is a hollow sound. He tells us we are being ‘Agile.’ He says the market has shifted-some nebulous feedback from a stakeholder who probably hasn’t used the software in 43 days-and thus, we are pivoting. Again. This is the third pivot this month. We are now 153 days behind the original delivery date, yet the spreadsheet says our ‘velocity’ is increasing. It’s a beautiful lie wrapped in the language of efficiency.

The Wisdom of Soil Conservation

Pearl S. would have hated this. She wasn’t just a soil conservationist; she was a woman who understood that if you don’t respect the underlying structure of the earth, nothing you plant will ever hold. She spent 13 years researching how the deep roots of perennial grasses anchor the soil against the wind. You can’t be ‘Agile’ with topsoil. You can’t decide to pivot to a different type of nutrient mid-season because a stakeholder had a dream about nitrogen. Soil requires a 23-year plan, or at the very least, a deep respect for the fact that some processes cannot be rushed or bypassed without catastrophic erosion. In our office, the erosion is psychological. The team is tired. We are ‘iterating’ on the same three buttons for the 83rd time, and the code base is starting to look like a house built by 103 different architects who were never allowed to talk to each other. Every time we change direction without a clear ‘why,’ the foundation cracks a little more.

[The architecture of indecision is a slow-motion collapse.]

🌿

There is a specific kind of arrogance in the modern corporate belief that planning is the enemy of speed. We’ve been sold this idea that ‘Waterfall’ is a dinosaur and that only the nimble survive. But what is nimbleness without a destination? It’s just a seizure. I see it in the eyes of the junior developers, who have written 233 lines of code this morning that they know will be deleted by 3 PM. They are being paid well, sure, but their souls are leaking out through the gaps in their productivity. There is no craftsmanship in a world where the ‘Definition of Done’ is ‘whatever we can ship before the CEO’s next board meeting.’ We are building digital ghosts, ephemeral structures that exist only to satisfy a metric on a dashboard that 43 people look at but nobody understands.

The Illusion of Progress

We talk about ‘failing fast’ as if it’s a virtue in itself. But failing fast is only useful if you’re actually learning, not just repeating the same 3 mistakes in a more colorful way. The business world adopted the vocabulary of software development because it sounded cool, but they stripped away the discipline. Real Agile requires a high degree of maturity and a clear vision; it’s meant to handle the ‘how,’ not to mask the absence of the ‘what.’ When you use it to justify a complete lack of strategy, you aren’t being a Silicon Valley disruptor; you’re just a person in a dark room swinging a bat at a piñata that might not even be there. I’ve seen projects consume $373,000 in ‘discovery phases’ that discovered absolutely nothing except that the leadership is afraid of making a firm decision.

This is where the contrast becomes painful. There is a world where planning isn’t a dirty word, where the ‘long view’ is the only view that matters. I think about the artisans who don’t work in two-week sprints, but in decades. There is a profound dignity in a product that doesn’t need to ‘pivot’ because it was engineered correctly the first time. It reminds me of the craftsmanship at

Magnus Dream UK, where the focus is on a standard of excellence that remains unmoved by the chaotic whims of the ‘now.’ Their engineering isn’t about chasing the latest trend; it’s about a meticulous, long-term commitment to quality that provides a literal foundation for rest. While my team is arguing about which shade of blue will satisfy a 3-second attention span, there are people out there building things that are meant to last for 33 years. It’s a reminder that precision and permanence aren’t obstacles to progress-they are the definition of it.

The Death of Expertise

I find myself thinking back to the 53-year-old developer who quit last month. He didn’t leave for more money; he left because he couldn’t stand the ‘whiplash meetings’ anymore. He told me that in his 23 years of experience, he had never seen so much activity yield so little result. We are in a state of permanent emergency. When everything is a priority, nothing is a priority. We have 13 ‘Priority 1’ tickets in the backlog, and the irony is that none of them actually move the needle for the user. They are just reactionary fires sparked by a leadership team that is terrified of the silence that comes with a long-term plan. They need the noise of the stand-up meeting. They need the visual clutter of the Kanban board to feel like they are in control. It’s a security blanket made of Post-it notes.

There is a hidden cost to this chaos: the death of expertise. You can’t become an expert in a system that changes every 13 days. You can only become an expert in the chaos itself. We are breeding a generation of ‘Agile practitioners’ who know everything about the ceremony of the meeting and nothing about the architecture of the product. It’s like being an expert in the rules of the huddle but never knowing how to actually throw the ball. I suspect that 63 percent of the people in my current meeting are secretly looking for other jobs, not because the work is hard, but because the work is meaningless. Meaning comes from seeing a project through, from the slow, methodical realization of a vision. You can’t have a vision if your eyes are constantly darting to the next shiny object.

The Silence of Strategy

What would happen if we stopped? What if we cancelled the sprint planning for the next 23 days and just… thought? What if we admitted that the ‘Agile transformation’ we spent 1503 hours on was actually just a way to avoid the hard work of making a decision? The silence would be terrifying at first. Managers would have to confront the fact that they don’t have a strategy. Developers would have to confront the fact that they’ve been using ‘iterative development’ as an excuse for sloppy initial design. But in that silence, we might actually find the ‘why’ again. We might find that Pearl S. was right-that you have to cultivate the ground before you can expect anything to grow. You have to commit to the soil if you want the harvest.

I look back at the whiteboard. The 13 people are still there. The marker in my hand is finally, truly dead. I put it down. The project lead asks if I have any input on the new ‘sprint goal.’ I think about the 233 wasted hours. I think about the precision of a well-made bed and the solid, unmoving reliability of a truly engineered product. I think about the tourist. I realize that being ‘Agile’ has become our way of avoiding the responsibility of being right. It’s a safety net for the indecisive. It’s a way to ensure that if we fail, we can at least say we were ‘flexible’ while we did it. But the stone bridge is still there, 33 blocks away in the other direction, standing perfectly still, doing exactly what it was designed to do a hundred years ago. It didn’t need a pivot. It just needed a plan.