Main idea

When showing a roadmap to a customer, you believe you are distinguishing between what you announce and what you merely let them see. The customer makes no such distinction. The sole fact that a topic appears in a document presented by the company creates an expectation — and that expectation behaves like a promise: it gets cited at renewal, it serves as an argument in negotiation, it produces disappointment if nothing comes.

The effect depends neither on intent nor on careful wording. A topic kept in reserve, shown once in a sales meeting, has entered the customer's head as something coming. The level of commitment displayed beside it does not correct the effect; it only documents it, for the conversation where you will have to explain that no.

Showing is therefore an act, not a piece of information. What costs is not saying no: it is having shown.

Why it matters

It changes what goes into a customer-facing document: not what is true, but what you accept having to stand behind. An uncertain topic, however honestly labeled, gets removed rather than qualified.

It also gives a rule to sales teams: the question before showing a card is not "am I committing?" but "am I ready to talk about this again in six months?".

Nuances and limits

Caution has its cost. A customer who is shown nothing often concludes that the product is not evolving, and the absence of any outlook is as real a reason to leave as a broken promise.

And not all customers read the same way: a structured account, used to vendor roadmaps, knows how to read a level of commitment; a small customer rarely does.

Open questions

• How do you give a customer the outlook they need without giving them a named topic to wait for?