The Weight of Stone, The Weightlessness of Code

Pushing the wheelbarrow across the uneven dirt of the restoration site, I felt the familiar vibration of a smartphone in my pocket-a notification for a software update I’ll likely never install, for a program I opened exactly 5 times in the last year. It’s a strange juxtaposition, standing here with a trowel that belonged to my grandfather, surrounded by 145-year-old limestone, while receiving alerts about ‘stability improvements’ for a digital world that feels increasingly unstable. I’ve spent the better part of 25 years as a historic building mason, a trade where ‘changing your mind’ mid-way through a supporting arch usually results in someone being crushed by 555 pounds of masonry. But lately, when I talk to my cousin who works in a shiny office building downtown, I realize that his world is far more dangerous than mine. His bosses have discovered a new way to ignore structural integrity, and they call it being ‘Agile.’

It’s Tuesday. My cousin, let’s call him Leo, spent his entire Monday-roughly 45 hours of work if you count the midnight oil-creating high-fidelity visuals for the ‘Blue Ocean’ campaign. It was crisp, it was strategic, it was grounded in a month of research. Then comes the stand-up meeting. He stands there with his coffee, and the manager, a man who wears expensive sneakers but has never seen a day of physical labor, announces a ‘pivot.’ The market is apparently moving. The ‘Blue Ocean’ is dead. Long live ‘Green Field.’ All those assets? They need to be green. Not by next week. By 5 p.m. tomorrow. This is the 35th pivot they’ve had this quarter. The manager smiles and says, “We’re just being agile, guys. Responding to change over following a plan.”

The Cowardice Behind the Methodology

But that is exactly what it has become. The original Agile Manifesto, birthed by 17 developers in 2005-well, the movement started earlier, but let’s say the mainstream adoption really crystallized around 2005-was about removing the suffocating weight of unnecessary documentation. It was about human-centric development. It was never intended to be a corporate get-out-of-jail-free card for leaders who lack the courage to commit to a strategy. When a leader refuses to make a choice, they aren’t being flexible; they are being cowardly. They are pushing the psychological and technical cost of their indecision onto the people beneath them. In the world of stone, if I keep changing the dimensions of the block I’m carving, I eventually end up with a pile of dust and no block at all. That’s what happens to teams under the ‘Agile-as-Chaos’ regime. They aren’t building a cathedral; they’re just making a lot of noise with hammers.

I remember my mentor, a man who could tell the density of a stone by the sound of his hammer, used a level that was calibrated so finely it could detect a hair’s breadth of tilt. He used to say that tools don’t make the mason, but a bad tool will lie to you about your own mistakes.

I think about that whenever I see software that promises to solve problems but only adds more layers of bureaucracy. Speaking of tools, I just updated that CAD software again. Why? I don’t know. I prefer the weight of the pencil. There is a specific friction between graphite and paper that helps me think through the weight distribution of an arch. Digital screens are too smooth; they make everything look possible, which is the first step toward delusion.

Strategic Creeping: The Slow-Motion Collapse

In my line of work, we call it ‘creeping.’ It’s when the soil shifts under a wall. You don’t notice it at first, just a tiny crack. But eventually, the gravity wins. Corporate ‘agility’ without a plan is just strategic creeping. It’s the slow-motion collapse of a company’s vision. Leaders think they are being ‘dynamic’ when they are actually just reacting to the loudest voice in the room or the latest tweet from a competitor. They are like sailors who think they are being ‘responsive’ by turning the rudder every time a wave hits the hull. You aren’t navigating; you’re just spinning in circles while the crew gets seasick.

Leadership is the art of saying ‘no’ to 125 good ideas so you can say ‘yes’ to one great one. But ‘Agile’ has made it too easy to avoid that ‘no.’ If you never have to commit to a plan, you never have to be wrong. If the project fails, it wasn’t because the strategy was bad-there was no strategy! It was just a ‘failed experiment.’ This misuse of the methodology reflects a deeper crisis of leadership. It’s a refusal to bear the burden of responsibility. In masonry, if the wall falls, I am the one who has to explain why to the preservation board. There is nowhere to hide. But in a ‘pivot-heavy’ environment, the blame is diffused into the fog of the process.

High Tech Defending Against Low Leadership

I’ve found that the only way to survive this reality is to find tools that actually respect the user’s time and effort. When my cousin was losing his mind over the ‘Blue Ocean’ to ‘Green Field’ disaster, he started using NanaImage AI to handle the heavy lifting of the visual iterations. It was the only thing that kept him from quitting on the spot. It allowed him to adapt to the manager’s whims without sacrificing his entire evening and his sanity.

I often wonder if these managers realize how transparent they are. We see the panic behind the ‘pivot.’ We see the lack of research behind the ‘new direction.’ It’s like a mason trying to hide a poorly cut stone with too much mortar. You can cover the gap for a while, but the weather always finds a way in. The frost gets into the cracks, expands, and pushes the stone out. The ‘weather’ in business is the market, and the market doesn’t care how ‘agile’ you claim to be if you aren’t actually delivering something of substance.

The Contract of Commitment

I see this every day in the eyes of the young people I work with on-site, the ones who left the corporate world because they wanted to build something that would last more than 45 minutes. There is a certain dignity in a plan. A plan says, “I have thought about this. I have weighed the risks. I believe this is the way forward.” It’s a contract between the leader and the team. When you break that contract every Tuesday at 9:05 a.m., you are telling your team that their time, their skills, and their sanity are worth nothing. I don’t care if you call it Scrum, Kanban, or ‘The Way of the Ninja’-if you don’t have a destination, you are just a drifter with a budget.

Last week, I was working on a chimney stack that was leaning about 5 inches to the north. It had been leaning that way since 1965. To fix it, I had to go slow. I had to understand why it was leaning. I had to have a plan for how to support the weight while I replaced the rotted bricks at the base. If I had been ‘agile’ and just started pulling bricks out to see what happened, the whole thing would have come down on my head. But because I had a plan, a real, documented, physical plan, that chimney is now as straight as an arrow. It took longer than a ‘sprint.’ It required more than a stand-up. It required expertise and commitment.

The Principles That Endure

I think back to that software update I ignored today. It’s still sitting there, a little red dot on the screen, demanding my attention. It wants me to change, to update, to ‘optimize.’ But the limestone doesn’t need an update. The mortar doesn’t need a pivot. The basic principles of building something that lasts-integrity, foresight, and a steady hand-haven’t changed in 5,000 years. If we could bring some of that masonry mindset into the digital boardroom, maybe we could stop the whiplash. Maybe we could actually build something worth looking at. Until then, I’ll keep my chisels sharp and my plans solid, and I’ll leave the ‘agile’ chaos to the people who don’t mind living in a house that’s constantly falling down.