Skip to content
Floskool

Chapter 1 · The resource

The decision log

Free lesson 8 minGroup Flopilot

Follow this course in your space: your progress is saved, and the community answers your questions.

Follow for free

"Wait, what did we decide about the Pricing page?" Three people, three different memories. You have the debate again, sometimes reach the opposite decision, and a month later you discover the first one had a good reason that nobody wrote down. A decision log fixes this with a very simple tool: one note, one line per decision.

Why a separate log

Decisions are already somewhere: in meeting notes, an email, a comment. The problem is they're scattered and mixed in with everything else. The log pulls them together in one place, in order, for a given project. It answers three questions that keep coming up, in ten seconds:

  • What was decided?
  • Who decided it?
  • Why?

The "why" is the most valuable part. It's what keeps you from rehashing the debate, or lets you change your mind knowing exactly what you're changing.

One line per decision

Each entry fits in five fields:

  1. Date: the day the decision was made.
  2. Decision: one sentence, stated positively. "The site will launch without a Spanish version."
  3. Who decided: a name or a role ("the client," "the board"). Not "we."
  4. Why: the main reason, in one line.
  5. What it changes: the concrete consequence, and the task created if needed.

What deserves a line

Not everything. A decision belongs in the log if:

  • it changes the scope, timeline or budget of the project;
  • it was discussed (there were at least two options);
  • someone is likely to question it later;
  • it commits someone outside the team (client, supplier, partner).

The font on the "Contact" button doesn't belong there. Dropping the online store does.

Where to keep it

In the "02 Brief and exchanges" folder of your structure (lesson 1), or in a pinned project note if your tool allows it. What matters: one log per project, always in the same place, with new decisions added at the top so the most recent one is read first.

Get in the habit of filling it in at the end of every meeting, using the "Decisions" section of the meeting notes. And after a call where a decision was made, add the line right away.

The template to copy

DECISION LOG: [project name]
(most recent at the top)

[YYYY-MM-DD] | DECISION: [one sentence]
             | WHO: [name or role]
             | WHY: [main reason]
             | WHAT IT CHANGES: [consequence] / task: [task name]

[YYYY-MM-DD] | DECISION:
             | WHO:
             | WHY:
             | WHAT IT CHANGES:

If you prefer a spreadsheet, create five columns with the same headings: Date, Decision, Who, Why, What it changes.

Examples

Web agency, bakery website

2026-06-16 | DECISION: the Orders page is cut from the first version.
           | WHO: the client (Mr. Lenoir), on Sarah's suggestion
           | WHY: the shop's ordering system isn't ready yet.
           | WHAT IT CHANGES: launch stays on July 3 / task: remove the page from the menu

2026-06-02 | DECISION: no Spanish version at launch.
           | WHO: the client
           | WHY: customers are almost all local; revisit in six months.
           | WHAT IT CHANGES: nothing to translate for now

Photographer, wedding

2026-05-28 | DECISION: no photos during the ceremony.
           | WHO: the couple
           | WHY: the officiant's request.
           | WHAT IT CHANGES: brief the two second shooters / task: "To read" note for the team

Nonprofit

2026-06-10 | DECISION: the block party is on June 21, not June 14.
           | WHO: the board (vote, 4 out of 5)
           | WHY: all key volunteers are available on the 21st.
           | WHAT IT CHANGES: rent two tents / task: reserve the tents (Brian)

Contractor, kitchen remodel

2026-04-15 | DECISION: laminate countertop instead of quartz.
           | WHO: Mrs. Davis
           | WHY: quartz lead time is too long for the planned date.
           | WHAT IT CHANGES: new estimate to send / task: estimate v03

When Mrs. Davis asks three months from now why it isn't quartz, the answer is right there, dated, with her name on it.

Your turn

Start a new decision log for your current project. Go back through your meeting notes and emails from the past few weeks, and enter the three most important decisions already made, with their why. If you can't find the why for one of them, that's exactly why you should keep this log from now on.