How to Keep a Decision Log Your Team Will Actually Use
Six months into a project, someone asks why you chose the more expensive vendor, or why the scope changed in March. If the answer lives only in a closed Slack thread and one person's memory, you have a problem. A decision log fixes this — a simple, durable record of the choices that shaped the project. With teams scattered across home offices in 2021, the hallway conversation that used to carry this knowledge has disappeared, which makes writing it down more important than ever.
What belongs in the log
A decision log is not meeting minutes and not a risk register. It captures decisions of consequence: the ones that, if reversed, would cost time, money, or trust. Keep the entry short but complete. Each row should answer five questions a newcomer would ask.
What was decided, stated as a clear outcome rather than a discussion.
Why — the rationale and the main options that were rejected.
Who decided, and under what authority (the decision-maker, not just who was in the room).
When it was decided, and when it takes effect.
What it depends on or affects, so the link to scope, budget, or schedule is visible.
Setting it up
Pick one home for it. A single shared table — a spreadsheet, a wiki page, or a tool your team already opens daily. If people have to go looking, they will not use it. One source of truth beats three scattered ones.
Give every decision an ID. A sequential number (D-001, D-002) lets you reference a decision in emails, change requests, and other documents without re-explaining it.
Name a single owner. One person — usually the project manager — is responsible for logging decisions promptly. Shared responsibility for the log means no responsibility.
Log it within a day. Capture the decision while the reasoning is fresh. A decision recorded a week later loses the rejected options and the nuance that made it defensible.
Record the status, not just the decision. Mark whether a decision is proposed, approved, or superseded. When you later change course, supersede the old entry rather than deleting it — the history is the point.
Making it stick
The log only earns its keep if it is used. Open it at the top of status meetings to confirm recent decisions are captured. Reference decision IDs in change requests and approvals so the log becomes load-bearing rather than decorative. And resist the urge to log everything — a log full of trivial choices buries the consequential ones, and people stop reading it. Aim for the decisions a future auditor, a new team member, or a frustrated stakeholder would want to understand.
Done well, the log pays off at exactly the moments that hurt most: a dispute over scope, a staff change, a funder's audit, or a quiet 'wait, why did we do that?' eighteen months on. The answer is one row away, written when memories were sharp and motives were clean.
If you want a decision discipline that holds up under audit and survives staff turnover, XNM's program & project delivery advisory can help you build it into how your projects run.