Why decision records beat meeting minutes
A meeting preserves the conversation. A decision record preserves the conditions for action.
The missing object
A meeting can end with agreement while leaving the decision undefined. Who had the authority to decide? What alternatives were considered? What trade-off was accepted? Minutes often preserve who spoke; teams also need a usable record of what now changes.
Record the decision, not only the discussion
A useful record states the question, the chosen option, the owner, the rationale and the evidence available at the time. Add dependencies, a review date and the conditions under which the decision should be reconsidered. The record need not be long; it needs to be explicit.
What would count as a result?
A decision becomes testable when the team can describe the behavior or outcome it expects to observe. Closing an action proves completion, not the expected effect. Connect the record to delivery, acceptance and re-observation before attributing improvement.
A question for the next review
Choose one recent decision. Can another team member reconstruct why it was made, who owns it and when its result will be checked? If not, the institution has retained a conversation but lost part of its operating memory.
A decision that can survive a handover
Consider a recurring service delay. “Improve coordination” leaves the next shift with an aspiration. A usable record says which team accepts the request, what information is required, when ownership transfers, and who resolves an exception. It also names the alternative rejected and why. This makes the organisation’s intended behaviour inspectable at the point where a person experiences it. The record connects institutional intent to a specific operating rule; it cannot establish that the rule is followed.
Build a review around exceptions
At the review date, sample requests that completed normally and requests that failed. Compare the recorded rule with what actually happened. Separate missing information, unavailable capacity, ambiguous authority and deliberate overrides; they call for different interventions. Track reopened requests and time waiting for a decision alongside completion time. A faster average with more unresolved exceptions may hide deterioration. Keep the original decision and append revisions so that a later reviewer can reconstruct what the team knew at each point.
A decision record to use in the next review
| Record | Question or field |
|---|---|
| Question and authority | What must be decided, and who may decide it? |
| Choice and evidence | Chosen option, rejected alternative, source and uncertainty. |
| Execution and review | Owner, dependencies, review date and reconsideration trigger. |
Free templates: record the decision and observe the friction