Field Guide
Communication
You’ll notice that a piece of information can travel effortlessly through one part of an institution and never reach another part just a few floors away.
At a mid-size software company, this week’s sales numbers arrive almost without anyone touching them. They’re pulled automatically into a dashboard every morning, summarized in a standing Monday leadership meeting, mentioned in the all-company email that goes out like clockwork. Nobody has to decide, this week, to make that information travel. A route already exists for it, and it does the carrying on its own.
The customer-support team, three floors down, knows something else just as well: a specific step in the product creates confusion for a large share of new customers, generates a steady stream of predictable tickets, and comes up in nearly every shift’s internal notes. Ask any support rep and they’ll tell you immediately, in detail, without hesitation — there’s nothing hidden about it. But the product and engineering teams upstairs, currently prioritizing next quarter’s roadmap, have never heard it. Not because support was told to stay quiet. Because no comparable route exists for this kind of information the way one exists for sales numbers — no dashboard, no standing meeting, no email anyone would think to cc them on.
The distinction underneath this: Communication is what carries the material this Field Guide names elsewhere — Formation, Institutional Memory, Metrics, Narrative, what Truth-Telling escalates — between the people, roles, offices, and parts of an institution that need it. Its question isn’t the general one, “are we communicating well.” It’s more specific: what actually travels through this institution, and what doesn’t, and by what route. The sales numbers travel because an established route carries them without anyone deciding to send them. The support team’s knowledge doesn’t, not because it’s being suppressed, but because no route was ever built for it.
None of this means Communication only happens inside an institution — plenty of what an institution communicates travels outward, to the people it serves or answers to, and that outward-facing work matters too. But the internal case is the one this scene makes visible, and it’s easy to miss precisely because nothing about it looks like a failure: information can be completely uncontroversial, known plainly and honestly by the people closest to it, and still simply have nowhere established to go.
This is a different gap from the one Truth-Telling names. Truth-Telling is about whether a known thing gets deliberately escalated into an actual decision. Communication sits closer to the infrastructure underneath that: whether a route exists for something to travel along at all, before anyone even reaches the question of whether to send it.
Strength · Shadow · Watch for
Lets essential, recurring information move to the people who need it without requiring a fresh decision every time it comes up.
The presence of some well-worn routes can hide the absence of others — an institution can feel well-connected while whole categories of important information have no route at all.
Something everyone assumes “someone must have told them,” where no one can actually name the route it would have traveled by.
Places to look: A recurring number or report that reaches leadership automatically, next to a recurring concern that reaches leadership only if someone happens to remember to raise it personally. Two teams working a few doors apart, each holding something the other would clearly want to know.
What travels through this institution without anyone having to decide to send it — and what would have to be deliberately carried by hand, because no route exists for it yet?