Severing the Informal Nervous System

When you move the people who talk to the customers away from the people who actually touch the hardware, you aren’t just changing their commute. You are severing the informal nervous system of the company.

You are taking a high-bandwidth, low-latency stream of “Hey, did we change the flare nut torque specs on the new 24k units?” and replacing it with a bureaucratic lag that turns a five-second nod into a forty-eight-hour waiting period.

I’ve spent a lot of time reading terms and conditions lately-every word, every clause. It’s a dry, exhausting exercise that teaches you one thing: the legal reality of a product is rarely the lived reality.

The T&Cs tell you what is “covered,” but they never tell you how to actually fix the thing when the wind is blowing at 40 miles per hour and the outdoor unit is making a sound like a bag of marbles in a blender. That knowledge isn’t written down in the legal department. It’s whispered in the breakroom between a support agent and a lead tech.

The Physical Geometry of Truth

Emma D.-S., a court sketch artist I’ve watched work on several occasions, once told me that the most important part of a trial isn’t what the witness says; it’s the way the lawyers lean toward each other when the judge is looking at a document.

“The most important part of a trial isn’t what the witness says; it’s the way the lawyers lean toward each other… Emma captures the ‘leaning in’ because that’s where the real action is.”

– Emma D.-S., Court Sketch Artist

There is a physical geometry to truth. In a courtroom, proximity dictates the flow of strategy. In a technical company, proximity dictates the flow of competence. When you move the support desk to a different building, nobody leans in anymore. They just sit upright in their ergonomic chairs and wait for the notification bell to chime.

Shadow Training & The Sensory Diagnosis

There is a specific, almost invisible process to how a technician actually diagnoses a piece of complex machinery-let’s say a high-efficiency heat pump. On paper, the process is: check the error code, consult the table, verify the voltage at the terminal block, and replace the component.

In reality, the process is much more sensory. A tech walks up to the condenser. They don’t just look at the LED; they listen to the rhythm of the compressor. They feel the vibration of the copper lines. There is a “harmonic” to a healthy system.

If a support agent sits twenty feet away from the testing bay where those techs are working, they overhear that. That overheard comment is a “shadow training” session. It’s a piece of high-level diagnostic intuition that bypasses the formal curriculum.

The agent doesn’t even realize they’ve learned it until three weeks later when a frustrated homeowner calls from a dusty attic. The agent hears the frustration, remembers the “stutter” conversation, and solves the problem in four minutes.

The Hidden Cost of Information Decay

When you move that agent to Building B, the shadow training dies. The agent is left with the PDF. And the PDF says “Check Motor.” This is the hidden cost of the “Efficiency Reorganization.”

We look at the cost per square foot and the cost per head, but we never look at the cost of the “Information Decay” that happens when knowledge has to travel through a digital pipe instead of a physical room. In the old world, the support agent was a junior apprentice to the entire engineering department by osmosis. In the new world, they are a data entry clerk with a pleasant voice.

I’ve seen this play out in dozens of industries, but it hits hardest in the world of climate control. If your software crashes, you might lose an hour of work. If your HVAC system fails in January, your pipes freeze and your life stops. The stakes are physical, which means the support needs to be grounded in physical reality.

When a homeowner is staring at a blank display in the middle of a July heatwave, the speed of cooper hunter tech support becomes the only metric that matters, far outstripping the theoretical savings of a cheaper lease in a different zip code.

Silos are Architectural, Not Psychological

We often talk about “silos” in corporate culture as if they are psychological failings, as if the employees are simply too stubborn to talk to each other. But silos are often architectural. If I have to badge through three doors and drive across a highway to ask a technician a question, I’m not going to do it.

I’m going to stay in my silo, and I’m going to give the customer the answer that is on the screen, even if I have a nagging feeling that the answer on the screen is wrong.

The irony is that we spend millions on Slack, Teams, and internal wikis to “bridge the gap.” We create digital water coolers because we destroyed the physical ones. We try to simulate the “overheard conversation” with hashtags and threads. But digital communication is intentional. You have to decide to type something.

In the world of technical support, the accidental information-the stuff you didn’t know you needed to know until you heard it-is the most valuable asset you have.

The 14-Gauge Solution

I remember a specific instance where a manufacturing change led to a different gauge of wire being used in a series of multi-zone units. It wasn’t in the manual update yet. The engineering change notice was still sitting in a “To-Be-Processed” folder in the compliance office. But the techs in the shop knew. They were complaining about the new wire being “stiffer and harder to strip” while they ate their sandwiches.

The support agents sitting at the next cluster of desks heard the complaining. They didn’t think much of it until the calls started coming in. “Hey, I’m having trouble getting a clean connection on the terminal block.”

Because they were ten feet away from the complaining techs, the agents didn’t have to “escalate” the issue. They didn’t have to wait for an official bulletin. They just said, “Yeah, we know, the new wire is a bit thicker.” Problem solved. Customer happy. Technician’s sandwich eaten.

We treat the distance between departments as a vacuum, but it’s actually a friction. Every foot of hallway, every flight of stairs, and every mile of road adds a layer of resistance to the flow of truth. When the resistance gets high enough, the truth just stops moving.

When “The Process” Becomes an Insult

I’ve often wondered if the people who design these reorganizations have ever actually sat in a support chair for a full shift. Have they felt the heat of a call where the person on the other end is crying because their mother’s oxygen concentrator is overheating in a 90-degree room?

In those moments, “the process” feels like an insult. You don’t want a ticket number. You want a solution. You want to be able to stand up, look over the cubicle wall, and yell, “Hey Frank, what causes the high-pressure switch to trip on the new CH mini split when the ambient temperature is only 85?”

That exchange takes four seconds. It saves a life, or at least a very expensive service call. But that four-second exchange is a casualty of the “optimized” floor plan. We are so obsessed with the “cost of support” that we forget the “value of support.”

Support isn’t just a drain on the balance sheet; it’s the most direct line of sight you have into how your product actually behaves in the wild. When you isolate support, you are blinding yourself. You are cutting off the feedback loop that tells you your flare nuts are failing, or your sensors are misreading, or your manuals are confusing.

A Sterile Workflow

It’s a mistake I’ve made myself, albeit on a smaller scale. I once tried to “streamline” my own workflow by moving all my research to one day and all my writing to another. I thought I was being efficient. But I found that without the “interruption” of research during the writing process, my writing became sterile.

It lost the immediate, messy connection to the facts. It became a “Building B” version of my work-cleaner, maybe, but much less useful. In the end, we have to decide what we want our support teams to be. Do we want them to be a firewall that protects the company from the customers? Or do we want them to be a bridge that connects the customers to the expertise?

The cost of being wrong is always higher than the cost of the rent.