Decision Log

In a fast move you’ll make dozens of calls — which furniture, whose budget, what opens day one. Write them down. A decision log is the difference between “we decided that weeks ago” and a circular conversation you’ve now had three times.

What it’s for

To keep settled questions settled. When someone asks “wait, why are we doing it this way?”, the log answers in one line — with who decided and the reasoning — instead of reopening it. It also protects you: a written decision is a shared decision, not something that quietly becomes your fault later.

How to use it

1. Log a decision the moment it’s made — in the standup, on a call, in a thread.
2. Capture the why, not just the what. The reasoning is what stops the re-debate.
3. When a “Decision needed” item in your Open-Item Tracker gets resolved, move it here.
4. Surface big ones in your Weekly Status Update.

The structure

Date	Decision	Made by	Why / context	Affects	Revisit?
Jun 4	Open with 6 of 8 conference rooms; finish 2 post-opening	Workplace lead + Ops	AV for 2 rooms slips past opening; not opening-critical	IT/AV, Comms	No
Jun 5	Reuse existing desks, buy new chairs only	Finance	Budget; desks are fine, chairs aren’t	FF&E, Finance	No
Jun 6	Approve rush fee to pull internet install forward	Founder	Connectivity is opening-critical	IT/AV	No

Tips

• The “why” column earns its keep. Months later, context is the thing nobody remembers.
• Reversible vs. not. Note decisions that are expensive to undo — those deserve a second look before they’re locked.
• Don’t bury it. A log nobody reads isn’t a log; keep it in the command center.

See the full workstream: Project Control.