On Monday everyone agrees to use the simpler launch plan. By Thursday, two teams are working from different interpretations of “simpler.” The meeting notes contain a long discussion, but no sentence that says exactly what changed.
A decision record solves a narrow problem: it makes a choice understandable after the conversation has ended. It is most useful when people outside the meeting need to act on the outcome or when the team may need to revisit the reasoning later.
Write the decision before the discussion history
Start with the question and the choice. In an invented project example: “For the pilot, we will offer two appointment slots per day rather than four.” Follow that with the date, the person authorised to decide and the person responsible for carrying out the next action.
Keep the background short. A record that opens with every comment from a forty-minute meeting makes readers search for the part they actually need. Link to supporting material when it is useful, but do not hide the decision inside an attachment title.
Separate participation from authority
A team can hear many views without leaving final authority ambiguous. Atlassian’s DACI play distinguishes the person driving a decision, the approver, contributors and people who need to be informed. The terminology is optional; the distinction is valuable.
Before using any framework, check your organisation’s actual approval rules. A workshop cannot give someone spending or legal authority they do not have. For an ordinary team decision, a small role note is often enough to prevent “I thought you were approving it.”
Record the trade-off without rewriting the debate
Use two or three sentences to explain the main reason for the choice and the disadvantage the team knowingly accepted. In the pilot example, fewer slots might make staffing easier while limiting the number of participants. Those are illustrative assumptions, not measured results.
Identify uncertain inputs explicitly. If the plan depends on a supplier date that has not been confirmed, record that condition. A later reader should be able to distinguish a fact available at the time from a working assumption that still needed checking.
Give the decision a useful review trigger
“Review later” is easy to forget. State the event or date that would justify reopening the choice, along with who will bring the relevant information. For example, a pilot review might happen after the first complete week of bookings, once the team has comparable records.
A review trigger is not a reason to restart the debate every morning. If new information does not affect the recorded assumptions or the decision’s scope, capture it for the planned review rather than quietly changing direction.
Put the record where the work happens
Share a link with affected colleagues and connect it to the task list. Ask one person who missed the meeting to explain the decision back to you. If they cannot identify what to do differently, the wording needs another pass.
When a decision changes, preserve the earlier record and mark it as superseded. A clear trail helps a team understand its choices without confusing an old plan with the current one.
When the next action belongs to a colleague, a clear delegation handover helps turn that decision into work.