Communicating is not installing

There is a sentence you hear in almost every results meeting: “that has already been communicated.” It usually closes the discussion. And it is almost always true — the material was produced, the presentation happened, the attendance list is filed, the email went out with a read receipt.

What that sentence does not answer is the only question that matters: did the behaviour change where it counts?

The difference is about location, not quality

Communicating and installing are not two steps on the same ladder. They are different operations, and the difference lies in where the message comes to exist.

When a message is communicated, it exists outside the person. It lives in the deck, the video, the playbook, the memory of whoever was in the room. To reach the client it has to be retrieved — and every retrieval charges a toll. The person has to remember, choose to use it, translate it into their own words and sustain it under pressure. At every link in that chain, something is lost.

When a message is installed, it exists inside the person. It stopped being content and became a way of deciding. It does not need to be remembered, because it is not stored anywhere: it fires. It is the difference between knowing there is an argument about value and being someone who builds value before talking about price.

A communicated message depends on someone repeating it. An installed message is already the way of working.

Why the distinction is practical, not philosophical

It matters because it changes what you verify.

If the objective is to communicate, measuring reach makes sense: how many people were exposed, how many completed, what the satisfaction score was. Those are honest metrics for what they propose to measure — they describe the broadcast.

If the objective is to install, none of those measures serve, because they all stay inside the room. Verification has to happen where the behaviour should appear: on a real call, in an issued proposal, at a counter with a queue behind it, in a negotiation where the client asks for a discount. You do not verify installation by asking people whether they enjoyed it.

What this does not mean

It does not mean conventions, e-learning, playbooks or role-play are bad formats. Any of them can be part of an installation, and often are. A good event creates a window of attention no other format creates. A well-written playbook organises what was scattered.

The error is not in the format. It is in assuming that exposure, completion or participation are proof of behaviour. They are proof that communication happened — which is a different thing, and something we already knew.

The question that reorganises the problem

Before choosing any format, there is a question that is almost never asked with enough precision: which behaviour, exactly, needs to start existing — and where should it appear?

“The team needs to know the product better” is not an answer. “The salesperson needs to ask the second question, before showing the product, to find out what the client came for” is an answer — because it describes an observable scene, in a specific place, that someone can go and verify.

When the question is asked at that level, two things change. Choosing the format stops being a guess and becomes a consequence. And verification stops being optional, because the answer already contains the criterion.

That is why the distance between communicating and installing is not a matter of vocabulary. It is the difference between a strategy that exists in the document and a strategy that exists in behaviour — which is the only place a client can find it.