Main idea

A few weeks after a decision, everyone remembers what suits them. The reasons get simplified, the constraints that weighed at the moment of choice disappear from the story, the frustrations stay intact. Collective memory keeps neither the comparison of options nor the grounds for the refusal: it keeps the outcome and the discontent.

At that stage, reopening the debate takes no bad faith. Nobody can produce what had been weighed, since nobody kept it. A decision then becomes indistinguishable from an old preference, and the discussion starts from scratch on a subject already settled — or, worse, each party executes its own interpretation of what had been decided.

What a decision log sets against that erosion is not archiving. It is a precise, short content: the decision made, its reason, the options set aside, what was agreed to be sacrificed, who made the call. A log that keeps the decision without keeping the loss protects nothing, because the loss is exactly the part collective memory erases first.

Why it matters

This gives a non-bureaucratic reason to trace arbitrations: it is not about accountability, it is about preventing a choice from being paid for several times.

It also indicates what has to be written first when time is short: the options set aside and the sacrifice accepted, before even the detail of the decision retained.

Nuances and limits

A record protects only what it contains. A log kept as minutes — "decision: launch in March" — lets the erosion work on everything else.

And written memory can serve the wrong cause: holding a two-year-old arbitration against a team that has new information confuses standing by a decision with stubbornness.

Open questions

• What volume of records can an organization keep on its arbitrations before the log stops being reread?