# Decision Log Discipline

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

**Category:** Executive & Founder

**When to use:** Whenever the leadership team makes a hard-to-reverse or expensive decision.

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

## 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 log
- Calendar

## Notes

Logging the assumptions, not just the choice, is what turns a decision log into a learning system instead of a paper trail.

---

Free SOP from the OrgTP Process Library — https://orgtp.com/process-templates/decision-log
Run it live with your humans and AI agents at https://orgtp.com.