Everyone in the Room Agreed. That Was the Problem.
- Aug 7
- 6 min read
Updated: Aug 19
A specialty manufacturer, a little over $400 million in revenue, approves an initiative at the March leadership meeting: simplify the order-to-delivery process and cut lead times by thirty percent.
The discussion is thorough. Concerns are raised and answered. The wording is refined twice before the vote.
Every executive leaves believing the team is aligned.
By June, the initiative is incoherent.
Sales has been removing approval gates on custom configurations so quotes go out faster.
Finance has been eliminating configurations altogether, on the reasoning that variation is what makes the process slow.
Operations has been consolidating handoffs on the plant floor and reports it is ahead of schedule.
IT has scoped a system-of-record consolidation that will not deliver anything until next year.
Every one of them is executing the decision that was approved. Two are directly undoing each other's work. No one was careless. No one misheard.
They were not working from different intentions:
They were working from different representations of the business.
A representation is the internal model a person reasons with, not their opinion about the business, but the structure they use to think about it at all.
The instinct on first encountering the idea is to treat it as a defect to be corrected. It isn't. No one can "reason" directly about a $400 million enterprise; the thing itself is too large, too distributed, and too fast to be held in a human head.
Every executive in that room was necessarily operating on a compressed model of the company, and had to be.
Representations are not a flaw in cognition.
They are the mechanism of cognition.
The question is never whether people are using them: it is whether the ones in play are compatible. That question is almost never visible during discussion.
The explanations that don't survive contact
The standard accounts are familiar: better communication, better alignment, better buy-in. The difficulty is that this company already had all three:
The decision was documented.
It was cascaded.
Each executive had committed to it publicly, in a room with their peers.
If those were the operative variables, the failure should not have been possible yet it recurs, at the same organizations, under leaders who are demonstrably good at their jobs.
When a remedy is applied thoroughly and the failure persists,
the diagnosis is usually wrong.
Nothing you say ever arrives
You form an intention.
You encode it into language: a lossy compression, performed under time pressure, against a vocabulary you share only approximately with your listener.
The words travel. Your listener reconstructs a meaning.
That last step is where the trouble lives, and it is the step we systematically overlook.
Communication is not the transfer of meaning.
It is the transfer of symbols from which meaning is reconstructed.
The reconstruction happens at the far end, out of materials the receiver already had. Those materials are their representation. And a representation has structure.
This is where the idea stops being psychological and becomes useful, because the components can be named:
Boundaries: where the thing being discussed starts and stops
Entities: what the moving parts are
Causal assumptions: what produces what; what must change for an outcome to change
Priorities: what gets sacrificed when two goods conflict
Constraints: what is treated as immovable rather than negotiable
Run the March decision through that structure and the divergence stops looking mysterious:
The sales leader's boundary on "order-to-delivery" opens when a customer first asks for a price.
The operations leader's boundary opens at release-to-floor – everything earlier belongs to someone else's problem.
Their causal assumptions diverge just as cleanly:
To the CFO, variation generates delay, so removing configurations is simplification.
To the sales leader, approval gates generate delay, so protecting configurations while removing gates is simplification.
Both readings are faithful to the approved initiative: each implies a program of work that damages the other.
Why trying harder doesn't fix this
If representations are the source of the divergence, then nearly every standard leadership remedy is aimed at the wrong layer. Better messaging, more repetition, more forums, more explicit commitment: all of it operates on the transmission. Even perfect listening would not solve it.
Two people can receive the same sentence
with complete fidelity and reconstruct incompatible meanings,
because the divergence lives in the priors they decode against,
not in what passed between them.
And there is no felt sensation of misunderstanding. Each party experiences comprehension. The internal signal that would normally prompt a clarifying question never fires precisely because each reading is internally consistent.
This is a structural property of how humans communicate, not a deficiency in any particular set of humans. Which is why interventions that treat it as a deficiency reliably fail to move it.
Agreement is cheap. Divergence is expensive.
The economics are unforgiving:
Agreement is produced in the room, in minutes, at almost no cost.
Divergence is discovered in execution, months later, after work product exists, budget is committed; and reversal carries a political price.
Worse, the language that survives an executive discussion is selected for its capacity to hold multiple readings. Watch a decision get drafted:
A specific formulation is proposed.
Someone objects, because under their representation it implies a consequence they cannot accept.
The wording is broadened until the objection dissolves.
This repeats until no one objects: what remains is a sentence compatible with every representation in the room, which is another way of saying a sentence stripped of exactly the content that would have exposed the incompatibility.
"Simplify. Streamline. Phased. Customer-first." These words reach consensus quickly for a reason. They are not lazy language. They are efficient instruments for producing agreement without resolving disagreement, and the room rewards them for it.
Set against that, look at where the organization spends its governance. Enterprises invest heavily in systems that manage execution: portfolio reviews, stage gates, status reporting, variance analysis, PMOs. Nearly all of it activates after interpretation has already happened, and none of it examines whether the interpretations were compatible to begin with.
Every organization governs execution.
None governs interpretation.
The consensus in that March meeting was real. It was agreement about a string of words, not about a course of action, and nothing in the company's operating machinery was designed to tell the difference.
What would have to be true
The permanent part of this is that representations differ and cannot be merged. But that they differ and whether the difference matters for this decision are separate questions, and the second one is answerable. What would it take to answer it before execution rather than after?
Externalization. Private reconstructions have to become explicit artifacts — not paraphrases of the decision, which only reproduce the ambiguity, but the underlying structure: where the boundary sits, what causes what, what gets sacrificed under conflict.
Normalization. Two executives will describe their models in different functional vocabularies. Left in native form they cannot be compared, because each reader silently translates the unfamiliar description into their own terms and concludes, wrongly, that they agree. Making heterogeneous descriptions structurally comparable is the hard part, and no meeting performs it.
Correspondence. Once comparable, differences can be tested for real incompatibility rather than absorbed by charitable reading, which is exactly what a meeting does, and what makes divergence invisible in the room.
Preservation. The output is not a merged model. Some divergences are benign, some productive, a few fatal. The work is separating them, not eliminating them.
The obstacles are real. Natural language will absorb a difference rather than expose one, given the chance.
Most organizations have no shared frame in which
two executives' answers are even structurally comparable.
And senior time is scarce, which rules out anything requiring a workshop. None of that makes the problem intractable. It makes it an instrumentation problem.
The claim, stated carefully
I am not claiming representations can be unified, or that a well-run organization achieves shared meaning. Both are false, and any method promising them deserves suspicion.
The claim is narrower: representations can be made structurally observable, compared, and tested before execution begins.
Organizations don't fail because people think differently. Everyone already knows people think differently, which is why the observation on its own changes nothing. They fail because they have no reliable way to determine whether those differences are compatible with the decision just approved, while the answer is still cheap to act on.
Most never test it. They observe agreement in the room, treat agreement as evidence of alignment, and meet the gap between the two around month four, where it arrives disguised as an execution problem, a resourcing problem, or a problem with a particular leader.
It was none of those. Everyone agreed. That was the problem.
If recurring friction persists despite real investment in leadership, strategy, culture, or transformation, the cause may not be where you've been looking.
I work with CEOs and executive teams to diagnose the representational gaps beneath the surface – the incompatible pictures of the enterprise that produce friction long before it looks like a people problem – and to build the coherence that lets trust, execution, and performance actually hold.
If you'd like to explore what's really driving your organization's friction, let's start a conversation: ted@tedwhetstone.com
Comments