Main idea

From the standpoint of whoever did not get their way, two very different situations look exactly alike: their argument was heard and then set aside for a reason, or it never weighed in the discussion at all. In both cases the outcome is the same and the minutes say nothing more.

Recording the options set aside and the grounds for rejecting them lifts that ambiguity. The support team that asked for a fix before launch, the sales team that defended an abandoned segment, the finance team that warned about margin can read what was weighed against their position. They are not convinced for all that; they know their objection existed at the moment of choice.

What this produces is not comfort. It is the condition for a decision to be executed by those it disadvantages: an organization where you cannot tell the set-aside from the ignored teaches its minority functions that speaking up is pointless, and prepares them to reopen the subject as soon as an occasion arises.

Why it matters

This gives a reason to trace rejected options that has nothing to do with documentary rigour or compliance, and everything to do with decisions holding over time.

It also qualifies the idea that an arbitration is judged by its sharpness: a sharp decision that says nothing about what it rejects remains, for the losers, indistinguishable from being steamrollered.

Nuances and limits

A record does not replace listening. Writing "option set aside: cost too high" without the function concerned having been able to lay out its reasoning produces the form of recognition without the thing.

And the exercise has a political limit: explicitly naming what each function lost can harden positions in an organization where arbitrations are experienced as defeats for a camp.

Open questions

• To what level of detail can the grounds for a rejection be written without turning the minutes into a case against a function?