A practical facilitator's guide to running a pre-mortem workshop: timing, participant selection, a five-phase agenda, and turning surfaced risks into owned actions.

Project debriefs keep finding the same thing: the warning signs were there all along, and someone didn't feel safe saying them out loud. A pre-mortem gets those warnings said while there is still time to act on them.
The method is simple to explain and hard to facilitate well. This guide covers why it works, how to put together the right group, a five-phase agenda you can run in 90 minutes, and how to make sure the outputs still matter the following Monday, which most guides leave out.
What a pre-mortem is and why the cognitive mechanism matters
Research psychologist Gary Klein developed the pre-mortem and introduced it to a broad management audience in Harvard Business Review in 2007. It turns the post-mortem around. Before the project launches, you ask the team to imagine that it has already failed badly, and then to work backwards and explain why.
The reframe works because of a cognitive effect called prospective hindsight. People are considerably better at explaining past events than predicting future ones, because they treat the past as fixed and search harder for causes. Klein's HBR piece cites 1989 research by Deborah Mitchell, Jay Russo and Nancy Pennington which found that prospective hindsight, imagining that an event has already occurred, increases the ability to correctly identify reasons for future outcomes by 30%.
The second mechanism is social. In ordinary planning meetings, especially when a senior leader is visibly invested in the plan, people hold back doubts so they don't look disloyal or obstructive. In a pre-mortem, pessimism is the task. Raising concerns is what the group is there to produce.
Optimism bias, the habit of underestimating cost and timeline, is a familiar problem in project planning, and a pre-mortem counters it through the structure of the session.
Picture a product team running a pre-mortem before launching a new software platform. Within minutes, a junior engineer points to a dependency on a third-party API that nobody has stress-tested. Everyone assumed the API was stable; imagining the failure shows it to be a single point of failure. The team builds a fallback before launch. If the API then fails in week two, the team handles a managed incident instead of a crisis.
When to schedule a pre-mortem
Timing matters more than most facilitator guides admit. The best window is after the plan is detailed enough to critique and before resources are fully committed and sunk-cost thinking sets in. In practice that means after the project charter or business case is approved and before the formal kick-off or budget release.
Run it too early and you get abstract worries about hypothetical problems. Run it too late and participants are invested in the plan succeeding. They will rate risks as unlikely because admitting otherwise feels like attacking their own work, not because they believe it.
In longer programmes, pre-mortems also help at phase gates, for example at the move from discovery to delivery or before a major go/no-go decision. There they test the assumptions that piled up during the previous phase, which is a different and useful job.
Some projects make a pre-mortem especially worthwhile: tight deadlines with little slack, teams working together for the first time, many external dependencies, politically sensitive launches, and any initiative that rests on an assumption nobody has tested in practice. If two or more of these apply, the 90 minutes are well spent.
Building the right room
Treat the participant list as a facilitation decision. It is more than admin.
Rooms work best with 6 to 12 participants from three groups. The first is the core project team, who know the plan in detail and are accountable for delivery. The second is adjacent stakeholders who will be affected by the project without running it; they see risks the core team is too close to notice. The third is at least one real outsider: a colleague from another function, a recently onboarded team member or a customer proxy. The outsider's unfamiliarity with the plan is useful, because they ask the questions the core team stopped asking months ago.
A citizen-facing project shows why. Imagine a team preparing to launch a public web portal that runs its pre-mortem with developers, a policy lead, a content designer and two members of a citizen advisory panel. The citizen representatives could well raise the most important risk of the session: the portal assumes every user has a valid email address, but the target group (older benefit claimants) is less likely to have one. That risk would not appear on any technical risk register, because nobody on the core team would think to look for it.
In practice, cross-functional groups find a wider range of failure modes than homogeneous ones. A room of engineers finds technical risks well. Add a finance analyst and budget risks appear; add a customer success manager and adoption risks appear. The more varied the room, the more of the failure space it covers.
Hierarchy works against honest pre-mortems. If the project sponsor is in the room and visibly attached to the plan, junior participants censor themselves. You have two options: brief senior attendees beforehand to reward dissent instead of showing discomfort with it, or have the sponsor join only for the synthesis phase, after the failures have been identified. Some facilitators keep the sponsor out of the ideation phase entirely, so the sponsor reviews the output and not the process.
An agenda in five phases
A 90-minute pre-mortem for a team of 8 runs like this:
- Minutes 0-10: briefing. Share the plan; a summary is enough. Then set the frame explicitly: "It is now 12 months from today. This project has failed badly. The launch went wrong, stakeholders are unhappy, and we're trying to understand how we got here." A specific scenario produces specific outputs.
- Minutes 10-18: silent generation. Everyone writes failure causes on their own, one per sticky note or card. No discussion and no sharing yet.
- Minutes 18-45: round-robin harvest. Each person shares one item at a time, going round until every unique item is on the board. The facilitator clusters as they go.
- Minutes 45-65: prioritisation. The group dot-votes or scores items by severity and likelihood and picks out the top 5 to 8.
- Minutes 65-90: ownership. Each prioritised risk gets a named owner, a specific mitigation action and a follow-up date.
Silent generation is the phase teams skip most often, and skipping it does the most damage. Andrew Van de Ven and André Delbecq's 1970s research on the nominal group technique (structured independent idea generation before group discussion) found that it produces more ideas than open group discussion. It also stops the first vocal participant from anchoring the room. Without it, the risk list reflects the most senior or most confident voice instead of everything the group can see.
If time allows, add a "pre-parade" with a smaller group after the failure exercise. The frame flips: "the project exceeded all expectations, customers love it, and we're trying to understand what specifically made it succeed." This brings out hidden strengths and unstated assumptions about what good looks like. It also keeps participants from leaving in a purely defensive mood about a project they will spend months delivering.
Turning surfaced risks into owned actions
The most common way a pre-mortem fails is a long risk list that sits in a shared document and is never opened again. Participants then see the exercise as theatre. This is entirely preventable.
Every prioritised risk leaves the room with a named owner, a specific mitigation action and a date to report back. "Monitor this" is not an action. A specific mitigation reads like "Build a fallback API integration by [date], owned by [name]" or "Conduct a stakeholder alignment meeting with [person] before [date], owned by [name]."
Give each risk to the person closest to it. A technical risk belongs to a technical lead, a stakeholder communication risk to the comms or change lead. When ownership defaults to the most senior person in the room, accountability spreads thin and actions stall, so push back on that default.
The outputs last longest when the findings go straight into the project's existing governance documents: the RAID log (Risks, Assumptions, Issues, Dependencies), the project brief or the team charter. One way to do it: the facilitator has every risk entered into the RAID log on a shared screen before anyone leaves, each with an owner and a mitigation due date. At the next weekly stand-up, the RAID log is the first agenda item. If some of the top risks materialise during the project, they already have owners and plans, which makes it far less likely that they turn into critical incidents.
Facilitation mistakes worth avoiding
Apart from skipping silent generation and leaving risks without owners, two mistakes are hard to see until you've made them.
The first is letting the session slide into solutions while the group is still identifying failures. As soon as someone says "we could fix that by...", attention shifts from finding problems to defending fixes, and the list stops growing. Interrupt it directly: "We're not solving yet. We're still looking for what could go wrong."
The second is the false-comfort pre-mortem, where the group lists risks carefully but agrees to rate them all unlikely to avoid discomfort. It looks like a working session, which makes it hard to spot. The giveaway is a list where every item scores 2 out of 5 on likelihood. Have participants rate risks individually before the group compares ratings, or name the dynamic: "Our job right now is to make this list as alarming as possible. Probability calibration comes later."
Both depend on psychological safety. Amy Edmondson's research on hospital nursing units found that the units with better leadership and working relationships reported more errors, most likely because people there felt safer admitting them. The same holds for pre-mortems: a room where people feel safe voicing uncomfortable concerns produces a more honest, and therefore more useful, risk list.
Pairing the pre-mortem with scenario planning and three horizons
A pre-mortem examines one failure scenario in depth, which is both its strength and its limit. For projects facing real strategic uncertainty, where the future itself is in dispute, combining it with scenario planning widens what it covers.
Use scenario planning first to find the key uncertainties behind different futures, which typically gives you 2 to 4 plausible scenarios. Then run a pre-mortem for each high-stakes scenario. Risks that show up in several scenarios come first, because they hold whatever happens. Risks that show up in only one scenario depend on that future and can be monitored accordingly.
The Three Horizons framework adds another angle. Pre-mortems on Horizon 1 (optimise current operations), Horizon 2 (build emerging capabilities) and Horizon 3 (transformative bets) produce different kinds of risk. Horizon 1 risks tend to be operational and near-term, Horizon 2 risks involve capability gaps and transition costs, and Horizon 3 risks involve wrong assumptions about what the future will demand. Tagging risks by horizon during the pre-mortem adds strategic depth to the output without making the session longer.
Workshop Weaver supports all three methods, with templates and facilitation guides designed to work together. If your pre-mortem is part of a larger planning cycle, use the scenario planning and three-horizons resources there alongside this guide.
Running your first one
Pick one upcoming project (a product launch, a strategy pivot, a new team) and schedule a 90-minute pre-mortem before the kick-off. The five phases, in order: brief the plan and set the failure frame, generate risks silently, harvest by round-robin, prioritise by vote, assign owners with dates.
A pre-mortem is less pessimistic than it sounds. It finds the problems you can still fix while there is time to fix them. The warning signs are almost always there, and the method gets them into the open before the debrief.