The Hidden Cost of Communication Gaps

The CEO's message was seven words long, repeated in every all-hands, printed at the top of the strategy deck, and referenced in nearly every leadership communication for the following two quarters: "We are becoming a customer-centric company." No one misheard it. No one disputed it. Every function could recite it accurately when asked.

Six months later, a hypothetical, illustrative comparison across functions reveals something the repetition never surfaced: Sales had interpreted it as license to increase customer contact frequency. Operations had interpreted it as a mandate to remove process steps that slowed response time. Finance had interpreted it as tighter scrutiny of customer-level profitability, cutting unprofitable accounts loose. Product had interpreted it as a directive to chase more customer feature requests. Support had interpreted it as a pure speed metric — faster first response, regardless of resolution quality. Five functions, each acting in good faith on the same seven words, had built five operationally different companies.

This is not a story about anyone failing to communicate clearly, and it is not a story about anyone failing to listen. The message was, by any reasonable standard, clear. It was also, in the sense this article develops carefully, not the same thing as shared meaning — and the gap between the two is where a genuinely important and under-examined category of organizational cost lives, hidden specifically because every individual instance of it looks, from the inside, like successful communication.

The mechanism worth making explicit from the outset runs in a specific sequence: information moves from a sender to a set of receivers; each receiver interprets it, drawing on whatever local context they have available; that interpretation gets translated into operational decisions specific to each function; those decisions then have to coordinate with decisions being made elsewhere in the organization, on the basis of the same original message; and the organizational consequence — coherent execution or costly divergence — depends on what happens at every step in that chain, not merely on whether the first step, transmission, succeeded. A communication problem, in the sense this article investigates, does not require that information went missing or arrived garbled. It can arise entirely from what happens after the information arrives intact: the same accurate message producing several different, individually reasonable interpretations, which then produce local actions that were never checked against each other before they diverged into something costly.

This connects directly to concerns already on a CEO's own agenda, not only a communications team's. Execution coherence depends on whether different functions pursuing the same stated priority are actually converging on compatible versions of it, or diverging in ways that will eventually surface as conflict. Change velocity depends on how much time gets spent, months into an initiative, discovering and reconciling interpretations that should have been checked at the outset. And strategic confidence — a leadership team's own sense that its direction has been understood — depends on evidence considerably more specific than whether a message was repeated and formally acknowledged.

The most useful theoretical starting point for this problem, and one with unusually direct relevance to the opening scenario, comes from Richard Daft and Robert Lengel's 1986 paper in Management Science, which asks a deceptively simple question: why do organizations process information at all? Their answer distinguishes two genuinely different forces shaping an organization's information needs. Uncertainty is the absence of information — not knowing something that could, in principle, be found out by gathering more data. Equivocality is different and, they argue, considerably more consequential in practice: a condition in which the available information is itself ambiguous, admitting multiple plausible interpretations, such that more data does not resolve the ambiguity and can sometimes deepen it (Daft & Lengel, 1986).

Their central and directly relevant finding, stated in their own terms, is that a major problem organizations face is a lack of clarity, not a lack of data (Daft & Lengel, 1986). The seven-word message in the opening scenario was never an uncertainty problem — no function was missing information about what the CEO had said. It was an equivocality problem: a message genuinely open to multiple internally coherent interpretations, each one a legitimate reading of the same words, none of them obviously wrong on its own terms. Daft and Lengel's framework predicts, correctly, that sending the message more often would not resolve this — repetition adds volume to a channel that was never data-constrained in the first place, leaving the actual ambiguity precisely where it started.

A third condition belongs alongside these two, and it is worth stating precisely because it is not one Daft and Lengel's own framework was built to address, and this article does not attribute it to them: coordination failure, where people may have arrived at genuinely compatible or even identical interpretations of a message, and the actions each person or function takes in response still fail to fit together. This is the article's own analytical addition to the uncertainty-equivocality distinction, not an extension of Daft and Lengel's original theory, which concerned information requirements rather than the downstream coordination of already-interpreted decisions. The three conditions call for genuinely different responses: uncertainty is resolved by acquiring more data; equivocality is resolved by richer, two-way exchange capable of narrowing which interpretation is intended; coordination failure is resolved by neither, because the interpretations may already be sound — what is missing is a mechanism for checking whether independently reasonable interpretations remain compatible with each other once each is acted on. Much of what gets diagnosed as a communication problem in ordinary executive conversation is, on closer inspection, one of these three genuinely different conditions wearing the same complaint.

This distinction reframes the entire executive question this article investigates. It is tempting, and intuitively appealing, to treat a communication gap as a volume problem — more town halls, more emails, more repetition of the strategic priority. Daft and Lengel's framework suggests this instinct is aimed at the wrong mechanism whenever the underlying problem is equivocality rather than uncertainty, which is precisely the condition a short, memorable, strategically abstract statement like "we are becoming customer-centric" is most likely to produce. The message was maximally repeatable specifically because it was short and abstract — and it was equivocal for exactly the same reason.

It is worth being precise about what would make a message like this less equivocal, since the fix is not simply adding words. Daft and Lengel's framework points toward richer, higher-bandwidth communication channels — direct dialogue capable of carrying feedback and clarification in real time — as the appropriate response to genuine equivocality, as distinct from the leaner, broadcast-style channels well suited to resolving uncertainty. A seven-word strategic statement, delivered through a slide and an all-hands announcement, is a lean channel applied to what was, from the start, an equivocality problem — which is precisely why no amount of additional lean-channel repetition was ever going to resolve it, and why a structured, two-way check across functions is a categorically different intervention than a clearer or more frequent version of the same broadcast.

A further distinction worth making explicit, building directly on the preceding section: communication, in the narrow sense of a message being sent and received, is not the same accomplishment as understanding, in the sense of a shared operational meaning actually forming on the receiving end. An organization can have excellent transmission — every function heard the same seven words, accurately, with no technical failure anywhere in the channel — while understanding remains genuinely fragmented, precisely because transmission and interpretation are two different processes, and success at the first guarantees nothing about the second.

This also clarifies a related and frequently conflated pair: clarity and agreement are not the same thing either. A message can be stated with complete clarity — unambiguous wording, no jargon, no vagueness in the sentence itself — while still producing genuine disagreement, or in the opening scenario's case, genuine divergence, about what it operationally requires. Clarity describes the message. Agreement, or its absence, describes what happens once different people, in different functional contexts, apply that clear message to their own specific decisions. The seven-word statement was clear. What it required of Finance specifically versus what it required of Product specifically was never, and could never be, resolved by the clarity of the sentence alone.

A handful of further terms this article relies on deserve explicit separation, because ordinary executive language routinely treats them as interchangeable in ways that obscure the specific mechanism this article investigates.

Information volume and information usefulness are not the same measure. A message can arrive in enormous, comprehensive detail and still fail to resolve which of several interpretations was intended, if the added detail elaborates the message without addressing its actual ambiguity — precisely the pattern Daft and Lengel's equivocality concept predicts and O'Reilly's overload findings reinforce from a different angle.

Message consistency and message repetition are similarly distinct, and the difference matters directly for the opening scenario. Repetition means saying the same words again. Consistency means the accumulated pattern of decisions, resource allocation, and measurement surrounding the message continues to point in the same direction the message described. A leadership team can repeat a message with perfect fidelity while allowing everything around it — what gets funded, what gets measured, what gets rewarded — to remain unchanged, producing exactly the multi-signal conflict described later in this article, where repetition is high and consistency, in the sense that actually matters, is not.

Transparency and indiscriminate disclosure are worth separating as well, because the instinct to solve a meaning gap by simply sharing more — more context, more background, more of the reasoning behind a decision — is not the same thing as sharing the right information to resolve a specific ambiguity. Transparency, in the sense worth preserving, means the information that would actually help someone correctly interpret a decision is available to them. Indiscriminate disclosure means volume without regard to whether it addresses the actual interpretive gap, and per O'Reilly's overload research, more disclosure of the wrong kind can degrade rather than improve the quality of the resulting interpretation.

Finally, coordination and communication are not the same activity, though they are closely related and often conflated. Communication is the transmission of a message. Coordination is the ongoing, active alignment of what different parts of an organization are actually doing in response to it — which, as this article has argued throughout, requires considerably more than transmission alone, and can fail entirely even where communication, narrowly defined, has succeeded without any apparent flaw.

A further, practical question follows directly from the uncertainty-equivocality distinction this article has developed: not only what to communicate, but through which channel — and Daft and Lengel's original framework was, in its first form, precisely a theory about matching channel richness to the kind of information problem at hand (Daft & Lengel, 1986). A lean, broadcast-style channel — an email, a slide, a posted announcement — is well matched to resolving uncertainty, where the content simply needs to arrive intact. A richer channel — direct conversation, capable of carrying real-time feedback, clarifying questions, and visible reaction — is what their framework identifies as appropriate for equivocality, precisely because resolving ambiguity requires the kind of iterative exchange a one-directional channel cannot support.

This gives the channel-choice question a more precise shape than "which tool should we use." A status update genuinely is well served by a dashboard or a written report — the underlying content is uncertainty-reducing, not equivocal, and a lean channel handles it efficiently. A genuinely ambiguous strategic priority, capable of multiple coherent interpretations, is poorly served by that same lean channel, however well-written, for exactly the reason this article's opening scenario illustrated: the channel can transmit the words perfectly and still leave the equivocality completely unresolved, because resolving it was never something a one-directional channel could do.

It does not follow that richer channels are simply superior and lean ones should be abandoned — richer channels are also slower, harder to scale across a large organization, and can themselves become a bottleneck if applied indiscriminately to genuinely low-ambiguity content that a lean channel would have handled perfectly well. The executive question worth asking about any specific communication is not which channel is generally best, but whether the channel actually chosen matches the kind of problem — uncertainty or equivocality — the content in question actually presents. A leadership team that has never asked this question explicitly is likely matching channels to convenience and habit rather than to the specific communication problem at hand, and has no particular reason to expect the match to be a good one.

This connects to a further, genuinely counterintuitive finding worth taking seriously precisely because it cuts against a strong executive instinct. Charles O'Reilly's 1980 study in the Academy of Management Journal examined how individuals actually respond to information overload in organizational decision-making, and found that perceived information overload was associated with higher satisfaction but lower decision-making performance, compared to perceived information underload (O'Reilly, 1980).

The satisfaction finding is worth sitting with, because it explains a specific executive trap. More communication — more updates, more context, more detail added to an already-repeated message — tends to feel like progress to both the sender and, per O'Reilly's finding, even to the receiver, who reports higher satisfaction under conditions of greater information volume. The same research found that this increased volume was associated with worse decision performance, not better — a pattern consistent with, though distinct from, the equivocality problem Daft and Lengel describe: more information does not, by itself, resolve which of several plausible interpretations is the intended one, and can instead simply add more material for each function to selectively use in support of the interpretation it had already, independently arrived at.

This is precisely the trap in the opening scenario. Additional communications about the customer-centric priority, issued in the following quarters, did not resolve the divergence — because the divergence was never a data problem the additional communications could correct. Each function, having already formed its own operationally coherent interpretation, absorbed the additional messaging as confirmation of the interpretation it already held, rather than as a correction toward a shared one. Leadership, observing that the message continued to be actively communicated and apparently well received, reasonably but mistakenly read the ongoing communication activity itself as evidence of communication effectiveness — precisely the confusion this article's central argument is built to correct.

It is worth being precise about what O'Reilly's finding does and does not establish, in keeping with the discipline this Journal applies throughout. The study is not a claim that all additional information is harmful, or that leaders should communicate less as a general policy — plenty of situations are genuinely uncertainty problems, in Daft and Lengel's specific sense, where more relevant data does resolve the gap. The finding is narrower and more specific: under conditions of already-high information volume, further increases were associated with lower decision performance despite higher satisfaction, a pattern that should make a leader specifically suspicious of the intuition that a communication gap is best addressed by simply producing more communication, without first diagnosing whether the underlying problem is a shortage of data or a shortage of shared interpretation.

A further, deeper theoretical account of why this happens comes from organizational sensemaking research discussed elsewhere in this Journal in a different context. Karl Weick's broader body of work, synthesized with Kathleen Sutcliffe and David Obstfeld in a 2005 Organization Science paper, characterizes sensemaking as oriented toward plausibility rather than accuracy: people and groups construct a workable interpretation of ambiguous circumstances, and once a sufficiently plausible interpretation is found, the active search for a better one characteristically stops (Weick, Sutcliffe, & Obstfeld, 2005).

Applied specifically to the communication problem this article investigates, rather than the attention-allocation problem this Journal's research on organizational blind spots examined, the implication is precise: each function in the opening scenario did not passively receive a meaning that was somehow missing from the message. Each function actively constructed a meaning, using the resources most immediately available to it — its own operational priorities, its own existing metrics, its own recent conversations — and stopped constructing further the moment that meaning felt coherent enough to act on. This is not a failure of listening. It is sensemaking operating exactly as the theory describes it operating, applied independently and in parallel by five different functions with five different sets of immediately available interpretive resources, producing five different, individually plausible, and mutually incompatible results.

This Journal's research on strategy implementation examined in detail how middle managers translate strategic intent into operational reality, distinguishing that translation function from simple message relay. The specific version of that mechanism relevant to communication itself concerns meaning rather than priority-setting: a middle manager receiving a centrally issued message does not relay it unchanged. They translate it — necessarily, because the central message was never specific enough to remove the translation step, and translation is the only mechanism by which an abstract statement becomes a concrete instruction for a specific team.

Steven Floyd's research on strategic consensus, discussed in this Journal's prior work, found that relatively few middle managers, across the organizations his research examined, articulated the same operational goals as their superiors — not through disagreement, but through the accumulated effect of independent, locally reasonable translation (Floyd, 1992). Applied to communication specifically, this means the seven-word message in the opening scenario was translated not once but many times, once per team, each translation independently plausible and each one, by the ordinary mechanics of translation, capable of diverging slightly from every other. The divergence this article's opening scenario describes at the functional level compounds further at the team level below it, in a pattern no single act of communication, however clear, is positioned to prevent on its own.

A concrete illustration makes the mechanism less abstract. A regional manager, translating the customer-centric priority for their own team, reasonably emphasizes faster response times, because response time is the metric their own local customers complain about most. A product manager, translating the identical message, reasonably emphasizes feature requests, because that is the channel through which customer voice actually reaches their desk. Neither translation is wrong given what each manager can see from where they sit — each is a locally rational reading of an intentionally general message, applied to genuinely different local evidence. The divergence is not a failure of either manager's judgment. It is what happens, structurally, when the same abstract instruction is translated independently by people who each have accurate but different local evidence to translate it against.

A specific and easily missed feature of this pattern deserves direct attention: each function's interpretation in the opening scenario was not sloppy, careless, or obviously mistaken. Sales's read — more customer contact — is a coherent, defensible operationalization of "customer-centric." So is Operations's read, and Finance's, and Product's, and Support's. Each interpretation, examined individually, survives scrutiny. The problem is not that any one function got it wrong. It is that five internally coherent, individually defensible interpretations do not automatically add up to one coherent organizational strategy, and nothing in the process that produced any single interpretation was designed to check it against the other four.

This connects the communication problem this article investigates to the aggregation logic developed elsewhere in this Journal's research: a company-wide sense that "the customer-centric message has landed" — measured, for instance, by whether people can recite it accurately, which is a transmission measure — can coexist with substantial, costly divergence in what it actually means operationally across functions, precisely because transmission success and meaning convergence are different things, measured differently, and an organization checking only the former has no way of detecting the latter.

It is worth stopping here to correct a conclusion this article has not intended and does not support: that different functions arriving at different interpretations of the same message is itself the problem, and that the goal should be identical interpretation everywhere. It is not, and treating uniformity as the target would be a genuine mistake. Sales, Operations, Finance, Product, and Support face materially different operating realities — different constraints, different customers, different failure modes — and a single abstract strategic statement should, correctly, be expected to require different local operationalizations to actually mean anything concrete in each of those contexts. An organization that somehow achieved word-for-word identical interpretation across every function would most likely have achieved it by making the original statement so specific that it could no longer function as a strategic priority at all, only as a set of five separate departmental instructions issued under one heading.

The executive question this article is actually built to raise, then, is not "do different interpretations exist" — they should, and their existence is not itself evidence of anything gone wrong. It is a more precise question: do these different, locally legitimate interpretations remain compatible with each other and with the underlying strategic intent, or have they diverged into something that will eventually produce the kind of costly friction the opening scenario described — and does leadership currently have any mechanism for discovering the difference before that friction becomes visible? Compatibility, not uniformity, is the actual target, and the entire value of the distinction developed throughout this article rests on keeping that target precise.

A further distinction worth making explicit, connecting to organizational silence research discussed in this Journal's earlier work: when a function's locally constructed interpretation of a strategic message eventually produces friction with another function's different interpretation — as it did, six months later, in the opening scenario — that friction is frequently not reported upward as a communication problem at all. Elizabeth Morrison and Frances Milliken's research on organizational silence describes a collective-level pattern in which concerns fail to travel upward, driven by a shared sense that raising them is unlikely to matter or unwise to attempt (Morrison & Milliken, 2000).

Applied here, the relevant silence is not necessarily about withholding disagreement with leadership — it is often simpler and more mundane than that: no one on the Sales team framed their interpretation as a hypothesis needing to be checked against Operations's interpretation, because nothing in the original communication invited that check, and raising "I'm not sure we all mean the same thing by this" can itself feel, in the moment, like an unhelpful or overly pedantic objection to a message everyone has already nodded along to. The silence here is not fear-driven in the sense this Journal's psychological safety research examines; it is a structural absence of any mechanism inviting the check in the first place; distinguishing the two matters because they call for different responses — better voice mechanisms will not fix a gap that no one has any structural occasion to notice.

The mechanisms this article has described operate at all times, in ordinary operation, but they become measurably more consequential during periods of organizational change, for a specific reason: change is precisely when an organization most needs its various functions to move in a coordinated direction based on shared meaning, and precisely when the messages describing the needed change are most likely to be abstract, aspirational, and equivocal in Daft and Lengel's specific sense — because a genuinely concrete, unambiguous statement of a new strategic direction would require a level of operational detail leadership rarely has fully worked out at the moment the change is first announced.

This produces a specific, recognizable pattern this article's sources would predict: leadership believes a transformation is progressing, because the message has been repeated, formally accepted, and referenced consistently in every relevant meeting — exactly the transmission-success signals available to leadership from where it sits. Operational teams, meanwhile, are quietly adapting their own local translation of that transformation to fit what they already know how to do, producing activity that looks, from below, like real progress and constitutes, in aggregate, several different and only partially compatible versions of the intended change. Neither leadership nor the operational teams are being dishonest with each other in this pattern. Both are accurately reporting what they can see from their own vantage point, and neither vantage point contains the information needed to detect the divergence between them.

A further, related pattern deserves separate attention: even where a single message is genuinely clear and well-interpreted, an organization typically receives many signals simultaneously, not just one, and those signals do not always point in a consistent direction. A stated priority to become customer-centric, arriving alongside an unchanged cost-reduction target, an unchanged quarterly revenue target, and an unchanged set of performance metrics that reward none of the specific customer-centric behaviors any function actually adopted, produces a genuinely different and more complex interpretive problem than the single-message case this article has focused on so far.

In this more realistic, multi-signal condition, each function is not simply interpreting one equivocal message in isolation — it is resolving a set of signals that may not be mutually consistent, and doing so, per Weick's sensemaking framework, by constructing whichever coherent story best reconciles the most operationally pressing signals it actually has to answer to. A function still measured and rewarded primarily on its pre-existing metrics will reasonably weight those metrics more heavily in its interpretation than an aspirational statement carrying no corresponding change in what gets measured — not from resistance to the new priority, but from the entirely rational observation that the new priority was never actually made comparably real in the organization's own measurement system.

Everything this article has argued so far could be misread as a case against communicating more, and that misreading deserves direct correction, because it is not the claim this article is making. More information genuinely reduces uncertainty in Daft and Lengel's specific sense of the term, and an organization facing a real gap in what it knows — not what it disagrees about, but what it has not yet found out — is correctly served by seeking more data, not less (Daft & Lengel, 1986). The argument this article has developed applies specifically to equivocality, where the problem is ambiguity of interpretation rather than absence of fact, and conflating the two conditions in either direction is exactly the imprecision this article has tried to correct.

Repetition, similarly, is not inherently wasteful. A message repeated consistently, without drifting in content each time, can genuinely build the kind of confidence and shared reference point this article's earlier discussion of consistency versus repetition was careful to distinguish from mere volume — the distinction was never that repetition is bad, only that repetition alone does not resolve equivocality, which is a narrower and more defensible claim. Transparency, likewise, can build real legitimacy when it shares the specific reasoning someone needs to correctly interpret a decision, and documentation genuinely preserves organizational memory that would otherwise be lost the moment the people who held it moved on or left.

Meetings deserve the same fair treatment. A meeting convened specifically to resolve genuine equivocality — where the value lies precisely in real-time, two-way exchange rather than one-directional transmission — is doing exactly what Daft and Lengel's richer-channel logic predicts it should. The same is true of middle-management translation and local interpretation, both discussed earlier in this article primarily as sources of potential drift: translation can also, and often does, improve a strategy by incorporating operational knowledge the original statement could not have contained, and local interpretation that stays connected to the organization's broader intent is adaptation, not failure, a distinction this Journal's research on strategy has developed in a related context.

Even silence is not universally a problem to be corrected. Some silence genuinely reflects that a piece of information was not significant enough to escalate, and an organization that treated every instance of something not being raised as evidence of a communication failure would be chasing a signal that, in a meaningful share of cases, simply is not there. The distinction this article has tried to maintain throughout — between silence as structural absence of a pathway and silence as evidence of a deeper problem — cuts both ways: it means some silence deserves real scrutiny, and it means an organization does not owe an explanation for every occasion nothing was said.

The honest version of this article's thesis is therefore narrower than "communicate less" or even "communicate differently." It is that the specific gap between transmission and meaning this article has described is real, structurally likely even under conditions of clear and well-received communication, and largely invisible to leadership from where it naturally sits — not that every instance of additional communication, repetition, translation, or silence is evidence of that gap. Mismatched architecture, not communication volume itself, is the actual target.

Everything this article has described is, almost by construction, difficult for a leader to observe directly from their own position. A leader who has communicated a message clearly, repeatedly, and received consistent formal acceptance of it has, from their own vantage point, no direct signal that five functions have quietly constructed five different operational meanings for it — the transmission-success indicators available to leadership and the meaning-divergence problem this article describes are simply not measured by the same instrument.

This is the same structural pattern this Journal's research on organizational blind spots has examined in a different context: the gap is not visible from where a leader naturally stands, and closing it requires a deliberate, structured comparison across the specific vantage points where the divergence would actually show up — not a better-worded version of the original message, and not more of it.

This is the specific measurement gap Klarwerk's Communication dimension is built to surface a structured signal about, and the boundary of that signal is worth stating with the same precision applied throughout this article. The relevant survey items ask participants, anonymously and in aggregate, about their own experience of whether information reaches them while still current, whether important context travels as far as it needs to, and whether what they understand to be the organization's priorities is something they could describe with confidence — a structured, self-reported proxy for exactly the transmission-versus-meaning gap this article has described, not a direct observation of any specific conversation, email, or meeting.

Where department-level comparisons show this dimension diverging materially between functions that received the identical central communication, or where the platform's Executive Tensions logic identifies a gap between a strong Strategy & Alignment score and a weaker Communication signal, that combination is surfaced as a disclosed pattern worth direct investigation — consistent with, though never proof of, exactly the kind of local-translation divergence this article's opening scenario illustrated. This is detection, not diagnosis, in the sense this Journal's other research has been careful to distinguish: the platform can surface that a divergence pattern exists. It cannot determine which specific message produced it, whether the divergence reflects necessary local adaptation or genuine drift, or which department's interpretation, if either, is closer to what leadership actually intended. Research evidence establishes why this divergence is structurally likely even under conditions of clear, well-received communication. Executive interpretation is the responsible next step once a pattern is surfaced, not the assessment itself. What Klarwerk can observe is a structured, anonymized signal of how people across different functions currently report experiencing information flow and shared understanding. What Klarwerk cannot determine is equally important to state without qualification: it does not measure communication quality as a complete construct, does not observe actual conversations, emails, or meetings, cannot determine what any specific individual misunderstood, does not identify an individual communication failure or its source, does not establish causation between a specific message and a specific downstream divergence, and does not predict how a future communication will be received.

One further distinction deserves to be made explicit, because it is easy to assume that solving the meaning-gap problem this article has described would, by itself, solve an organization's coordination problems — and that assumption does not hold. Communication is the transmission and, ideally, the shared construction of meaning this article has been examining. Coordination is the further, separate accomplishment of different people's actions actually fitting together toward a common outcome. The first can succeed completely while the second still fails.

Consider a case where everyone genuinely does share the same operational meaning of a priority — the equivocality has been resolved, the interpretation is aligned, no divergence exists. Coordination can still fail if no one has settled who owns a specific decision, if two teams both correctly understand the priority but neither knows the other is already acting on it, or if everyone can accurately describe the same KPI while quietly optimizing for a different lever that happens to move it. This is a different failure mode than anything discussed earlier in this article, closer to the coordination-mechanism territory this Journal's research on organizational friction addresses directly — and it is worth naming the boundary precisely rather than letting the two subjects blur together. This article's territory ends at shared meaning. What an organization does once meaning is genuinely shared — how it assigns ownership, resolves dependencies, and reconciles simultaneous action — is a separate, adjacent problem, real and consequential, but not the one this article has been built to answer.

The following uses the same illustrative Meridian Logistics scenario referenced elsewhere in this Journal — hypothetical and demo-based, not a real customer, used here only to make the mechanism concrete.

Picture Meridian's company-wide Communication score registering in a moderate, unremarkable range — not alarming, not obviously strong. A department-level view shows this average obscuring real variation: one function reports meaningfully lower confidence that it understands current priorities than the rest of the organization, while its own Execution Index remains strong — a function executing capably and consistently, on its own internally coherent understanding of what it should be doing, which department-level data alone cannot confirm is the same understanding held elsewhere. The responsible next step is not to conclude that this function has been poorly managed or that a specific message failed — the assessment does not, and structurally cannot, support that conclusion. It is the same kind of specific, falsifiable question this Journal's research has modeled throughout: if we asked this function, independently and without prompting, to state in its own words what our current top priority requires of it, and asked two other functions the identical question, would we get compatible answers, or three coherent, defensible, and quietly incompatible ones?

What would validate this reading, and what would challenge it, is worth stating explicitly. What would validate it: independently asking the three functions and finding genuinely different operational translations of the same stated priority. What would challenge it: discovering the lower score traces to a recent, unrelated disruption in that function rather than a genuine meaning gap, or that the function's own leadership already knows its interpretation differs and considers the difference intentional and appropriate. The score can only point toward the question worth asking. It was never going to be able to answer it.

The following questions are intended for a direct leadership conversation, each surfacing a different mechanism this article has described.

1. If we asked three different functions, independently, to describe in their own words what our most recent strategic message requires of them specifically, would we get compatible answers?

2. Is our most important current message equivocal — genuinely open to multiple coherent readings — or simply under-communicated? Those require different fixes, and repeating an equivocal message will not resolve it.

3. Which of our performance metrics currently reward behavior that quietly contradicts our most recently stated priority, whether or not we intended that?

4. When leadership feels confident a message has landed, what specific evidence is that confidence actually based on — and is it a transmission signal or a meaning signal?

5. Where might two parts of this organization currently be executing capably on two different, internally coherent, and quietly incompatible understandings of the same stated priority?

None of the mechanisms this article has described suggest that leadership communicated poorly in any conventional sense, and a leader who concludes from this article that the fix is simply clearer writing or more frequent repetition has, per Daft and Lengel's own framework, correctly diagnosed neither the mechanism nor the remedy. Nor should this article be read as counsel to communicate less, translate less, or treat every silence with suspicion — this article has been explicit that each of these can be exactly the right response to the right condition, and the discipline it asks for is matching the response to the condition, not defaulting to less activity as though volume itself were the problem. A message can be clear, well-received, formally accepted, and repeated consistently, and still fail to produce shared operational meaning — not because anything about the communication was deficient, but because meaning is not something a message delivers on its own. It is something each recipient actively constructs, using whatever interpretive resources are locally available to them, and stops constructing the moment a coherent-enough answer is reached.

That reframing carries real, practical consequence. The question worth investigating is not "did we communicate this clearly enough," which the opening scenario's leadership team could answer yes to with complete honesty. It is "do we actually know whether the meaning different parts of this organization constructed from that communication are the same meaning" — a question no amount of additional repetition can answer, and one that requires, instead, a deliberate, structured check across exactly the vantage points where a plausible, well-intentioned divergence would otherwise stay invisible until it had already become expensive.

The advantage belongs to leadership teams willing to treat their own confidence that a message has landed as a hypothesis worth checking, not a conclusion the act of communicating has already earned.

This is, in the end, a more achievable standard than the one most leadership teams have implicitly set for themselves. Leadership cannot eliminate interpretation differences, and the preceding sections have argued at length that it should not try to — local interpretation is where an abstract strategy becomes real, situated work, and some divergence across functions is the ordinary, healthy cost of that translation happening at all. What leadership can do is build a disciplined, repeatable way of discovering when those differences have quietly moved from compatible to costly, before that shift is only visible in the friction it eventually produces. That is a narrower ambition than "perfect shared understanding," and for exactly that reason, a genuinely reachable one.