Building a Decision Log So You Stop Re-Debating the Same Marketing Choice Every Quarter

Six months from now, someone's going to ask "wait, why don't we run Facebook ads?" as if it's never come up before. 💖 It has come up before. You decided. You had good reasons. Those reasons are currently stored in nobody's memory in a form anyone can access, which means the debate restarts from scratch — and this time, without the context that made the first decision a good one.

What most businesses get wrong

• Decisions live only in someone's memory. When that person forgets the details, or leaves, the reasoning leaves with them.
• There's a record that a decision happened, but not why. "We decided not to" without the reasoning is almost useless six months later.
• New hires or partners relitigate settled choices because they genuinely don't know a decision — with real thought behind it — was ever made.
• Every "let's revisit this" conversation starts from zero instead of starting from what was already tried or considered.
• "We haven't revisited it" gets confused with "we never actually decided." Those are very different situations that deserve different conversations.

The one-page log that ends this

How to actually run this day to day

Log the decision within a day of making it, while the reasoning is still fresh and specific — not a vague summary written from memory three weeks later. Write the revisit trigger as something checkable: a number, a date, an event. "If it feels like it's not working" isn't a trigger; "if enquiry volume drops below 15 a month for two consecutive months" is. When a decision gets questioned again, the very first move — before any new discussion — is pulling up the log and checking whether that trigger condition has actually happened.

Mistakes to avoid

• Don't write entries so vague they're meaningless later — "decided to focus on socials" tells future-you nothing about why or what else was considered.
• Don't let the log exist and then never actually check it before a meeting — a log nobody opens provides zero protection against relitigating.
• Don't let it balloon into hundreds of untouched entries — archive anything genuinely outdated so the active log stays usable.
• Don't use the log as a blunt instrument to shut down every new idea — it's a reference point, not a permanent veto on reconsidering anything, ever.
• Don't make the log only the owner's job to fill in — anyone involved in a decision should be able to add to it.

Frequently asked questions

What if the market has genuinely changed since the decision was made?

Then it's worth revisiting — and that's fine. The log's job isn't to lock a decision in forever, it's to make sure a re-debate starts from the real original reasoning and actually checks whether the revisit trigger condition has happened, rather than restarting from nothing because someone forgot a decision was ever made at all.

Who should actually own keeping the log updated?

Whoever is in the room when the decision gets made logs it, within a day or two. It shouldn't default to one person chasing everyone else for details after the fact — that's how logs stop getting updated within a month.

What tool should we use for this?

The simplest shared document your team already opens regularly. A spreadsheet or a shared doc works fine — the format matters far less than whether people actually look at it before a decision gets reopened.

Isn't this just extra admin on top of everything else?

It's ten minutes per decision, which is considerably less than the hours lost to re-arguing the same choice every few months with less context than you had the first time. The admin cost is real but small compared to what it replaces.

Keep reading 🤍

• In-House vs Outsourced Marketing: A Decision Framework for Any Small Business
• The 'One Thing' Rule: Why Fixing Five Marketing Problems at Once Fails
• When to 'Fire' a Client: A Decision Framework for Unprofitable or Toxic Relationships