Alignment & delivery

Pre-mortem

"It is six months from now and the project has failed. Why?" Everyone writes, we group, we prevent.

When. The most profitable exercise before a big initiative: it gives permission to name the risks nobody dares mention.

Duration
1 h
Participants
Project team + sponsor
Output
Top risks + mitigations
Stage
Pre-PMF · Post-PMF · Scale-up · Mature
Causes of failureGroupingMitigations
Open in FigJamFind the right sequence

In FigJam: File → Duplicate to your drafts, then keep this workshop's section. Get the file on Figma Community

Filled example

Causes of failureSync conflicts wipeda technician'safternoon twicePhotos queuedoffline neverreached invoicingLéa never turned iton, the toggle wasin settingsAndroid 9 vans losthalf the featureTwo squads arguedabout who owns thesync engineWe shipped in July,half the customerson holidaySupport had no wayto see a stuck queueScope grew to fulloffline dispatchGroupingData loss and trust(3 causes)Adoption anddiscoverability (2causes)Ownership and scope(3 causes)MitigationsConflict rulewritten before code:field wins, officegets a diffOffline on bydefault, visiblebanner when queued,Ana owns itField app squad ownssync end to end, Tomsigns the APIcontractSupport screen forstuck queues in thesame release, Julientests itShip in September,beta with Sophie's22 technicians first

Example data. Fieldnote is a fictional company used to fill all 61 boards, so the examples tell one consistent story.

Post-PMF Fieldnote, the week before starting the offline mode project: Karim, Tom, Ana, Julien and Élise imagine it is six months later and offline mode failed.

What the team took away

Nobody had said out loud that the toggle would live in settings. Five mitigations, five owners, the scope stays at intervention logging only.

How to run it

Preparation

Agenda

  1. 5 min
    Set the scene
    Say it exactly like this: 'It is six months from now. The project failed badly. Not delayed, failed.' Do not soften it.
  2. 10 min
    Write the causes
    Everyone writes, in silence, one cause per sticky. Push for volume: at least 5 per person. Nobody speaks.
  3. 15 min
    Read around the room
    Go around, one sticky per person per turn, until all are on the board. No comment, no defense, no 'that would never happen'.
  4. 15 min
    Group and vote
    Cluster similar causes. Each person gets 3 dots for the causes they find most likely. Take the top 5.
  5. 15 min
    Mitigate
    For each of the top 5: what do we change in the plan this week? One action, one owner, one date. Write it in the Mitigations column.

Pitfalls

Afterwards

The top 5 risks and their mitigations go into the kick-off canvas or the project risk log. Review them at the first milestone: which ones happened anyway?

Source : Gary Klein

Related workshops

Back to the compassAll workshopsVersion française