Main idea

People often set the firmness of a decision against its revisability, as if you had to choose between holding a line and staying able to learn. The opposition disappears as soon as a third element is recorded with the decision: under what conditions it should be reopened.

Writing those conditions at the moment of choice — a usage threshold not reached, a contrary market signal, a feasibility assumption disproved, a deadline passed — changes the nature of what can restart the debate. Reopening stops being obtained and becomes triggered. It no longer depends on insistence, political weight or turnover among the participants, but on a fact anyone can observe.

Without that clause, the organization has only two regimes, equally bad. Either the decision is treated as final and becomes wrong as soon as the context moves. Or any frustration is enough to restart the discussion, and the choice never existed for the teams executing it.

Why it matters

This turns a question of character — holding firm or giving in — into a question of drafting, hence into something a team can install without changing its culture.

It also answers those who refuse to decide on the grounds that the information is incomplete: the decision is made, and what would call it into question is named.

Nuances and limits

Written conditions do not cover the unforeseen. A change nobody had in mind at the moment of choice will appear in no clause, and refusing to take it into account in the name of the rule is the same stubbornness in a cleaner form.

And a condition that is too loose does the opposite of what is expected of it: "if field feedback is bad" reopens the decision at will, under cover of procedure.

Open questions

• How do you formulate a reopening condition precise enough to be observable, without freezing in advance what the organization will be allowed to learn?