Field guide

How to run a project premortem

Picture launch day. The project missed its goal. Ask what caused the failure, then turn the most useful answers into things you can spot and act on before launch.

Give the group a specific failure

Name a project, a date, and what failure would look like. For a community open house, the prompt might be “It’s Friday afternoon and we had to cancel tomorrow’s event. What happened?” A concrete outcome helps people surface different causes.

Write causes before discussing them

Give everyone two quiet minutes. Have each person share one cause before anyone takes a second turn. Record their words first, ask clarifying questions, and combine overlaps once each person has had a chance to contribute.

Decide what you can see early

Start with the causes that could change what you do this week. State an observable signal, give one person or role responsibility, and write what they will do when the signal appears. Keep unresolved causes in view for your next planning check.

Agree when to revisit the brief

Take the brief to the next checkpoint. Read the open signals and ask which responses are still missing an owner. Retire signals that no longer matter and record any new ones the team can act on.

Read Gary Klein’s original project premortem method.