Astrid T. is a woman who understands the weight of a silent telephone. She is a hospice volunteer coordinator and she spends her days in the quiet space between a clinical diagnosis and a final breath.

For ten years, Astrid kept a leather-bound notebook in the top drawer of her desk. The notebook contained the home phone numbers of three social workers and two priests and a woman named Martha who could find a spare hospital bed in the middle of a blizzard.

When a family spiraled at three in the morning and the grief became too heavy for the walls of a small house, Astrid did not fill out a form. She opened the drawer and she dialed a number and she spoke to a human being she knew by name.

The problem was usually solved before the sun came up. The system was messy and it was personal and it worked because the people in the notebook felt a sense of duty to Astrid.

The Liability of Transparency

Last year, the hospital group implemented a centralized management portal. They told Astrid the notebook was a liability. They said the notebook was not transparent. They gave her a login and they showed her how to use the drop-down menus.

Now, when a family is in crisis, Astrid logs into the dashboard and she creates a case. She selects the urgency level and she attaches the relevant patient ID and she clicks a button labeled Submit.

The request goes into a queue. The queue is monitored by a rotation of staff members in a corporate office four hundred miles away. Astrid watches the status bar. It stays yellow for “Pending” and then it turns blue for “Assigned.”

The family is still crying and the priest is asleep and the social worker is off the clock. The portal is fair and it is organized and it is perfectly, devastatingly slow.

The IT world has built the same kind of cage. We call it the escalation path. We tell ourselves it is a ladder that leads to a solution, but more often it is just a series of rooms where the doors only open from the outside.

I spent years believing in the holiness of the process. I was an administrator at a firm with eight hundred users and I was tired of being stopped in the hallway. I was tired of the “quick questions” that took forty minutes to answer.

I was the one who wrote the policy that ended the era of the direct phone call. I told my team that we were professionalizing the department. I said that if a request was not in the system, it did not exist.

The Tiered Cage of Professionalism

I built a wiki and I defined the tiers. Tier One was for the simple things. Tier Two was for the configurations. Tier Three was for the disasters. I thought I was building a machine that would free us from the chaos of the informal network.

I was wrong. I was profoundly and demonstrably wrong. I mistook a barrier for a process and I mistook silence for efficiency. By forcing every problem through a narrow, standardized gate, I stripped away the most valuable asset any IT department possesses: the ability to route a problem based on the intuition of experience.

In the old days, an admin knew that a licensing error on a Remote Desktop Services server was not just a ticket. He knew that the specific error meant the grace period was ending for the accounting department during tax season.

He did not need to read a manual to know that forty people would be locked out of their environments by lunch. He knew who owned the license keys and he knew how to reach them. He made a call and the server stayed up.

Under my new, “professional” system, that same admin had to file a ticket. The ticket went to a junior tech who did not know the accounting department or the tax deadline. The junior tech followed the script.

He asked the admin to restart the service. He asked for screenshots. He waited four hours to respond because his metrics were based on volume, not on the severity of the business impact.

By the time the ticket reached someone with the authority to actually fix the license, the accounting department was dark.

The Latency of Formalism

The informal network was never actually disorganized. It was a high-speed routing system tuned by years of human interaction. It functioned on a currency of trust and a deep knowledge of who actually held the keys to the kingdom.

When you replace that network with a formal escalation path, you are not just organizing the work. You are adding latency to every transaction. You are replacing a 15-minute fix with a two-day paper trail.

This is especially true in the world of Microsoft licensing. There is a specific kind of dread that comes with a “No Remote Desktop License Servers Available” message. It is a binary problem. Either the users can work or they cannot. There is no middle ground.

When a system engineer is staring at a production server that is refusing connections, they do not want a ticket number. They want the licenses and they want them now. They need to know if they need User CALs or Device CALs and they need to know if the 2022 licenses will play nice with the 2019 host.

In a formal corporate procurement environment, this is a nightmare. You send a request to purchasing. Purchasing sends a request to a vendor. The vendor puts the request in a queue. The queue is managed by an account executive who is currently at lunch.

Three days later, you get a quote. You approve the quote. The license arrives in another forty-eight hours. The users have been sitting on their hands for a week. The process was followed perfectly and the business lost twenty thousand dollars in productivity.

The alternative is the direct route. It is the digital version of Astrid’s notebook. It is knowing that you can go to the

RDS CAL Store

and get the exact perpetual licenses you need in fifteen minutes.

It is the realization that speed is a form of expertise. When a vendor understands that an IT admin is under a deadline, they do not build a ladder for the admin to climb. They provide the solution and they get out of the way.

They provide pre-sales help to make sure the versioning is correct and they provide post-sales setup guidance because they know that a license key is useless if it is not installed correctly.

I remember a specific Tuesday when I realized my formal system had failed. I was sitting in my glass-walled office and I saw one of my senior engineers, a man named Mike, pacing in the breakroom.

Mike was a veteran who could fix a corrupted registry in his sleep. He looked defeated. I asked him what was wrong. He told me that the sales team’s terminal server was down. He knew exactly what was wrong. He needed a specific pack of 50 User CALs to replace a batch that had been fat-fingered during a migration.

“Why haven’t you fixed it?” I asked.

Mike looked at me with a tired smile. I had created a world where my best engineer was forced to be a spectator to a crisis he knew how to solve. I had prioritized the “fairness” of the queue over the reality of the business.

I had built a system that treated every problem as if it were the same size, which is the same thing as having no priorities at all.

The ladder of escalation is often sold as a way to “manage expectations,” but it usually just manages to frustrate everyone involved. It assumes that the person at the bottom of the ladder has the wisdom to know when to pass the ball, but the system is designed to keep them from passing the ball too quickly.

The junior tech is incentivized to close the ticket or keep it at their level to prove they are doing their job. The senior engineer is incentivized to stop caring because their hands are tied by policy.

We are living in an era where we have more tools for communication than ever before, yet it has never been harder to talk to the right person. We have replaced the direct line with the chatbot. We have replaced the personal relationship with the “customer success manager” who changes every six months.

We have traded the notebook for the portal, and we are paying for it in the currency of our own time.

The irony is that the informal network was actually more “fair” than the formal one. In the notebook era, the urgency was determined by the person closest to the problem. The priority was set by the reality of the situation, not by a pre-defined category in a software suite.

If the server was smoking, you called the guy who had the fire extinguisher. You didn’t file a “Facility Maintenance Request” and wait for a three-day SLA to kick in.

Dismantling the Tiers

I eventually dismantled the strict tiers in my department. I kept the ticket system for tracking and documentation, but I gave my senior staff the “Golden Key.” I told them that if they saw a problem they could fix in ten minutes, they should fix it and write the ticket later.

I told them that knowing who to call was a skill we should celebrate, not a habit we should break. We went back to having a list of names and direct numbers for our most critical vendors. We looked for partners who valued our time as much as we did.

Astrid still has her notebook. She keeps it in her purse now, away from the prying eyes of the hospital administrators. She still uses the portal because she has to, but when the situation is dire and the clock is ticking, she reaches for the leather-bound book.

She knows that a formal process is a luxury for people who have time to waste. For everyone else, there is the direct line.

In the world of IT infrastructure, where a single licensing error can halt a multi-million dollar operation, the “direct line” is the only thing that matters. It is the difference between a minor hiccup and a systemic collapse.

It is the reason we still value the people who know the “secret” ways to get things done. The formal escalation path is a fine thing for a slow day, but when the users are calling and the screen is red, give me the notebook every time.