The short answer
Core relationship: Set a specific future point and failure outcome. Participants first write causes independently, then group mechanisms, assess detectability, and assign preventive or recovery actions.
For run a pre-mortem before an important decision, begin with describe the failed future and finish with convert risks into controls. The sequence keeps the starting facts, intermediate result, and final limit visible instead of relying on memory.
A reliable method
Describe the failed future
Use a concrete outcome instead of saying the plan went badly. Capture the result before moving to write independently. A written output shows whether the next deduction follows from the evidence or quietly adds a new assumption.
Write independently
Silent generation reduces anchoring on the first senior opinion. Compare this output with the warning about generic pessimism. If that failure still fits, revise the representation before using the result in another deduction.
Group by mechanism
Combine duplicates while preserving distinct causal paths. Use group by mechanism as a checkpoint. Name the input, the change made, and the conclusion that becomes available so another reader can reproduce the move.
Convert risks into controls
Assign an indicator, owner, and response for the most important risks. Finish by stating what this step establishes and what it leaves undecided. That boundary prevents a valid local conclusion from being stretched beyond the question.
Failure modes to watch
Generic pessimism
Risks need a mechanism and observable signal. Return to describe the failed future and rebuild only from information the problem actually provides.
Risk list without action
A documented concern does not reduce exposure by itself. Compare the disputed move with group by mechanism; the two should use the same definitions and direction.
Only prevention
Recovery and rollback matter when prevention cannot be guaranteed. Run the practice task while deliberately watching for only prevention. Record the first point where the reasoning begins to drift.
Worked case
Describe the failed future in the case
A product launch missed its date and caused customer confusion. Possible mechanisms include an untested migration, unclear rollback ownership, support scripts arriving late, and dependencies that had no readiness criteria.
Why convert risks into controls matters
The case starts with describe the failed future, then uses write independently to control the next inference. The conclusion is acceptable only after convert risks into controls. Changing any fact that supports those moves can change the answer, while an unrelated detail should not.
Check against generic pessimism
Questions for write independently
- Can another reader reproduce describe the failed future from the stated information?
- Did you complete write independently without reversing or enlarging the claim?
- Does the result survive the failure mode generic pessimism?
- Which part remains uncertain after convert risks into controls?
This check is specific to the method above. A clear answer should expose the evidence chain and the point where a different fact would produce a different conclusion.
Try the method
Run a ten-minute pre-mortem for a current plan. Select two risks and define one early warning and one response for each.
Continue after convert risks into controls
Use the problem prioritization guide for the broader method, then apply the idea in the decision matrix calculator. Keep the written reasoning so the next attempt can improve a specific step rather than simply repeat the exercise.
Compare this method with Design Small Experiments for Problem Solving, then continue to Define Decision Criteria Before Comparing Options for a different reasoning task.