The language matched. The reality didn’t.

The language matched. The reality didn’t.

Over the years I’ve sat in a lot of workshops, leadership sessions and planning discussions where the room appeared to reach alignment surprisingly quickly.

Sometimes the topic was growth. Sometimes adoption. Sometimes customer value. Sometimes a problem that everyone could feel but nobody could describe particularly well yet.

The organisations were different. The industries were different. The people around the table were different.

Yet a particular moment kept appearing often enough that I eventually started paying attention to it.

The discussion would begin with people sharing what they were seeing.

Sales would talk about conversations that were becoming harder to move forward. Marketing would bring market signals that seemed to point in a particular direction. Product teams would describe behaviour they were seeing inside the platform. Customer Success would add examples from implementations, renewals or day-to-day customer interactions.

For a while, everything would feel productive in the way good workshops often do.

People would build on each other’s points. Examples would trigger other examples. The room would gradually start converging around a particular idea.

Sometimes it was adoption.

Sometimes value.

Sometimes transformation.

Sometimes customer success.

The specific word wasn’t usually the interesting part.

What stood out was how quickly the room settled once a familiar term appeared.

People would nod. The discussion would accelerate. Different observations would begin attaching themselves to the same explanation. Compared to many organisational conversations, it often felt remarkably efficient.

Nobody was arguing.

Nobody seemed confused.

Nobody was pushing back.

If you left the room at that point, it would be difficult to identify a problem. Most people would probably describe the meeting as aligned.

It was usually only months later, when the consequences of that alignment started showing up in different parts of the organisation, that something else became visible.

Teams would move in slightly different directions.

Priorities would drift.

Different departments would talk confidently about the same objective while describing noticeably different outcomes.

Nobody had deliberately changed course.

Nobody was working against the agreed direction.

Yet somehow the organisation had still begun pulling itself apart around the edges.

That was the moment I kept finding myself coming back to.

Not the workshop itself.

What happened afterwards.

The comfort of familiar language

One of the reasons this is difficult to spot is that organisations naturally develop shared vocabulary over time.

Certain words become shorthand for much larger ideas. Eventually they stop feeling like words altogether and start feeling like established truths.

People talk about growth without needing to define it.

They talk about adoption, value, transformation, customer success, productivity, enablement or innovation in the same way.

The language becomes familiar enough that very little effort is spent revisiting what sits underneath it.

Most of the time that feels completely reasonable.

After all, if people have been using the same terminology for months or years, why would anyone assume they mean different things?

What I kept noticing, however, was that people were often arriving at those conversations from very different parts of the organisation.

A sales leader might spend most of their week inside customer conversations and buying processes. Product teams might be looking at usage behaviour, adoption trends and roadmap decisions. Customer Success might be spending their time helping customers operationalise change after implementation. Finance might be focused on economic outcomes and commercial performance.

Each group develops a legitimate understanding of the business from the reality they experience most often.

The difficulty is that those realities do not always overlap as neatly as the language suggests they do.

Agreement can be misleading

Most people assume misalignment announces itself through disagreement.

In practice, some of the most interesting examples I’ve seen looked like agreement.

The meeting ends smoothly.

The strategy deck makes sense.

The terminology remains consistent.

The actions appear clear.

Nothing feels obviously broken.

In fact, the stronger the shared language becomes, the easier it can be to believe everybody is working from the same understanding.

Then the friction starts appearing.

A product team invests in solving a problem that leadership thought had already been addressed.

Customer Success measures progress differently from Sales.

Marketing reinforces a message that seems sensible from a market perspective but lands differently once it reaches customers.

When people compare notes, the differences are often subtle rather than dramatic. Nobody is describing an entirely different business. Nobody is operating with entirely different objectives.

The variation exists in the interpretation.

The words survived.

The meaning underneath them shifted.

The drift is almost invisible

What makes this particularly awkward is that the drift rarely arrives all at once.

It accumulates through hundreds of small adjustments that all seem reasonable when viewed individually.

A team changes how it explains something because customers respond better.

A new leader introduces language that fits their previous experience.

A process evolves.

A market changes.

A customer problem becomes more important than it used to be.

The organisation adapts, which is exactly what healthy organisations should do.

The terminology often remains stable throughout all of this.

That stability creates a reassuring sense of continuity. Presentations still look familiar. Strategic updates still sound coherent. Dashboards still appear connected.

From a distance, very little seems to have changed.

Yet the amount of interpretation required to maintain that coherence quietly increases.

People spend more time clarifying what was meant.

More time translating between teams.

More time reconnecting discussions back to original intentions.

More time relying on experienced individuals who still remember where particular ideas came from before they spread across the organisation.

Most of the time, nobody notices this work happening because it becomes part of how the organisation functions.

What we kept noticing

The more I saw this pattern, the less interested I became in whether people were using the same terminology.

That turned out to be a surprisingly weak signal.

The more interesting question was whether people were describing the same reality.

Those are not always the same thing.

An organisation can achieve remarkable consistency in language while carrying significant variation in interpretation. In some cases, the consistency of the language actually makes the variation harder to see because it creates confidence that alignment already exists.

The conversations can sound aligned, the documents can look aligned, and the plans can appear coherent, even while different parts of the organisation are quietly solving different versions of the same problem and believing they are moving in the same direction.

Over time I found myself becoming less interested in what people said they agreed on and more interested in what they believed that agreement actually meant.

Because those are not always the same thing.

Sometimes the language matches perfectly.

And the reality underneath it doesn’t.