Pearl J. is a wilderness survival instructor in the North Cascades who occasionally runs “stress-test” simulations for corporate leadership retreats. In one specific exercise, she divides a team into three distinct roles: the Scouts, who are the only ones allowed to look at the actual terrain; the Navigators, who are the only ones allowed to hold the topographical map; and the Liaisons, who are the only people permitted to speak to both groups.

The Scouts and Navigators are forbidden from communicating directly. It is a simulation of the standard corporate hierarchy, where specialized information is siloed and mediated by a central representative.

The Granite Shelf Failure

A team of twelve attempted this on a granite shelf near Sahale Glacier. The Scout saw a narrow chimney in the rock that looked passable. The Liaison took that information and ran two hundred yards back to the Navigator.

By the time the Liaison arrived, they had forgotten whether the Scout said the chimney was on the left or the right side of the couloir. The Liaison guessed. The Navigator plotted a course based on a guess. The team spent four hours climbing into a dead-end gorge because the person holding the map was not allowed to hear the person looking at the rock.

The exercise ended with the team exhausted and dehydrated. Pearl noted that the Liaison was the most stressed person in the group, despite doing no technical navigation or physical scouting. They were exhausted by the burden of being a human telephone.

The Digital Gatekeeper

In the world of software development, this Liaison is the account manager. They are the person whose entire professional function is to be the single point of contact. They sit in the middle of the “official” shared channel, a gatekeeper standing between the person with the problem and the person with the solution.

Renata, a technical program manager at a mid-sized fintech firm, recently experienced the digital version of that granite dead-end. At 4:15 p.m., she typed a question into the project’s Slack channel: “Is the message queue idempotent for the legacy ledger integration?”

It was a binary question with a complex answer. She watched the account lead’s typing indicator appear. It flickered for nine minutes. The account lead was likely drafting a response, editing it for tone, perhaps checking a slide deck or a previous status report to see if they could answer it without “bothering” the engineers.

“Great question, Renata! Let me sync with the technical team on our stand-up tomorrow morning and get back to you with a full update.”

Renata did not have until tomorrow morning. She opened a direct message to Anders, the senior engineer whose name she had seen on the most recent pull requests for that repository.

“Hey Anders, sorry to go around the official channel, but is the queue idempotent for the ledger?”

Anders replied in ninety seconds. He sent a link to a specific line in the documentation and added a two-sentence caveat about a race condition in the staging environment. Renata thanked him and apologized again for the “side-channel” interruption.

– Anders replied: “No worries. Everyone does it. It’s the only way things actually get built.”

The Mailbox Paradox

Earlier today, I counted my steps from the front door to the mailbox-exactly forty-four. It is a predictable, direct path. If I had to tell a neighbor to go get my mail, and that neighbor had to call a third party to ask for the key, the process would take twenty minutes instead of forty seconds.

We accept this in our personal lives as absurd, yet we bake it into our million-dollar engineering contracts as a “premium service.” I spent several years believing that account managers were a vital buffer. I was wrong.

I used to argue that senior engineers were too “expensive” or too “socially specialized” to be put in front of clients. I believed that they needed a translator to turn technical constraints into “business value” and to shield them from the chaotic whims of a client who doesn’t understand the difference between a front-end tweak and a database migration.

I was wrong because I was treating engineering as a commodity and communication as a distraction. When you separate the people having the conversation from the people doing the work, you don’t get “focus.” You get a game of Telephone where the stakes are the success of your product.

Truth vs. Commercial Dilution

The relay role exists to protect the commercial relationship from the technical truth. If a client asks a question and the engineer answers, “No, we can’t do that by Friday because the API won’t support the load,” the truth is out in the open. The commercial relationship must then deal with that reality.

But if that same question goes through an account manager, the answer can be massaged. It becomes: “We’re looking into some optimization paths to ensure we hit our milestones.”

This isn’t a lie, but it is a dilution. It allows the vendor to maintain a veneer of “everything is fine” while the engineers scramble in the background to fix a structural impossibility they never should have been asked to solve in the first place.

A Biological Response to Blocked Arteries

The informal side channel-the direct DMs, the “don’t tell the account manager we talked” calls-is not a breakdown of process. It is a biological response to a blocked artery. People are rebuilding the connection that the organizational chart tried to remove.

When companies hire Digital Heroes, they often expect the standard layer of middle management. They expect the person who will “manage” the relationship.

Instead, they find a model where one named senior tech lead owns the architecture and attends every call. There is no filter. If the architecture is failing, the client hears it from the person who wrote it. If the timeline is slipping, the explanation comes from the person holding the keyboard.

This transparency is uncomfortable for vendors who rely on the account manager to hide the “sausage-making.” It is also uncomfortable for clients who are used to having a person they can yell at who isn’t the one actually building their software. But that discomfort is the price of speed.

We have reached a point where nobody actually “books” the account manager for their expertise. They are booked for their availability. They are a professional “I’ll find out for you” person.

In a world of high-latency communication, perhaps that had value. In a world of Slack, GitHub, and real-time observability, that person is a bottleneck. The tell-tale sign of this decay is the apology.

When Renata apologized to Anders for asking a question, she was apologizing for being efficient. She was acknowledging that the “correct” way to work was so broken that she had to “break the rules” to get her job done.

The Distraction Tax

Organizations pay for both the official nervous system and the informal one. They pay the salary of the account manager to sit in the meetings and relay the messages, and they pay the “distraction tax” of the engineers who have to answer the same questions twice.

Once to the client in a “secret” DM, and once to the account manager during the “sync.” Removing the relay requires a terrifying admission: that the engineers are capable of managing the relationship and the clients are capable of hearing the truth.

From Managing Expectations to Sharing Reality

Pearl J.’s team eventually made it out of the gorge, but only after the Scout and the Navigator started shouting to each other over the Liaison’s head. They stopped caring about the rules of the simulation because they were tired of being lost.

In software, we are often just as tired, but we keep whispering through the relay, pretending that the person in the middle is adding value, while our DMs are full of the truths we aren’t supposed to say out loud.

The most successful projects I have seen in the last decade shared one trait: there was no one in the room whose job was just to “be in the room.” Every person on the call could open the codebase or the architectural diagram and explain exactly why a decision was made.

If you find yourself watching a typing indicator for ten minutes for a question that takes ten seconds to answer, you aren’t being managed. You are being delayed. And no amount of “client success” or “relationship management” can make up for the cost of a team that is forbidden from looking at the map while they are standing on the mountain.