Campaign operations workshop / 5 MIN READ
Name the campaign failure before it becomes a deadline
Turn plausible delivery failures into prevention actions and clear response triggers.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
A premortem is useful when it reveals concrete ways the plan could fail and changes what the team does now. A dramatic list of worries without owners only adds anxiety.
What you will leave with: A short risk set with causes, early signals, prevention and contingency ownership.
Use this when
- A campaign depends on several external parties.
- A high-visibility launch leaves little room to recover from operational mistakes.
This is not a prediction of failure or a statistical risk model; it does not replace specialist safety assessment.
Describe a specific failed outcome
Atlassian’s premortem guidance asks teams to consider project problems and follow through on actions. Keep the imagined failure specific enough to reveal a mechanism.
Instead of “the launch was a disaster,” use a scenario such as the public event opened without a usable registration desk or the advertised service was unavailable in a promoted region. Ask participants to write possible causes independently before discussion. Include people who operate the process, not only those who approved the concept. Their practical knowledge often concerns dependencies that a campaign plan leaves implicit.
Separate causes from symptoms
For each scenario, ask what would have to go wrong and which existing control is supposed to prevent it. A complaint surge is a symptom; an unsupported eligibility promise may be the cause. Avoid assigning motives or blame to named colleagues. Focus on conditions the team can inspect or change.
Distinguish known issues from uncertain risks. A supplier that has already missed a mandatory acceptance step is not merely a hypothetical concern. Record the uncertainty honestly rather than using red, amber or green labels to conceal missing information. Where consequences involve safety, legal obligations or sensitive data, involve the appropriate specialist.
Choose prevention and a practical fallback
Write a prevention action that can happen before the risk materializes, such as verifying a regional fulfillment path or rehearsing a manual admission process. Name an owner who can actually do the work. “Be careful” and “monitor closely” are not prevention plans.
Then decide what happens if prevention fails. A fallback may involve reducing scope, delaying release or stopping a particular activity. Confirm whether the fallback requires approval or advance resources. Do not assume an emergency gives the team permission to make new commitments, share restricted data or ignore safety controls. Rehearse the consequential decision rather than only naming it.
Set signals and review the changed plan
Choose an observable signal that indicates action is needed, such as missing supplier confirmation at a specific review point. The signal should arrive early enough for the response to matter. Assign who checks it and who can decide the next step.
Close the session by changing the project plan, not by filing the risk document. Review open risks when a dependency changes or a decision approaches. Retire resolved items with a brief explanation and keep unresolved ones visible. A useful premortem makes the team’s plan more realistic without requiring them to imagine every possible catastrophe.
Make the reasoning concrete.
A fictional industry campaign includes an invitation-only demonstration at a partner venue. The plan assumes the venue will provide staff to check attendees, but nobody has confirmed that responsibility.
Leave it as a general event risk
Opening: Record “entry delays” in the risk list.
Hypothesis: The concern has been acknowledged.
Risk: No one has changed the assumption that creates it.
Assign a prevention action
Opening: Confirm staffing and rehearse the admission route with a named fallback owner.
Hypothesis: The team can resolve the actual dependency before guests arrive.
Risk: If staffing cannot be secured, the event format may need to change.
The campaign lead obtains a clear staffing decision and prepares an approved manual admission plan. The risk closes only after the operational owner verifies the arrangement, not when the task is merely assigned.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Failure
What specific outcome would make this campaign fail operationally?
Cause
Which assumption or dependency could produce it?
Prevention
What action can reduce the risk before launch?
Signal
What observable event triggers intervention?
Fallback
Who can authorize and carry out the response?
Watch for the wrong conclusion.
- Writing vague disasters without causal detail.
- Treating an already-occurring issue as a hypothetical risk.
- Assigning a fallback that nobody has authority or resources to execute.
Your next action
Choose one critical campaign assumption and write the failure, early signal and prevention owner in three concrete sentences.
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: Pre-mortem →Primary framework-publisher guidance · Supports: A premortem identifies potential project problems and follows through on mitigation actions; the campaign risk cards are original analysis.