Communication Breakdown
Is Interface Failure.

The person is not the problem.

There is someone on your team whose work is strong, whose read on the business keeps being right, and whose review says the same thing every cycle anyway: work on your communication. Maybe the written analysis is precise but the meetings do not land. Maybe the answers arrive a beat late, or blunt, or wrapped in the careful qualifiers a room reads as uncertainty. The substance holds up every time someone actually checks it. The delivery keeps getting flagged. So the organization does what it knows how to do with a flagged person: it names a development area and starts coaching.

And nothing changes. The coaching cycle runs, the person adjusts what they can, the next review softens the wording, and the same read keeps dying in the same rooms. Every experienced manager has watched this loop at least once, and most have run it, because if this were a person problem the standard treatments would eventually work. They keep not working. The failure is being located in the wrong place.

This arc builds out the first of the three moves from What Leading Becomes: gather the signal the organization already holds, then place the judgment, then route the work. The three moves sit on one line. The line starts with something one person knows, a warning, a read, a number that will not hold, and it ends at a judgment your organization acts on. Every decision you make runs down a version of that line, and the line has crossings where what travels can die. The first crossing sits between the person who knows and the room that decides, in the space between how one thinks and how the other listens. That space is the interface. What dies there never reaches the judgment at the far end. The person being coached is usually standing at that first crossing.

The most expensive misdiagnosis.

Follow the line instead of the person for a moment. The person your organization keeps coaching is holding a read it needs: an integration risk nobody upstream has seen, a number everyone trusts that will not survive the quarter, a customer pattern sitting three levels below the dashboard. When the room reads their delivery instead of their content, that read does not arrive, and the decision it belonged to gets made without it.

What the room is getting wrong has an old engineering name: the signal-to-noise ratio. Every channel carries both, and a receiver is only as good as its ability to tell them apart. An interface nobody designed filters on style, so fluent, confident delivery passes as signal whatever it carries, and careful, qualified delivery gets discarded as noise whatever it carries. You can watch the filter run in any leadership meeting: the confident summary collects nods, and the hedged correction gets parked for a follow-up that never happens. That is an organization confusing noise for signal, in both directions. Polished wrong ideas get through, and right ones get rejected because they arrived plain.

The organization then pays for the miss several times over. It pays for the coaching engagement, then for the performance plan when the coaching does not take, and often enough for a backfill and six months of ramp, because people who keep hearing that the problem is them tend to leave, or get quietly rotated out of the rooms where decisions happen, and the read they were carrying leaves with them. The bill also splits across levels, which is part of why nobody owns it: the middle manager runs the coaching conversations, the executive approves the development spend, and the decision the read belonged to goes wrong somewhere above both of them. None of that spending is booked as what it is. The coaching is booked as development and the departure as fit, and the decision that went wrong for want of the read gets an explanation that has nothing to do with communication, usually bad luck or bad execution. There is no line item for a judgment that failed to arrive.

The shape of the diagnosis gives the error away. A communication failure always has two ends: something was sent one way and received another, so both sides of the exchange failed to bridge the gap. Only one person in the exchange gets diagnosed, and it is reliably the one whose style sits further from the organization’s default. If the failure really lived inside a person, you would expect the diagnosis to land on either end at roughly the same rate. It lands on the non-default end almost every time.

Saying this plainly cuts against most of the communication training organizations buy. Language is important, and words are important. Leadership is influence, and influence runs on language. None of that makes one way of communicating more right, or more professional, than another. What organizations have actually done is confuse the dominant language for the right language, and the dominant way of influencing for the right way to influence. The style the room was built around, the fluent verbal read delivered quickly and with confidence, has been treated as a standard when it was only ever a default. The person whose style matches that default gets received, and everyone else gets routed into coaching.

The failure lives at the interface.

The Cognitive Translation Protocol starts from one claim. A communication failure happens at the interface between two cognitive systems, not inside either one. You have seen the evidence without the frame. A director answers exactly the question that was asked, and the room hears an unwillingness to commit. Someone asks for a quick gut check and gets twenty careful minutes, because the question meant something different on the other side of the table. Two people leave the same meeting with two different decisions in their notes. In each case both people did their part correctly, and the exchange still failed, because the failure happened in the space between them, and nobody in your organization owns that space. That is why the fix is structural.

This lens comes from the side of the exchange that gets diagnosed. My own communication runs literal, explicit, and deliberate. What most rooms process automatically I process the long way, on purpose, and it shows in the timing and the shape of what comes out. Organizations read that for years as a communication deficit in me, and every coaching conversation aimed at the delivery while the content sat there unexamined. From inside the exchange I could watch the actual event, a translation mismatch between two ways of processing, get recorded each time as a deficiency in one of them. The Neurodiversity Movement gave that observation its structural name: different nervous systems produce different cognitive architectures, shaping thinking, sensing, and processing across mind and body, not broken brains. In an exchange, that shaping runs in both directions at once, through how information is taken in and how it is communicated back out.

The Brain Economy puts a price on what the misdiagnosis wastes. Cognitive capacity is the economic variable now, and the effort a person spends on being understood is drawn from the same capacity you hired them to think with. You can see the spend in an ordinary workday: the email rewritten four times before it goes out, the extra hour of preparation before a thirty-minute meeting. I named that overhead the translation tax in an earlier essay. The undesigned interface is what levies it on the people you hired to think.

This is also why soft skill has been such an expensive filing label. Open your competency model and look at where communication lives: a personal attribute, listed beside integrity and drive, scored one person at a time. File it there and every interface failure becomes somebody’s development plan. Communication is a cognitive process running between two people, and once your organization files it that way, the failure becomes something you can design against. That label is worth rethinking at the foundation. It decides, before anyone has looked at the content, whose problem the failure is going to be.

From deficit to interface.

What changes in practice is where the intervention lands. The deficit model spends its budget redesigning the person. The interface model designs the channel, and the channel is made of ordinary things a leader already controls, at whatever level you lead from: a middle manager owns the format of the meetings they run, and an executive owns the defaults every meeting in the function inherits.

The meeting format is one of them. If the only path a read can take into a decision is a fast verbal exchange in a full room, that interface selects for fast verbal processors and drops everyone else’s contribution on the floor. A written pre-read changes what survives. So does a real asynchronous path, where analysis can arrive in the shape it was produced in rather than the shape the meeting allows. Shared context is another: a room that establishes what everyone knows before it judges what anyone said hears different things than a room inferring intent from tone in real time. And the route itself can be made explicit. A read that matters can be given a defined path to the decision it belongs to, one that does not depend on the sender’s live fluency, the same way a board does not depend on hallway conversation for the numbers it governs by.

These are changes to the channel. The reflex to file them under accommodation in the HR sense is the deficit model reasserting itself, quietly relocating the problem back inside a person who needs special handling. A designed channel gets more true signal through for everyone on it: the deliberate processor gets their read into the room, and the fast intuitive processor gets decisions made on better inputs. Design the interface well and the communication problem, the one the organization kept trying to coach out of a person, largely disappears.

The interface has structure.

Interface can sound like a vague space between people, but it has structure. The framework names six points where signal between two cognitive systems gets lost: inference, timing, signal clarity, sensory load, emotional attribution, and execution visibility. The gut check that came back as twenty careful minutes was an inference failure. The answer that arrives a beat late in a fast room is a timing failure. Some of the six fail before a word is spoken and some fail after everyone believes the exchange succeeded, which is part of why the losses are so hard to see from inside any single conversation.

Each of the six can be designed for, and the failures happening between two people who think differently are design failures, however thoroughly they have been documented as personal ones.

The Operating Brief.

The first crossing.

The three moves from What Leading Becomes run in sequence down the same line, from what someone knows to the judgment your organization acts on. The other two, placing the judgment and routing the work, run on whatever survives this first crossing. A decision built on a read that arrived garbled is garbled too, and nothing downstream can repair it, however well the rest of the system runs. Getting the signal in clean comes first because everything at the far end inherits its quality.

The next essay walks those six points one at a time, as an audit you can run against your own organization. The ask this week is small. When communication breaks between two people who think differently, look at the channel before you look at the person. The signal your organization needs most is dying in transit across interfaces nobody designed, carried by the people the deficit model keeps sending to coaching. Design the interface, and the signal starts arriving.