Elias keeps a shop on a street that most people only use as a shortcut to the highway. He is a restorer of mechanical clocks-not the battery-operated ones that hum with a cheap, electronic buzz, but the ones that breathe.

He spent three days last week staring at a 19th-century French carriage clock that refused to keep time despite every gear being structurally perfect. He had cleaned the pivots, polished the leaves, and checked the mainspring for fatigue. By all measurable data, the clock should have been accurate to the minute.

The owner had suggested 3D printing a replacement for the escape wheel, citing a “digital model” that guaranteed geometric perfection. Elias had declined. He knew that the problem wasn’t the geometry; it was the “set” of the metal, a subtle, invisible tension born from a hundred years of ticking.

He eventually found the culprit: a microscopic burr on a secondary pinion that only revealed itself when the clock was tilted at a specific seven-degree angle. No diagnostic tool would have found it. Only the calloused tip of a thumb and thirty years of “knowing the feel” could.

We are currently in the process of 3D printing our entire corporate existence, and we are wondering why the timing of our departments feels so jagged.

Priya: The Human Knowledge-Base

Last month, a mid-sized logistics firm I consult for decided to “optimize” their procurement and IT support. For years, if you had a question about the labyrinthine nightmare that is Microsoft server licensing, you emailed Priya.

Priya had been with the company for nine years. She didn’t just know the SKU numbers; she knew that the third-floor server rack was over-provisioned and that the marketing team’s contractors only needed access during the Q3 push. She was a repository of context.

Of course, in the language of modern management, “freeing up” is often a polite euphemism for “rendering redundant.” Priya was moved to a different department, and the team was told to “submit a ticket” or “check the FAQ.”

The Logical Grid vs. The Crossword Clue

A system engineer named Marcus needed to scale up their remote desktop environment. He had twenty-eight new hires coming in-a mix of part-time data entry clerks and two full-time analysts. In the old world, he would have walked past Priya’s desk, mentioned the mix of users, and she would have told him exactly which Client Access Licenses (CALs) to order to remain compliant without overspending.

She would have reminded him that the data entry clerks shared workstations, so Device CALs were cheaper, while the analysts needed User CALs for their roaming laptops.

Marcus opened the Portal. He was met with a dropdown menu.

The menu offered “RDS CAL – User” or “RDS CAL – Device.” There was no option for “Mixed Environment for Shared Workstations.” There was no “Ask a Question” box that didn’t require a pre-assigned category. The Portal was a logical grid, but Marcus’s problem was a crossword clue with three possible answers and only four squares of space. The Portal didn’t have “context” in its database. It only had “definitions.”

The Static of Disconnection

My left arm is currently buzzing with that peculiar, electric static that comes from sleeping on it at a sharp angle. It’s a reminder that systems-even biological ones-depend on unobstructed flow. When you pinch a nerve, the hand doesn’t stop existing; it just stops communicating correctly with the brain. You can still see the fingers, but you can’t feel the texture of the keys.

The Portal is a pinched nerve in the corporate body. It cuts off the “tactile” feedback of human expertise, leaving the organization numb to its own complexities.

We have reached a point where we value the interface of knowledge more than the knowledge itself. We assume that if a question can’t be answered by a dropdown menu, it isn’t a valid question. This is a dangerous form of organizational gaslighting.

When Marcus couldn’t find his specific scenario in the Portal, he didn’t think, “The Portal is limited.” He thought, “I must be doing this wrong.” He spent four hours searching the internal wiki, four hours of high-value engineering time wasted on a task that Priya would have solved in four minutes.

The “Strategic Tasks” Priya was supposedly moved to? They didn’t exist. She was eventually managed out because the system no longer recognized her value. The system could measure “Tickets Closed” and “Portal Uptime,” but it had no metric for “Mistakes Prevented by a Five-Minute Conversation.”

You cannot measure the absence of a disaster. You cannot put a KPI on the catastrophe that didn’t happen because someone with a memory and a pulse said, “Wait, don’t do it that way; we tried that in 2018 and it crashed the SQL cluster.”

This isn’t just about licensing; it’s about the erosion of tacit knowledge. Tacit knowledge is the stuff we know but cannot easily write down. It’s Elias knowing the “feel” of a carriage clock pinion. It’s a seasoned IT admin knowing that a certain server version has a “handshake” issue with a specific VPN.

When you replace a person with a portal, you aren’t just automating a process; you are lobotomizing the collective memory of the firm.

The High Stakes of Precision

I see this most clearly in the world of infrastructure software. There is a reason why people get nervous when buying server licenses. It’s not just the cost; it’s the fear of the audit. It’s the fear of being “out of compliance” because you checked the wrong box in a digital vacuum. You want a human to look at your setup and say, “Yes, this is correct.” You want the reassurance that the gear fits the movement.

In those moments of high-stakes precision, you find yourself looking for something like the RDS CAL Store because you realize that the transaction isn’t just about a key; it’s about the confirmation that you haven’t just wasted five thousand dollars on the wrong type of access.

You want the sizing help. You want the setup guidance. You want the thing the Portal was designed to eliminate: a person who actually knows things.

We are told that automation is about scale. And it is. You can process ten thousand “standard” requests an hour with a well-built API. But business isn’t a series of standard requests. Business is a series of exceptions held together by a thin veneer of routine.

The 10% of cases that don’t fit the dropdown are almost always the 10% that actually matter-the big migrations, the emergency expansions, the weird legacy integrations that keep the lights on.

When you erase the Priyas of the world, you save on the salary, but you pay a “Complexity Tax” every single day thereafter. You pay it in engineering hours. You pay it in “over-licensing” because the staff is too afraid to be under-licensed. You pay it in the slow, grinding frustration of a team that feels unheard.

Reversing the Portalization

I look at my arm, the feeling finally returning in a painful rush of pins and needles. Communication is returning, but it hurts. Reversing the “Portalization” of a company hurts, too. It requires admitting that the spreadsheet lied-that the “efficiency gains” were actually just shifted costs.

It requires acknowledging that a person with a decade of context is worth more than a thousand pages of documentation that nobody reads.

“Elias eventually fixed the carriage clock. He didn’t use a 3D printer. He used a tiny, Arkansas whetstone and a loupe.”

– The Mechanical Truth

He removed the burr, reassembled the movement, and watched the balance wheel find its rhythm. It wasn’t “optimized.” It was right.

Building Bridges, Not Walls

We need to stop building interfaces that act as walls. We need systems that act as bridges to the people who know the “feel” of the gears. Because when the clock stops-and eventually, every system stops-a dropdown menu won’t be the thing that starts it ticking again.

It will be the person who remembers how it was built, why it was built, and exactly which pinion is holding the tension.

The next time you are told to “use the portal,” ask yourself what is being hidden behind that sleek, blue-and-white curtain. Usually, it’s the person you actually need to talk to, sitting three desks away, wondering why the world suddenly went silent.