How to Run a Pre‑Mortem That Catches Campaign Risks Before Launch

The single biggest mistake I see SMB owners make in pre‑mortems is treating them as a box‑ticking exercise instead of a real risk‑hunt.

How do you run a pre‑mortem before a campaign?

Answer: You run a pre‑mortem by gathering the core team, declaring that the launch has failed, and asking each person to write down the reasons why.

Start by inviting the people who will own the launch — product, marketing, sales, and support leads. State clearly that the effort has failed, then give everyone five minutes to silently list every possible cause. Collect the lists, group similar items, and turn each cluster into a concrete failure scenario. For each scenario ask what early signal would have shown the problem and who could act on it. Capture those signals and owners in a simple table.

What does a successful pre‑mortem deliver?

Answer: A successful pre‑mortem delivers a concise list of plausible failure causes, each paired with a clear owner and a concrete mitigation step.

The output is not a lengthy risk register; it is a focused set of items that the team can act on immediately. Each item includes a short description of the failure mode, the name of the mitigation owner, and a single‑sentence action that reduces the chance or impact of that failure. Because the owners are named, the follow‑up becomes a routine check‑in rather than a separate meeting. This turns abstract worry into concrete, trackable work.

Manager scan (quick digest example)

• Review the pre‑mortem table each morning
• Ask each mitigation owner: “Are you on track, stuck, or need help?”
• Note any new signals that were not in the original list
• Update the gap column if reality diverges from plan
• Keep the conversation under two minutes per owner
• Use the scan to surface emerging risks before they become incidents
• Turn the scan into a standing item in your daily stand‑up
• Let the owner see the Plan → Fact → Gap trend at a glance

Tool tip (AiAdvisoryBoard.me): In a pre‑mortem, treat each imagined failure as a fact that you compare against your original plan. The gap between the two shows where visibility is missing. Capture that gap in a simple table: column one – what you planned to happen, column two – what the failure scenario says actually happened, column three – the gap that points to a blocker or a missing metric. Reviewing this table every morning gives the owner a quick Plan → Fact → Gut check without waiting for a full report.

Tool tip (AiAdvisoryBoard.me): Use the mitigation owners list from your pre‑mortem as the basis for a daily “owner scan”. Each morning, the owner checks in with those owners for a one‑sentence update: are they on track, stuck, or needing help? This turns the pre‑mortem into a living risk radar that surfaces emerging gaps before they become incidents. Over time, the scan builds a habit of proactive ownership and keeps the Plan → Fact → Gap loop tight.

Micro-case (what changes after 7–14 days)

At a small‑to‑mid‑size software services firm, the founder ran a pre‑mortem before a new outreach campaign. The team imagined the campaign falling flat because the messaging missed the buyer’s pain point. That gap revealed a missing step in the content review process. The founder assigned the content lead as mitigation owner to add a pain‑point check before any copy went live. Within a week or two, the owner noticed the content lead flagging a couple of drafts that would have missed the mark, and stopped them before they reached prospects. The founder could decide to adjust the messaging without micromanaging the writers, because the risk was already visible and owned.

FAQ

What if the team struggles to imagine failure? Start with a simple prompt: “If we woke up tomorrow and learned the launch was a disaster, what would the headline say?” This opens the imagination without requiring deep expertise. Once the first few ideas flow, the group can build on them and dig deeper into underlying causes.

How long should a pre‑mortem session last? A focused session of thirty to forty‑five minutes is enough for a small team. Larger groups can split into breakout pods of three to five people, then reconvene to merge the findings. The goal is energy, not endurance — stop when the list of distinct failure themes stops growing.

Do we need a facilitator? A neutral facilitator helps keep the tone constructive and prevents blame‑shifting. If no dedicated person is available, rotate the role among senior members who are not directly responsible for the launch outcome. The facilitator’s job is to time‑box the activity and capture the outputs visibly.

How do we turn the pre‑mortem into ongoing work? Assign each mitigation owner a recurring five‑minute check‑in in your daily or weekly rhythm. Treat the update as a status signal, not a performance review. Over time, the habit of early signal sharing reduces surprise and builds confidence in the launch plan.

Can we reuse a pre‑mortem for future campaigns? Absolutely. Keep the template and the list of mitigation owners as a living library. Before each new effort, review the past items, retire those that are no longer relevant, and add fresh scenarios based on the new context. This creates a cumulative risk‑awareness that grows with experience.

Conclusion

Running a pre‑mortem gives founders a clear view of hidden risks before money is spent, turns vague worries into owned actions, and sharpens the Plan → Fact → Gap loop. The practice is lightweight, repeatable, and scales with the team’s maturity.

Take ten minutes today to gather your core team and run a quick pre‑mortem on the next campaign you are planning.

If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the weekly diagnostic works. https://aiadvisoryboard.me/?lang=en