The click of the ‘Send’ button usually carries a satisfying finality, but today it was followed by that cold, hollow drop in the stomach. I realized, exactly 5 seconds too late, that I had sent the email without the attachment. It’s a tiny, stupid error, but it’s a symptom of the ritual overtaking the purpose. I was so focused on the act of sending-the muscle memory of the mouse movement-that I ignored the actual content. This is exactly how stagnation starts. It begins with a habit that works, which then becomes a ritual that must be protected, and eventually, it becomes a wall that stops any new information from getting in.
My missing attachment was a micro-version of the problem: Because I was an ‘expert’ at sending emails, I stopped being present in the complexity of the task. Expertise breeds inattention.
The Tribal Elder and the Status Quo
I’m currently sitting across from Atlas R.-M., our resident quality control taster, who is currently swirling a dark, viscous liquid in a glass that probably costs more than my first car. He’s a man who lives in the nuances. He can tell if a batch of chocolate was tempered at 85 degrees or 87 degrees just by the way it snaps against his teeth. He’s watching the Lead Architect of our systems department-let’s call him Greg-rant about why we shouldn’t adopt the new deployment pipeline. Greg has been here for 25 years. He is the tribal elder. He is also the single greatest bottleneck in the building.
‘We’ve been doing it this way for 15 years. It works fine. Why change it?’
The ‘fine’ process Greg is defending takes about 45 hours of manual intervention every week. It involves 5 different spreadsheets that don’t talk to each other and a server that needs to be manually rebooted every time the humidity in the room changes by more than 5 percent. To Greg, this isn’t a problem to be solved; it’s a landscape he has mastered. He knows the cracks in the sidewalk, so he’s forgotten that we could just pave a new road. He is the classic Expert Beginner. He reached a level of proficiency in 2005 and decided that the world should simply stop spinning right there.
The Cost of ‘Fine’
Greg didn’t like that. But Greg is currently blinded by the sunk cost of his own tenure. This is the danger of the ‘Expert Beginner’ trap. In many organizations, we confuse the length of a resume with the depth of the expertise… many people stop learning after the first 5 percent of their career. They find a solution that doesn’t get them fired, and they spend the next 15 years polishing that one solution until it shines, even as the world around them moves on to entirely different problems.
The Weaponization of Institutional Knowledge
When we proposed a shift to a more modular, automated system, the resistance wasn’t technical. It was emotional. To Greg, the new system represents a world where his 25 years of ‘rack-kicking’ knowledge is worth zero. He has built his entire identity on being the only person who knows how to fix the broken thing. If the thing is no longer broken, what is he? This is where institutional knowledge becomes a weapon used against progress. It’s a protection racket where the old guard keeps the systems inefficient so they remain essential.
Toxic Fermentation:
Skills unupdated don’t just stay the same; they ferment into something toxic. A culture of ‘no’ stifles teams faster than any market crash.
These aren’t experts. They are survivors of a previous era who have mistaken their survival for mastery. The real experts are the ones who are willing to be juniors again.
Dismantling the Arrogance of ‘Fine’
Lost Man-Hours (Per Cycle)
Focus on Value Creation
I’ve realized that I’m not immune to this. After I sent that email without the attachment, I spent 5 minutes blaming the software. I blamed the interface. I blamed the person who messaged me right as I was clicking. I did everything except admit that my own ‘expertise’ had made me sloppy. It’s easier to defend a mistake than it is to dismantle a habit. If I can’t even handle a single email, how can I expect Greg to handle the dismantling of a 25-year-old architecture?
A solution like
represents an exit ramp from this cycle of stagnation. It moves the focus from ‘who knows the secret’ to ‘how can we all move faster.’ It’s the difference between a dark cellar full of rotting beans and a clean, efficient lab where quality is measurable and repeatable.
The Necessary Friction
We often talk about ‘building on the past,’ but we rarely talk about ‘burning the past’ to make room for the foundation of the next thing. Greg isn’t building on the past; he’s living in it, and he’s charging us rent for the privilege.
True expertise is the ability to discard what is no longer true. It’s the willingness to admit that the 105 pages of documentation you wrote in 2015 are now just interesting historical artifacts.
The Curator vs. The Builder
20X
1 Year of Experience Repeated 20 Times (The Museum Curator)
We need to stop rewarding people for how long they’ve been in the chair and start rewarding them for how much of the building they’re willing to renovate. Expertise shouldn’t be a fortress; it should be a toolkit. And if your toolkit only has tools from 25 years ago, you aren’t an expert-you’re a museum curator. And in a fast-moving market, museums are just places where things go to be forgotten while the real work happens somewhere else.
The Humble Step Forward
I’ve decided to stop defending my own ’emails-sent’ record and start double-checking every attachment. It’s a small step, a 5-minute commitment to being a beginner again.
I’m going to go re-send that email now. With the attachment. And maybe I’ll suggest a new way to handle the files altogether, just to see if I can still feel that uncomfortable, beautiful spark of being a junior again. Because the day I stop feeling like I have something new to learn is the day I start becoming the bottleneck. And I’ve seen enough 15-year walls to know I don’t want to be one.
‘It was good for its time,’ he says. ‘But its time was 15 years ago. Today, it’s just a memory that’s overstayed its welcome.’