The neon-blue border of the Zoom window pulses, a digital heartbeat that feels increasingly out of sync with my own. On the screen, a Jira board is being shared for the 12th time this week. Small virtual rectangles-sticky notes for the modern age-are being dragged from ‘In Progress’ to ‘Review.’ My hands are cold, a familiar numbness that starts at the tips of my fingers and creeps up to my wrists as I listen to the mechanical cadence of the daily stand-up. I am watching 22 years of deep architectural knowledge being compressed into a two-minute update about a button color.

We have traded the cathedral for the assembly line, and we’re calling it progress. The tragedy of the modern workplace isn’t just the boredom; it’s the systematic dismantling of the master-apprentice relationship in favor of a flat, interchangeable hierarchy. When everything is a sprint, nothing is a journey. We are obsessed with the ‘velocity’ of the team, a metric that measures how fast we are running without ever bothering to ask if we are running toward a cliff.

The Blunt Instrument

I recently found myself in a heated debate during a refinement session. I was arguing against the implementation of a new caching layer for the 12th time. I was loud, I was certain, and I used every ounce of my 22 years of seniority to shut down a junior developer named Hayden C. I won the argument. Three days later, I realized I was completely, embarrassingly wrong. The junior was right. But the ‘Agile’ process didn’t care about the truth of the system; it only cared that we reached a consensus and kept the board moving. My expertise wasn’t used to solve a problem; it was used as a blunt instrument to maintain the schedule.

This is the hidden cost of the ‘Agile’ age. It rewards the loudest voice that can fit its thoughts into a 15-minute window. It devalues the quiet, slow, agonizing process of becoming truly good at something. Expertise is not a set of tasks; it is a state of being. It is the ability to see the patterns in the chaos because you have lived through the chaos 52 times before.

Take someone like Hayden C. In our organization, Hayden is officially categorized as an ‘Emoji Localization Specialist.’ … Hayden spends hours agonizing over the specific pixel-density of a smile, knowing that in certain contexts, a slight tilt of the mouth can change a message from ‘friendly’ to ‘sarcastic.’ And yet, in the sprint planning, Hayden’s work is reduced to 2 story points. The process cannot quantify the 32 years of cultural immersion Hayden brings to the table. It only sees a task that needs to be ‘done.’ We are treating experts like Hayden as if they are modular components, ignoring the fact that their ‘output’ is inseparable from their soul.

There is a peculiar lack of patience in our current era. We want the result without the aging. We want the wisdom without the years. This brings me to a realization I had while researching the legacy of craft outside the digital world. There are some things you simply cannot ‘sprint’ toward. You cannot iterate your way into a masterpiece in two-week increments. Real value, the kind that lasts for 12 or 22 or 52 years, requires a surrender to the clock, not a fight against it.

Consider the way we approach the finer things in life, those relics of patience that stand in stark contrast to our hurried stand-ups. With Old Rip Van Winkle 10 Year Old, for instance, there is an absolute refusal to compromise on time. You can have the most ‘Agile’ distillery in the world… The expert distiller knows this. They don’t move a sticky note to ‘Done’ until the seasons have done their work. They respect the ‘blockers’ of nature.

The Fragility of Greatness

But a system that is resilient to the loss of expertise is a system that is incapable of greatness. Greatness is inherently fragile because it is tied to specific, irreplaceable human beings. If you replace a master distiller with a machine, you might get a consistent product, but you will never get a legendary one. If you replace a lead engineer who understands the 12 layers of legacy debt with a ‘full-stack’ developer who just follows the Jira tickets, you will get a functioning app, but you will never get a revolutionary platform.

I think about the argument I won. The one where I was wrong… In that moment, I wasn’t an expert; I was a cog that had learned how to jam the gears to get what I wanted. It was a failure of character born from a failure of environment.

Finding the Long Work

We need to find a way back to the ‘long’ work. We need to carve out spaces where Hayden C. can spend 32 hours thinking about a single character without being asked for a status update. We need to allow our masters to be slow. We need to recognize that the most valuable thing an employee brings to the table is not their ‘velocity,’ but their ‘judgment.’ And judgment is a slow-growth crop.

I’m looking at the clock on my wall. It’s 3:32 PM. Another meeting is about to start. I think about the 12 years it takes to make a decent spirit, and the 22 years it took for me to realize how little I actually know.

We are so busy being ‘Agile’ that we’ve forgotten how to be ‘Adequate,’ let alone ‘Excellent.’ Maybe the next time someone asks me for my ‘blockers,’ I’ll tell them the truth. I’ll tell them that the process is the blocker. The urgency is the blocker. The fear of being slow is the blocker.

But I probably won’t. I’ll just unmute my mic, adjust my camera so they can’t see the 12 books on philosophy sitting on my desk, and say ‘No blockers today, Toby. Everything is on track for the demo.’