The Inner Steady

The Project Premortem: Find Weak Points Before the Plan Hardens

By The Inner Steady Editorial Team

·

2–3 minutes
Three colleagues inspect an early project prototype and blank cards before launch, considering possible obstacles together.

A small team is preparing a public workshop. The venue is booked, the speaker has agreed, and the announcement is ready to go. Everyone likes the plan, so the remaining uncertainties stay unspoken: What if registration is slow? Who will cover if the speaker cancels? When does the venue need a final head count?

A premortem gives those questions a place before the project is under way. The team imagines that a specific future milestone has already been missed, then privately lists believable reasons. This differs from a postmortem, which explains something that happened. The premortem is a planning exercise designed to make concerns easier to raise while there is still time to adjust.

A team member privately writes on a blank card before a group discussion, illustrating independent thinking during a premortem.

Run the exercise in three passes

  1. Set a concrete future point. “Six weeks from now, the workshop was postponed” gives people a clearer prompt than “What could go wrong?”
  2. Think alone before comparing notes. Give everyone a few quiet minutes to write possible causes. This reduces the chance that the first confident voice will define the whole discussion.
  3. Turn causes into signals and changes. For each plausible issue, name what you could notice early and what you would do if it appeared.

A useful result is not a long catalogue of disasters. It is a shorter list of preventable weak points: a deadline with no owner, a single contact who holds essential information, or a decision that needs to happen earlier than the team assumed. Sort concerns by how soon they could become visible and whether a small change would reduce their impact.

Keep the exercise proportionate. A premortem is not a probability model and does not guarantee success. It also should not become a way to blame whoever raised a concern. The aim is to make responsible disagreement useful before people become attached to a plan.

For a companion tool focused on underestimated time, see our article on the planning fallacy. A schedule estimate and a premortem answer different questions: how long might this take, and what could keep it from working?

Prospective-hindsight research has examined how imagining a future event as if it had already occurred changes the reasons people generate. Gary Klein later described the premortem as a project-planning application. Use it to widen the conversation, then verify the risks with evidence.

Research note

See Mitchell, Russo, and Pennington’s study of prospective hindsight and Gary Klein’s practical account, “Performing a Project Premortem”.

✎ Write