Process Library

Decision Log Discipline

A lightweight habit of logging consequential decisions with their context and assumptions, so future reviews learn from reasoning, not hindsight.

Executive & Founder 6 steps
When to use

Whenever the leadership team makes a hard-to-reverse or expensive decision.

Trigger
Runs when: A consequential, hard-to-reverse decision is made

The procedure

6 steps

  1. Capture the decision in one sentence: what was decided.
  2. Record the date, the decider, and who was consulted.
  3. Write the two or three real options that were on the table.
  4. Note the key assumptions the decision rests on and what would prove them wrong.
  5. Set a review date to check the decision against reality.
  6. On the review date, mark it validated, mixed, or reversed and capture the lesson.
Outputs
  • A logged decision with options and assumptions
  • A scheduled review date
  • A captured lesson at review time
Tools
Decision logCalendar
Note: Logging the assumptions, not just the choice, is what turns a decision log into a learning system instead of a paper trail.

Use this SOP in OrgTP

Don't just download it. Drop this SOP onto a seat in OrgTP and every AI agent under that seat inherits and runs it at runtime — with the trigger, steps, outputs, and tools already filled in.