Most teams can find the current landing page, campaign or price. Far fewer can explain why it looks that way, what it replaced and whether the change worked. A marketing decision log closes that gap.
The aim is not to document every edit. It is to preserve the decisions that a future teammate would otherwise have to reconstruct from analytics, chat, tasks and memory.
A marketing decision log is a chronological record of meaningful marketing changes, the reasoning behind them, the evidence used to judge them and the action that followed.
What belongs in a marketing decision log?
Record a change when it carries a hypothesis, trade-off or commitment. A corrected typo is activity; a new value proposition, offer, audience, price or campaign structure is a decision.
- The location: page, campaign, email, ad, offer or journey step.
- The before and after state in language a teammate can compare.
- The reason for the change and the expected outcome.
- The owner, change date, success measure and review date.
- The result, evidence type, conclusion and next action when known.
A useful test: if reversing the change would require a discussion, the change probably deserves a record.
Why a task list or analytics dashboard is not enough
A task manager tells you that work was delivered. Analytics tells you what happened across an audience. Neither reliably preserves the exact decision that connects the work to the result.
The decision log sits between those systems. It does not replace them. It links the asset, rationale, measurement window and conclusion so someone can evaluate the learning later.
A lightweight operating rhythm
The log only compounds when it stays easier than rediscovering the context. Use a short creation step and a separate review step.
- CaptureRecord the before, after and one-sentence reason while the change is fresh.
- ScheduleName the signal and date that will make the change ready to review.
- EvaluateAdd the result and label how strong the evidence really is.
- ConcludeWrite keep, revert, iterate or no action—and explain why.
- ConsultSearch the log before approving a similar change.
What good looks like
A good entry remains understandable to someone who was not in the meeting. It separates observation from causality, names the comparison period and records an inconclusive result without embarrassment.
A weak entry says “new homepage copy—performed better.” A strong entry identifies the old and new promise, why the team expected qualified enquiries to improve, which dates were compared, what else changed and what decision the team made.
Start with the next real decision
Do not begin with a six-month archaeology project. Capture the next meaningful change, then add older decisions only when they become relevant. The first useful record should take less than a minute; completeness can grow with use.
Clear answers
Frequently asked questions
Is a marketing decision log the same as an experiment backlog?
No. A backlog contains ideas that may happen. A decision log records changes that were actually made and follows them through to evidence and a conclusion.
Should failed changes stay in the log?
Yes. A documented negative or inconclusive result can prevent more wasted work than a successful change. Keep the conditions and evidence visible so the team knows when the lesson applies.
How detailed should each entry be?
Detailed enough for a teammate to understand the change, intent, result and next action without reopening the original chat or task. For most changes, concise structured fields are more useful than a long report.
Make this part of the next decision.
Diffined keeps the change, reason, evidence and conclusion together in one private history.
Try the working prototype ↗