“We already decided that” is not very helpful when nobody remembers what was decided or why. A decision log gives a group a stable account: the choice, its date, who had authority to make it, and the reasoning needed to understand it.
Such records can sit within a wider organizational logbook. Their purpose is different from recording every sentence of a meeting. They preserve the commitments that other people need to act on.
Remembering without becoming stuck
Imagine a community venue deciding not to open on Sundays because it lacks volunteer coverage. A short record prevents newcomers from interpreting the closure as an unchangeable principle. When more volunteers arrive, the reason for the old decision supplies a clear basis for reconsideration. A review date can give that reconsideration a place on the calendar.
The log is particularly valuable for people who were absent. They can distinguish an idea someone mentioned from an adopted agreement. Recording when a decision replaces an earlier one prevents two contradictory instructions from remaining equally plausible.
Writing can also conceal disagreement. A tidy summary should not erase a material uncertainty or imply unanimous support where none existed. Nor should a public log expose private information simply to demonstrate transparency. The useful record is brief enough to maintain and rich enough to explain what the group is committed to, under which assumptions, and until what changes.
Real cases
- GitLab: written context with one accountable decision-maker — How can a distributed team combine wide input with clear decisions?
- Loomio: different rooms have different decision rights — What must an online discussion space specify before its decisions mean anything?