Campaign operations workshop / 5 MIN READ
Keep the reason for the campaign decision
Record enough context that the next person can understand why a choice was made.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
A decision record is not meeting minutes. It preserves the choice, rationale, assumptions and conditions for reconsideration so teams do not repeatedly reopen settled questions or inherit unexplained constraints.
What you will leave with: A compact decision record linked to the work it governs.
Use this when
- A project changes owners midway through delivery.
- Teams revisit the same choice because nobody remembers its basis.
This is not a permanent defense of an old decision or a substitute for the actual approval required to act.
Record the decision, not the whole discussion
Atlassian’s DACI guidance connects a decision to its driver and approver. Keep those responsibilities visible in the record without reproducing every message that led to the choice.
Write the question, chosen option, decision date and authorized decision-maker. State the scope so the record is not applied to a different audience or release. “Use the simpler venue format for this regional pilot” is more useful than “simpler is better.” Link to the relevant approved plan and evidence, keeping confidential material in its proper location rather than copying it into a broad log.
Preserve the decisive trade-off
Explain the few considerations that actually changed the choice. These may include an operational constraint, an audience need or an unresolved risk. Distinguish observed facts from planning assumptions. A reader should understand why the chosen option was reasonable under the conditions known at the time.
Mention serious alternatives and why they were not selected, but avoid a transcript of every idea. Keep the language professional and focused on the work. Do not record speculative personal motives or use the log to assign blame. A concise honest rationale is more useful than a polished story that pretends uncertainty never existed.
Define when reconsideration is justified
Write the conditions that could reopen the decision, such as a changed product capability, a confirmed venue restriction or evidence that an assumption was wrong. Separate those triggers from a new stakeholder’s preference to restart the discussion.
A record should make course correction easier when the facts change. Do not treat prior approval as proof that a harmful or misleading action should continue. If the decision is superseded, link the replacement and explain the material change. Preserve the historical record where appropriate, but clearly mark which choice currently governs execution.
Use the record at handoffs and review points
Include relevant records when a new owner, supplier or reviewer joins. Ask them to flag missing context rather than making them reconstruct a long chat history. Before reopening a familiar question, inspect whether the facts or decision scope have actually changed.
Keep the system lightweight. Store one record per consequential choice, not every routine edit. Link it from the task that depends on it and assign an owner to update its status. The purpose is continuity of reasoning. If nobody can find the record at the moment of action, its completeness has little practical value.
Make the reasoning concrete.
A fictional campaign selects a smaller live demonstration because the available product setup cannot safely support the original audience size. A new lead later asks why the event was not made bigger.
Reopen the idea from scratch
Opening: Restart the format debate without checking the prior constraint.
Hypothesis: The new lead can reconsider the creative opportunity.
Risk: The team may repeat work while the same delivery limitation remains.
Inspect the decision record
Opening: Review the capacity condition and ask whether it has materially changed.
Hypothesis: The discussion can focus on new facts rather than lost context.
Risk: The smaller format may remain the appropriate choice.
The record identifies the equipment configuration that constrained the event. The new lead checks that fact with the operational owner and retains the format until a verified alternative exists.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Choice
What question was decided, for which scope?
Authority
Who made the decision and under what responsibility?
Rationale
Which facts and trade-offs were decisive?
Trigger
What new condition would justify reconsidering it?
Current status
Is this record active, superseded or no longer relevant?
Watch for the wrong conclusion.
- Saving long minutes without identifying the actual decision.
- Rewriting the rationale to hide uncertainty.
- Using an old decision as a reason to ignore new material evidence.
Your next action
Capture one consequential choice from the current campaign in five lines: question, decision, reason, assumption and reconsideration trigger.
Sources & scope
The workflow, worksheets and hypothetical examples are original editorial analysis. Sources support only the identified principles. No measured business results or named human reviewer are claimed.
- Atlassian Team Playbook: DACI →Primary framework-publisher guidance · Supports: DACI distinguishes the decision driver, approver, contributors and informed people; the campaign application is original editorial analysis.