The meeting ends with a familiar sentence: “Great, we're aligned.” A week later, someone asks what was decided. Another person remembers a different answer. The team spends its next meeting reconstructing a conversation it already had.
More detailed minutes may help, but the missing piece is often smaller: a clear record of the decision itself.
Separate the discussion from the decision.
Meeting notes explain what people discussed. A decision record states what the team will now do. It should be short enough that the owner can read it without reopening a recording or scrolling through several pages.
For a small team, five fields are enough to begin:
- Decision: what was approved, declined or deferred?
- Reason: which constraint or evidence drove the choice?
- Owner: who can move it forward or resolve an exception?
- Next step and date: what happens now, and by when?
- Revisit condition: what new information would justify changing the decision?
Make reopening a decision deliberate.
Imagine a team choosing a date for a program launch. The decision is not just “launch next month.” It records who approved the date, which capacity constraint was considered, who briefs participants, and what would trigger a change.
A new staffing constraint may justify revisiting it. Someone missing the original conversation does not automatically require the entire team to decide again. The record gives them a place to catch up and raise a specific concern.
Start with one recurring meeting.
Do not build another large system before you know whether it helps. Add a decision section to one weekly meeting. At the end, read the decisions back, confirm owners and dates, and put the record where the team already works.
At the next meeting, review exceptions and overdue next steps. Keep routine updates out of that discussion when people can read them beforehand.
Measure the friction you want to remove.
Count decisions reopened without new evidence and next steps with no owner. Establish the baseline before setting a target. A smaller number can be useful, but ask why it changed: fewer recorded decisions is not the same as clearer decisions.
The goal is a team that can move work forward with a shared memory of what it agreed to do.
The launch example is illustrative. This note offers a practical starting point, not a claim of measured client results.