Decision Log

What is a Decision Log?

A decision log is a shared, dated record of a team's significant choices, noting the decision, context, options weighed, rationale and owner. It keeps settled questions from being reopened and preserves the reasoning.

Updated November 2026 · 3 min read


A decision log is a running record of the significant decisions a team or project makes, capturing what was decided, why, by whom, when and which alternatives were considered. It gives everyone, including people who join later, a single place to see how the current plan came to be. Without one, teams relitigate settled questions, lose the reasoning behind choices and struggle to learn from decisions that turned out well or badly.

Decision logs are common in product management, program management, architecture and governance work. They are simple to set up, often a table in a shared document, wiki or work management tool, but they only help if entries are written at the time of the decision and kept current.

What to record in a decision log

FieldWhat to Write
ID and dateA unique reference and the date the decision was made
DecisionOne or two sentences stating what was decided, in plain language
ContextThe problem or question that prompted the decision and any constraints
Options consideredThe alternatives evaluated, including doing nothing
RationaleWhy this option was chosen, with the evidence or assumptions behind it
Decision-maker and contributorsWho made the call and who was consulted
ImpactWhat changes as a result: scope, timeline, cost, teams affected
StatusProposed, decided, superseded or reversed, with a link to any later decision
Review dateWhen to check whether the decision still holds, if relevant

Which decisions belong in the log

Not every choice needs an entry. Log decisions that are hard to reverse, affect several teams, involve significant cost or risk, settle a debate that took real time, or change scope, priorities or commitments. Routine choices that one person can easily undo, such as a button label, can stay out. A useful test is whether someone six months from now might ask, "Why did we do it this way?"

  • Architecture decision records (ADRs) are a specific form of decision log for software architecture, usually one short document per decision stored with the code. Michael Nygard popularized the format in a 2011 blog post.
  • Meeting minutes capture discussion. A decision log captures only outcomes and reasoning, so it is far easier to search.
  • A risk register tracks uncertainties that might happen. A decision log tracks choices that have been made, though decisions often respond to risks in the register.
  • A RAID log combines risks, assumptions, issues and decisions in one place, common in program management.

How to keep a useful decision log

  1. Agree on a template and location. Use the same fields and one shared place that everyone can find.
  2. Record decisions when they are made. Make logging the last step of any decision meeting, not a task for later.
  3. Assign an owner. A product operations lead, program manager or chief of staff keeps the log tidy and prompts others.
  4. Link it. Connect entries to the related roadmap items, tickets, documents and later decisions.
  5. Never delete entries. Mark reversed or superseded decisions and link to what replaced them, so the history stays intact.
  6. Review it. Revisit key decisions at their review dates or in retrospectives to learn from outcomes.

Decision log example

Consider a hypothetical product team building a mobile app that debates for three weeks whether to support offline mode in the first release. The team finally decides to defer it. The decision log entry records the decision, the context (two enterprise prospects asked for it, but usage data from the web app showed fewer than 5% of sessions started with a poor connection), the options (build now, defer, build a read-only cache), the rationale (building it would delay launch by six weeks) and a review date one quarter after launch.

Two months later, a new sales leader asks why offline mode is missing. Instead of reopening the debate, the product manager shares the entry. At the review date, the team checks the data again, sees that offline requests have grown among field-service customers and logs a new decision to build a read-only cache, linked to the original entry.

Common pitfalls

  • Logging after the fact. Reconstructed entries lose the options and reasoning that make the log valuable.
  • Recording only the outcome. "We chose vendor B" without the why is little better than no entry.
  • Too many trivial entries. A log full of minor choices buries the important ones.
  • Hiding it. A log only one person can find does not prevent repeated debates.

Decision logs work best alongside clear decision rights and frameworks such as the DACI decision making framework and the RACI matrix, which clarify who decides and who is consulted.

Frequently asked questions

What fields should each decision log entry have?

Each decision log entry should have an ID and date, a plain statement of the decision, the context that prompted it, the options considered including doing nothing, the rationale and evidence, who decided and who was consulted, the impact on scope, timeline or cost, a status such as decided or superseded, and an optional review date.

How do you decide what goes in a decision log?

Log decisions that are hard to reverse, affect several teams, carry significant cost or risk, settle a long debate, or change scope, priorities or commitments. Leave out routine choices one person can easily undo, such as a button label. A good test is whether someone six months from now might ask why the team did it this way.

What is the difference between a decision log and an architecture decision record?

An architecture decision record (ADR) is a specialized decision log for software architecture, usually one short document per decision stored alongside the code. A general decision log is a running table of a team's or project's significant choices of any kind, from scope and priorities to vendors and timelines. Michael Nygard popularized the ADR format in a 2011 blog post.