liveBook · Manning

Pre-mortem session

As explained in Collaborative Software Design: How to facilitate domain modeling decisions

A premortem is a prospective risk-analysis technique in which participants imagine that a project or plan has failed and identify the causes of failure in advance.

A pre-mortem is a prospective risk-analysis and sensemaking technique. The group imagines that a project has already failed, then identifies what went wrong instead of speculating about what might go wrong. section 4.10 section 4.3.6

Run the session in four practical moves:

  • Set the stage: ask participants to imagine they are several months ahead and the project has miserably failed, despite everyone’s best efforts. section 4.3.6
  • Have everyone write individual perspectives on stickies before discussing them, creating a safer way to surface reservations and concerns. section 4.3.6
  • Explore three questions: What were our initial goals? What actions did we take? What went wrong? section 4.3.6
  • Review and prioritize the risks together, then decide which mitigation actions to prepare. section 4.3.6

Failure viewed from the future

Instead of asking a project team, “What might go wrong?”, invite them to describe the failed project in hindsight. This shift can make uncomfortable thoughts, conflicting perspectives, and hidden concerns easier to discuss before they hinder progress. section 4.10 section 4.3.6

How Collaborative Software Design: How to facilitate domain modeling decisions covers it

How deep it goes
Explains the framing, individual collection, discussion questions, risk prioritization, and mitigation decision, while remaining a simple exercise.
Examples
Uses a failed-project scenario, sticky-note perspectives, and three questions about goals, actions, and what went wrong.
What it assumes
Assumes a project or plan to examine and teaches participants to voice reservations through a safe hindsight exercise.
What you can do after
Practice/perform a premortem that surfaces risks, prioritizes them, and supports preparation of mitigation actions.
How it connects
Connects sensemaking, risk analysis, group perspectives, potential conflicts, and mitigation actions.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Collaborative Software Design: How to facilitate domain modeling decisions. The section links point to the parts of the book it draws on.