The Myth of Shared Understanding

Category: Team dynamics Shared language often hides very different interpretations.

A team agrees, in a meeting that everyone leaves feeling good about, that the new feature needs to be “simple.”

Everyone nods. It is a sensible word. It is hard to be against simplicity. The designer hears “simple” and pictures a clean, minimal interface with most of the options stripped out. The engineer hears “simple” and pictures a small, contained build with no new infrastructure, which to her means reusing the existing components exactly as they are — buttons, menus and all. The product manager hears “simple” and means simple for the customer to understand, which he assumes will require careful explanatory copy, a short tour, and a few well-placed prompts. The person who actually asked for it, the commercial lead, hears “simple” and means cheap and fast.

Four people. One word. Four genuinely different briefs. And because the word they all used was the same, every one of them walked out of that room believing the matter was settled. They did not just fail to disagree — they each came away with positive confirmation that the others were on board, because the others had said the very thing they themselves were thinking. The agreement felt unusually strong precisely because the word was doing so much hidden work.

The gap did not surface in the meeting. It did not surface in the week that followed, when each of them went away and worked diligently toward their own version of the brief — the designer paring the interface back, the product manager scoping a tour, the engineer keeping the build tight, the commercial lead reassuring the customer it would be quick. Every one of them was, by their own lights, delivering exactly what had been agreed. Every one of them was being a good colleague. The very diligence that should have been reassuring was, in fact, four people walking confidently in four directions.

It surfaced at the demo, when the designer’s stripped-back interface collided with the product manager’s explanatory tour, neither of which was cheap or fast, and none of which the engineer had built infrastructure for. At that point the conversation that should have happened at the start finally happened — except now it happened over a thing already half-built, with deadlines attached and tempers shorter, and everyone privately convinced that the others had quietly changed their minds.

Nobody had changed their minds. They had never held the same one. The word “simple” had let them skip the conversation that would have revealed they disagreed, and they had mistaken the skipping of it for the resolving of it.

The Principle

A shared word is not a shared understanding. When people agree on language, they very often agree only on the language — each filling the same word with their own private meaning — and the difference stays hidden until the work forces it into the open, usually at the worst possible moment.

Words are compression. “Simple,” “soon,” “done,” “good enough,” “robust,” “aligned,” “MVP,” “high quality” — each one stands in for a whole cloud of specific expectations, and each person unpacks it back into their own cloud, not yours. The agreement is real at the level of the word and absent at the level of the meaning. The trouble is that we experience agreement-on-the-word as if it were agreement-on-the-meaning, and we feel the relief and the closure that real alignment would bring, so we stop talking exactly when we most need to keep going.

Why It Is Inevitable

Shared understanding is expensive to build and a shared vocabulary is free to assume, so we almost always reach for the cheaper one and call it the same thing.

To genuinely confirm that two people mean the same thing by “robust” or “by Friday,” you have to slow down, make the implicit explicit, and risk discovering a disagreement you were getting along fine without. Agreeing on the word costs nothing and feels productive. It moves the meeting along. It lets everyone leave with the satisfying sense that a thing has been decided. The incentives in the moment all push toward the surface agreement and away from the deeper test.

There is a second, quieter reason. Each person assumes their own interpretation is the obvious one — not an interpretation but simply what the word means — so it does not occur to them that anyone could be hearing something different. The engineer is not aware she is choosing one meaning of “simple”; from the inside it just is the meaning. This is why the gap is so hard to spot in the room: nobody is suppressing a known disagreement, the way they might in a false consensus. There is no felt disagreement at all. Everyone is sincerely, confidently aligned with a version of the plan that lives only in their own head.

And language rewards the illusion. The more abstract and agreeable a word is, the easier it is to say yes to, and the more different things it can quietly contain. “We’re aligned on the vision” is almost always true at the level it is said and almost always untested one layer down, because the words chosen are precisely the ones general enough that everyone can endorse them without anyone having to mean the same thing. We even reach for these words on purpose, though we would rarely admit it — when a real definition would expose a disagreement we don’t have the time or appetite to resolve, a comfortably vague word lets the meeting end on a note of agreement and leaves the disagreement intact for someone else to discover later. The abstraction is not always an accident. Sometimes it is the path of least resistance dressed up as consensus.

There is also the simple fact that we are usually in a hurry. Pinning down what “done” means feels like pedantry when there is real work waiting to be started, and the person who insists on it can look like they are slowing things down or failing to trust their colleagues. So the test gets skipped, not because anyone is careless, but because the cost of skipping it is invisible today and the cost of running it is felt immediately, by the person who runs it, in the form of a slightly more awkward meeting.

How It Shows Up

• Everyone leaves the meeting happy, and the disagreement appears only when something concrete has to be produced.
• “That’s not what I meant by that” — said with genuine surprise, late, over work already done.
• The same word — done, ready, simple, soon — used confidently by people who, it turns out, were describing different things.
• A spec or brief that everyone signed off on and everyone now reads differently.
• Two people who think they’re arguing about a decision when they’re actually arguing about a definition.
• Hand-offs that go wrong not because anyone failed to do their part, but because each did their version of the part.

Why It Causes Damage

The damage is severe because the failure is invisible right up until it is expensive. An open disagreement is a problem you can see and work on. A hidden non-agreement looks exactly like agreement, so it consumes no attention, raises no flag, and gets actively built upon — plans laid, work scheduled, commitments made — all resting on a shared understanding that does not exist. The flaw is laid into the foundations and then paved over with confidence.

It also surfaces at the worst possible time. The mechanism that finally exposes the gap is the work itself — the demo, the delivery, the integration, the moment of contact with reality — which is to say it surfaces after the cost of fixing it has multiplied. The conversation that would have taken ten minutes at the whiteboard now takes a fraught afternoon among people who feel let down, because each of them kept their side of a bargain that was never actually struck.

And it poisons trust on the way out. Because everyone genuinely believed they had agreed, the divergence reads as betrayal or incompetence rather than as a definition that was never pinned down. “You said you’d keep it simple.” “I did keep it simple.” Both are telling the truth, and neither can see it, and the relationship pays for a failure of language that gets misfiled as a failure of character.

How To Counter It

• Test for meaning, not for assent. After “are we agreed?”, ask each person to say in their own words what they think we just agreed to — the differences fall out immediately, and cheaply.
• Make the abstract concrete. Force the slippery word down to something specific: not “simple,” but “no new screens and no copy longer than a sentence”; not “soon,” but “a date.” If a word can’t survive being made concrete, it was hiding a gap.
• Use examples and counter-examples. “So this would be in scope, but that wouldn’t — yes?” A single concrete instance pins down a definition faster than any amount of discussion of the definition itself.
• Be most suspicious of the easiest agreements. When a word goes through a room with universal, frictionless nodding, treat that as a reason to check, not a reason to relax. Frictionless usually means untested.
• Write it down and read it back — not to create a record, but to discover the gap. Ambiguity that survives a conversation often dies the moment someone has to commit it to a single sentence everyone has to look at.
• Confirm meaning at the hand-off, not just at the start. Understanding drifts as work moves between people; re-state what “done” means each time the thing changes hands.

What Good Looks Like

Teams that treat agreement as a hypothesis to be tested, not a state to be reached. Where the response to a quick, warm “great, we’re all agreed” is a habitual, unembarrassed “let’s just check we mean the same thing” — and where that check is understood as diligence rather than distrust. Where the load-bearing words in any plan are deliberately dragged down from the abstract to the concrete before anyone builds on them.

In those teams, disagreements still happen — but they happen early, at the cheap end, over a whiteboard rather than over a delivery, while opinions are still cheap to change and nobody has yet invested a fortnight in their own private version of the plan. The arguments are louder at the start and far quieter at the end, which is exactly the right way round.

Shared understanding still has to be built — it never comes free with the shared words — but it gets built on purpose, while it is still affordable, rather than discovered to be missing once the cost of its absence has already come due.

A Reflective Question

Think of a word at the centre of something you’re currently working on — done, good, simple, soon, aligned. If you asked each person involved to define it concretely, in their own words, without hearing the others first — are you confident the definitions would match, or are you assuming they would the same way everyone in that meeting assumed they had agreed?