Main idea

A product exploration decision is almost always presented as a trade-off between acting — hence taking a risk — and waiting — hence taking none. The framing is false: waiting carries its own risk, that of arriving at a usage once it is established and customers' decision criteria have formed without the product.

The real choice therefore bears on the nature of the risk accepted, not on its presence. Exploring early exposes you to spending on a hypothesis that does not come true. Waiting exposes you to having to catch up on ground where others have already learned.

What some companies call caution is sometimes just another way of letting others do the learning in their place — and learning, for its part, cannot be caught up by building faster.

Why it matters

This shifts the burden of proof in committee. As long as waiting is treated as the neutral option, whoever proposes to explore has to demonstrate, and whoever proposes to wait has nothing to justify. Naming the risk of waiting restores the symmetry: both options call for an argument.

It also changes the nature of the trace left behind. A chosen risk is written down and can be reread; a risk suffered under cover of caution leaves nothing, and the organization cannot learn from its own decision.

Nuances and limits

Symmetry is not equivalence: in a stable market and on a marginal usage, the risk of arriving late is genuinely low, and waiting is then the right decision — for the right reason.

And the risk of exploring too early is not only financial: a premature exploration takes up the team's attention and installs in the product objects that will have to be removed.

Open questions

• How do you estimate the cost of a learning delay, when it only appears at the moment the catch-up is under way?