[[Impact mapping]]-like [[Decision making|decision making]]: > A framework for capturing decisions in a way that preserves context — not just _what_ was decided, but _why_ it mattered and _what_ it changed. Most decision logs fail because they record outcomes without business context. This framework forces the connection between a decision and the problem it solves - making it useful not just as an archive, but as a living reference for future decisions. - **WHY** decision is made (business [[Problem|problem]] statement with context) - **WHO** decision maker - **WHEN** decision was made - **HOW** decision is made with justification - ***WITH*** options considered - **WHAT** [[Outcome|outcomes]] (good or bad) decision brings ^parts Particularly useful when: - onboarding new team members who need to understand _why_ things are the way they are - evaluating whether a past decision still holds given new context - avoiding rebuilding the wheel — similar problems often have reusable solutions When applied at scale across an organization, decision logs form a **knowledge graph of business problems and solutions** — queryable with AI, reusable across teams, and resilient to people rotation.