The Informal Channel Carries the Real Coordination

Category: Why This Was Never an Accident The corridor conversation isn’t people skipping the process. It’s the part of the process that works.

The official process for getting a quote approved had six steps and a form. On paper it took two days. In practice it took two hours, because everyone knew the form didn’t cover the common cases, and everyone knew what to do about it. You sent the figures to Priya before the form, because Priya could tell you in a sentence whether finance would bounce it. You gave the warehouse a heads-up so they didn’t start picking the wrong stock. You checked with Sam before it went out, because Sam remembered the client had a contract clause the form never asked about. None of this was written anywhere. It was just how the quotes actually got out clean.

Then a new operations lead arrived, looked at the process, and saw people working around the form. So he tightened it. Everything had to go through the system, in order, with no side conversations. It was cleaner. It was auditable.

Within a month, quotes were going out with the contract clause missed, getting bounced by finance, picked wrong in the warehouse. Each one was logged as a separate error.

The form was now followed perfectly. Nobody had said it was the side conversations holding it together.

The Principle

Most of the coordination that actually keeps work moving happens off the org chart, and the informal channel that carries it is not a deviation from the real process. It is the part of the process that works.

Every formal process is a finite set of defined paths. It is written down at one moment, by people imagining the cases they could foresee, and it handles those cases well. But real work keeps throwing up cases the paths don’t cover. A step gets blocked. An edge appears that the procedure never anticipated. A question turns up that maps onto no form. The formal process has nothing to say about any of this, because it was finished before the case existed.

The informal channel is how the organisation actually handles those cases. It is the quiet word, the back-channel message, the “before you send that, check with Sam.” It is a person who knows who to ask, a heads-up that routes a decision to the one human who can make it, a nudge that unblocks a queue before it stalls. This is coordination and information routing through unofficial paths. It is not about who really holds the power, which is a different thing entirely. It is about how work actually travels when the official route runs out.

Here is the trap. Because the informal channel leaves no record, it is invisible from the documented view. So when a tidy-minded person looks at how the work gets done, they see only the formal map, and the map shows no corridor conversations. The channel reads as shadow process, as people working around the system, as exactly the sort of thing good governance is meant to stamp out. The instinct is to formalise it or remove it. And when that happens, the gaps it was silently covering reappear, as delays and dropped work and decisions sent to the wrong place, with nobody connecting the new failures to the channel that was just shut down.

Why It Pays Off

The informal channel is high-leverage work, and it stays that way, for three plain reasons.

It is adaptive where the formal process is rigid. A procedure is fixed at the moment it was written. It cannot bend to the case in front of it, because it has never seen that case. The informal channel can. It responds to the actual situation, so it covers exactly the edges and exceptions the procedure could not foresee. The rigid layer handles the expected; the adaptive layer handles everything else.

It routes around blockages in real time. When the official path jams, the channel finds the live human who can clear it now. The approver is on leave, so someone who knows the work asks the deputy directly. The queue is long, so a quiet word moves the urgent thing up. The form doesn’t fit, so two people sort it between them in a minute. None of this waits for the process to unstick itself, which is the difference between a thing that ships today and a thing that waits three days for the system to catch up.

And it carries context the formal record cannot hold. “Check with Sam, the client has a clause” is institutional knowledge that no form has a field for. It surfaces at exactly the moment it is needed, from exactly the person who happens to hold it. The formal record stores what someone thought to write down in advance. The channel delivers what nobody knew to ask until the case appeared. The responsiveness of the informal layer is what makes the rigidity of the formal layer survivable.

The Benefit

The payoff is real, it compounds, and almost none of it is ever attributed to the channel that produced it.

The first benefit is work that actually completes. The cases the form doesn’t cover get handled instead of bouncing. The throughput is real throughput, not the paper kind, where a process “ran” on time while the work inside it quietly failed. A quote that goes out correct is worth more than a quote that goes out on schedule and comes straight back.

The second is errors caught off the record, before they are committed. The quiet “check with Sam” kills the missed-clause failure before the quote ever leaves the building. There is no incident to show for it, because the thing that would have become an incident never happened. The channel’s best work is the work that leaves no trace at all.

The third is resilience to the unexpected. Because the channel adapts, the organisation absorbs the case the procedure never imagined, rather than freezing on it or failing it outright. The thing that should have broken the process gets quietly routed around instead.

A place where the informal channel runs well feels like a place where the process just works. And that is the heart of the problem. The smoothness gets credited to the formal process, never to the off-record network quietly covering its gaps. The gain from the channel is large, distributed, and invisible. The cost of removing it is also distributed and delayed, arriving as a slow return of every gap it used to fill. That asymmetry is exactly why nobody defends it. By the time the failures come back, the channel that prevented them is long gone, and unmourned.

How It Shows Up

• The process that “takes two days on paper” but reliably takes two hours, because everyone knows who to ask before they touch the form.
• The “before you send that, check with Sam” that catches the thing no procedure ever asked about.
• The new leader who tightens a process, eliminates the side conversations, and is genuinely surprised when the error rate climbs.
• The decision that used to get made in a corridor in a minute and now takes three days through the proper channel, with nobody calling the slowdown a cost of the change.
• The team where work just seems to flow around obstacles, credited to “good people who get on,” when it is actually a standing network quietly routing the cases the system can’t.

How To Cultivate It

• Recognise the channel before you tidy it away. When you see people working around the process, your first question should be what gap is this covering, not how do I stop it. A workaround is usually a map of where the formal process is incomplete. Read the map before you burn it.
• Don’t try to formalise the part whose value is informality. You can document the cases the channel keeps having to cover, and fix the form so it covers them. You cannot turn responsive, real-time routing into a procedure without destroying the very thing that made it useful. Improve the formal layer. Leave the adaptive layer free.
• Protect the conditions the channel runs on. It lives in proximity, in trust, and in people knowing who to ask. Reorganisations, remote shifts, and high turnover are the things most likely to quietly sever it. When you change those conditions, expect the routing to thin, and rebuild the connections on purpose.
• When you must close a workaround, find what it was covering first. Before you shut a side path, trace which gap it was filling, and make sure the formal process now genuinely handles that case. Otherwise you are switching off the cover without fixing the hole.
• When new failures appear after a tightening, suspect the channel you just closed. A sudden rise in errors, delays, or dropped cases right after a process got cleaned up is the signature of removed informal routing, not coincidence. Look there before you treat each failure as its own unrelated problem.

What Good Looks Like

The mark of success is, deliberately, a formal process that appears to just work. But the thing making it work is a living, system-wide routing network covering the gaps no procedure can foresee, and a good organisation recognises that network, protects it, and rebuilds it when it changes the conditions the network depends on.

Good looks like a formal process that delivers because an informal one quietly carries its exceptions. It looks like leaders who treat workarounds as diagnostic information about where the process is thin, not as misbehaviour to be corrected. It looks like a team that, when it reorganises, knows the corridor network is load-bearing and re-establishes it on purpose rather than discovering its absence in a month of climbing errors. The smoothest organisations are not the ones whose formal process covers everything, because none does. They are the ones with a healthy off-record network quietly covering what the process missed, and the sense to see that the corridor conversation was never people skipping the process. It was the process actually working.

A Reflective Question

The last time you tightened a process and stamped out the working around the system, did you check what those workarounds were quietly covering? Or did you only find out when the gaps they had been filling came back as failures you logged as something else?