How to Keep a Decision Log Without Writing One

Every team that's been burned by "wait, who decided that?" tries a decision log.

It's a good idea. A single place that says what was decided, when, by whom, and why. The next time a client says "we never agreed to that," you open the log and point. The next time a new hire asks why the API is shaped that way, the answer is there.

Most decision logs last about a month.

Why decision logs die

The problem isn't discipline. It's that a decision log is a copy.

The decision itself happens in a meeting, a Slack thread, a call with the client, a reply-all. It's made out loud, by people who then go do the thing. The log is a second place where someone has to write down what just happened — after it happened, by hand, in a format that's different from how it was said.

That step is where it dies. Three reasons:

Nobody owns the writing. The person who made the decision assumes the PM will log it. The PM was in a different meeting. The note-taker wrote "push launch to the 14th" but didn't know it was a decision and not a suggestion.

The decision looks obvious at the time. Everyone in the room knows the launch moved. Writing it down feels like recording that the sun rose. Three weeks later, with two people gone and a client asking, it isn't obvious at all.

The log is a different tool. A Notion page, a Confluence doc, a column in a spreadsheet. Nobody has it open when the decision is made. By the time they do, the moment's passed.

A 2020 survey found more than a third of organisations spend over 24 hours a month collecting project status (Wudpecker). A good share of that is reconstructing decisions that were made and never recorded.

What a decision log is actually for

Worth being honest about this. Teams say decision logs are for institutional memory, onboarding, and alignment. Sometimes they are. Mostly they're for one moment: when someone senior asks what happened and you need to show them rather than tell them.

A project manager on Reddit described that moment exactly — a project six months late because a board member pushed through a scope change, and the PM couldn't say so without it becoming a fight. The advice was to build a chronology with evidence, because "the person who rammed their agenda through can't dispute the facts when you can show where and how they got their change through."

That's the real job. A decision log is cover. It lets the evidence do the accusing so a person doesn't have to. And that's precisely why a hand-written log fails when it matters: the entry that would have protected you is the one nobody wrote, because the person who should have written it was the one being overruled.

The log that writes itself

If the decision was said out loud somewhere, the record already exists. It's in the transcript, the thread, the email. The log failed because someone had to copy it. So don't copy it — read it.

That's what Fluorine does with a project board. Its engine, Flo, reads the places a team already works — Slack, Zoom and Google Meet transcripts, GitHub, Notion, forwarded email — and when something said there disagrees with what the board shows, it proposes the change and quotes the sentence. You confirm or reject.

Every confirmed change goes into Drift: what changed, when, who said the thing that caused it, and who confirmed it. Click a due date on the board and you get the moment on the call where it moved. Click a status and you get the Slack message that said it was done.

Nobody writes an entry. The entry is the evidence.

Flo never changes the board on its own, never writes to any connected tool, and never records a call — it reads the transcript your meeting tool already produces. Here's exactly what it reads and never does.

What this changes in practice

"Who decided that?" has a one-click answer. Not a reconstruction from memory, not a search through Slack. The date on the board links to the sentence that moved it.

The record exists for the decisions you'd never have logged. The small ones — a date slipping a day, a task quietly reassigned — that turn out to matter later. A hand-written log only captures what someone thought was important at the time.

The evidence is neutral. When the record shows that legal changed the copy on Tuesday's call, that's not you accusing legal. It's the call.

Nobody's job is "keep the log." The meeting is the log. The board hears it.

Try it on one project

Connect the Slack channel and the meeting recording for one project. Run two weeks as you normally would. Then open Drift and read what it recorded.

If it caught decisions you'd have lost, that's the case. If the board never disagreed with anything said — it happens — you have a well-run project and a week of evidence that says so.

Fluorine is free for 14 days, card required, nothing charged until day 15. Try it.

FAQs

Is this a replacement for a decision log or an addition to it? A replacement for the part that failed — the manual entry. If your team keeps a doc of architectural decisions with reasoning, keep it. What Fluorine records is the board-level decisions: status, dates, ownership, priority — the ones that were said out loud and never written down.

What if the decision was made in a tool Flo doesn't read? Then it isn't in the record, and Flo won't claim otherwise. Flo reads Slack, Zoom, Google Meet, GitHub, Notion, notes written in Fluorine, and email you forward to it. A decision made in a hallway is still a hallway decision.

Can I export the record? The summary view produces a plain-text account of what changed over any date range, ready to paste into an email or a doc. A full data export is on the roadmap.

Who can see the record? Workspace members. Owners and admins see every change; members see the ones on tasks assigned to them. Nobody outside the workspace sees anything in it.

References

Wudpecker. (2024). 15 Project Management Trends in 2024. https://www.wudpecker.io/blog/15-project-management-trends-in-2024