My vertebrae gave a sharp, dry pop that echoed against the glass walls of the boardroom, a sound far too loud for a room filled with 19 people pretending to care about a quarterly audit. I had cracked my neck a bit too hard, and now a dull, rhythmic throb was settling in right behind my left ear, perfectly timed with the flickering of the overhead fluorescent tube. Across the table, Margaret-who has occupied that exact chair for the last 39 years-wasn’t looking at the screen. She was looking at me with the kind of pity usually reserved for a toddler trying to explain gravity. I had just suggested that we could automate her department’s primary data-entry workflow, a move that would effectively turn a 9-hour manual grind into a 9-minute background process.

‘The new system could never handle the nuances, Lucas,’ she said, her voice dropping into a register of practiced solemnity. ‘You have to do it by hand. There are layers to this that a machine simply cannot see.’

It was a classic move. It’s the gatekeeper’s gambit. We often mistake this for a fear of technology, a Luddite-style hesitation to embrace the shiny and the new. But if you sit in these rooms long enough, you realize it has nothing to do with the software. It’s about the architecture of identity. Margaret isn’t protecting the process; she’s protecting the 29 layers of complexity she spent four decades mastering. If the process becomes simple, the high priestess becomes a redundant observer. When you democratize the work, you destroy the hierarchy of the ‘difficult.’

This is why legacy systems persist. They are the physical manifestations of the ‘hero’s journey’ in the most boring sense possible. We build these convoluted, Rube Goldberg-esque structures out of spreadsheets and legacy databases because they require a specific, localized knowledge to navigate. This creates job security, sure, but more importantly, it creates a sense of belonging to an elite group. Only we know why the $999 invoice has to be entered into the system three separate times using 9 different keystrokes.

The Sensory Logic of Obsolescence

I remember a project where we tried to streamline a logistics chain for a manufacturing firm. The lead foreman, a man who had 29 distinct scars on his forearms from 29 different machine mishaps, refused to touch the tablet we gave him. He insisted that the ‘feel’ of the paper told him more about the inventory than a screen ever could. He had learned to read the gaps and the errors like a tracker reads broken twigs in a forest. To him, the efficiency of the new system was a form of blindness. He was losing his sight.

But here’s the contradiction I can’t quite resolve: sometimes, the veterans are right about the soul of the work, even if they’re wrong about the method. You see this in industries that have managed to evolve without discarding their heritage. For instance, the way

Chase Lane Plates handles the transition from old-world aesthetics to new-world materials is a masterclass in this balance. They’ve managed to strip away the unnecessary friction while keeping the identity intact. It’s a rare feat.

The Grief of Irrelevance

Most companies fail at this because they view change as a binary. It’s either the ‘old way’ or the ‘disruption.’ They don’t account for the fact that Margaret has tied her self-worth to the 9-hour manual task. If you take that task away, you aren’t just giving her back 9 hours of her life; you are taking away 9 hours of her feeling necessary. To successfully implement change, you have to find a new way for the veteran to be the hero.

I once spent 49 days trying to convince a law firm to move their filing system to the cloud. One of the senior partners, a man who still used a fountain pen that cost $899, argued that digital files lacked ‘gravitas.’ […] If the files are weightless, was his career weightless too? It’s a terrifying question to ask someone at the end of their professional life.

We mock the people who can’t figure out the new UI, but we don’t acknowledge that they are losing a language they spent their lives learning. It’s like being told that the French you’ve spoken since birth is now obsolete, and everyone is moving to a dialect consisting entirely of emojis and shorthand.

Craftsmanship vs. Efficiency

Lucas J. once showed me a piece of origami that took him 599 individual movements to complete. […] He looked at me, adjusted his glasses, and said, ‘Because then I wouldn’t be the man who can fold the sphere. I’d just be the man who owns a laser.’ That hit me in the gut. That’s Margaret. She doesn’t want to be the woman who clicks a button; she wants to be the woman who knows the nuances.

The challenge for us-the people pushing the updates, the people cracking our necks in boardrooms-is to stop treating the ‘nuance’ argument as a technical lie. It’s an emotional truth. We have to design systems that allow for craftsmanship even within automation. We have to find the $299 billion middle ground where efficiency meets dignity.

I should have asked her to help me design the logic of the automation, to bake her 39 years of ‘nuance’ into the code itself. I should have made her the architect of the new, rather than the victim of it.

The Legacy of Pain

My neck still hurts. Every time I turn my head to the left, I’m reminded of that sharp pop. It’s a tiny, physical legacy of a moment of tension. Maybe that’s what these broken processes are: the physical pops and cracks of a company that has grown too fast for its own skeleton. We cling to the old ways because they are familiar, even when they cause us pain.

I think I’ll go apologize to Margaret, though I’ll probably wait at least 9 minutes before I do. Some things shouldn’t be rushed.