startthat.work home

CH-08 Premortem (prospective hindsight, inversion) Also serves: Project forward.

Asks a team to assume the plan has already failed and to write the reasons, and produces a grouped list of failure reasons and draft assumptions.

ChallengeEvidence: PracticeChallenge technique, runs in step 6Strongest statement: describe

What it does

Asks a team to assume the plan has already failed and to write the reasons. Artefact: a ranked or grouped list of failure reasons; read clusters and reasons raised only by sceptical members.

When to use it

Use when a plan is about to be adopted and you want the team to say why it might fail while it can still change.

When it does not fit

It is run after the decision has been taken, or reasons are not converted into plan changes or monitored indicators.

Result format

The result is a ranked or grouped list of reasons the plan failed, written as if the failure had already happened, with the assumptions behind them in an assumptions list. It names the clusters of reasons and the reasons raised only by sceptical members.

Requirements on the material

PropertyRequirement typeRequirement
Unit of analysisAlways appliesrequires=topic
Appraises source credibilityApplies in some casesno

Not restricted on: Structure, Content type, Variable types, Time structure, How the sample was chosen, Level of detail available, Number of sources, Whether sources can be joined, Amount of material, Known data problems, Producer interest, Source dependence, Origin, Document genre, Language, Personal information, Security classification, Licence.

Minimum materialA plan with a decision date and a team, with about 20 to 30 minutes.
Additional sources needednone
Not for (rules)none
Not for (text)It is run after the decision has been taken, or reasons are not converted into plan changes or monitored indicators.

Choosing and ordering

Kind of techniqueChallenge technique, runs in step 6
Phase tagvalidate
Other phase tagsconclude
Kind of findingrisk; pattern
Question answeredwhat next; why
Strongest statement it supportsdescribe
Needs as input
Makes as output
Must exist firstNone
Loop targetproceed with limit stated

Library checks by stakes

Each stakes level includes the checks of the level below it. Checks that need a person apply at high stakes only, so the process leaves them out at lower stakes (decision 38). Repeatability: judgement dependent.

StakesCheckPerson involvedCounts as a different method
exploratoryassumption and limitation statementnoneno
decision-informingassumption and limitation statementnoneno
decision-informingindependent reviewneeded; left out below high stakesno
high-stakesassumption and limitation statementnoneno
high-stakesindependent reviewneededno
high-stakesexpert reviewneededno
high-stakessecond technique with different assumptionsnoneconditional

Failure modes and limits

Model suitabilityhuman judgement required
Typical model failureProduces a generic failure list from general knowledge in place of the views of the team members, including the sceptics.
Error sourcesinput data; coder or rater judgement; language model
Certainty limitsDescribed by Klein in 2007; the commonly quoted effect figure is unconfirmed and no evidence of improved outcomes was found.

Evidence and tag basis

Practice. Described by Klein in 2007; the commonly quoted effect figure from Mitchell, Russo and Pennington (1989) is unconfirmed, and no evidence of improved outcomes was found. (Klein, Performing a project premortem, Harvard Business Review; Wikipedia, Pre-mortem)

Tag basis: input profile inference; selection inference; sequencing inference; robustness inference. All tag values are inference unless a source is named.