Decision Records

A generalist can use completed decision records across domains to demonstrate breadth of impact. A one-page decision record creates a stable artifact that later functions as evidence of judgment. The log should record important decisions and the reasons behind them. The recommended decision record includes context, options, decision, impact, owner, and review date. A one-page decision should document context, considered options, the decision, owner, metric, expected impact, and review date. A useful decision entry should include the decision, the reason for it, and the surrounding context without exposing confidential details. Decision records should stay lightweight enough to circulate without becoming a heavy process. Decision context fades over time, including constraints, tradeoffs, risks, conversations, and business pressures. The written decision artifact records what was decided and why it was decided. Written decision records can help explain why a path was reasonable during reviews, architecture discussions, incident reviews, or interviews. The decision artifact clarifies ownership, measurement, expected impact, and review timing.