Run a Pre-Mortem Analysis to Prevent Project Failure Before It Happens
Conduct a pre-mortem analysis to identify project risks, root causes, and preventive actions before your project even begins.
📝 The Prompt
Act as a senior project risk strategist trained in Gary Klein's pre-mortem technique and cognitive bias mitigation. Facilitate a thorough pre-mortem analysis for my upcoming project to identify and prevent likely failure modes before work begins.
Here is my project context:
- Project name/description: [PROJECT NAME AND 1-2 SENTENCE DESCRIPTION]
- Timeline: [START DATE] to [END DATE]
- Team size and key roles: [DESCRIBE TEAM COMPOSITION]
- Budget or resource constraints: [DESCRIBE CONSTRAINTS]
- Definition of success: [WHAT DOES A SUCCESSFUL OUTCOME LOOK LIKE?]
- Stakeholders who must be satisfied: [LIST KEY STAKEHOLDERS]
- My biggest worry about this project (gut feeling): [DESCRIBE CONCERN]
Please conduct the pre-mortem in these structured phases:
1. **Imagined Failure Narrative**: Write a vivid, realistic 150-word story set at [END DATE] describing how this project failed spectacularly. Make it specific to my context, not generic.
2. **Failure Mode Identification**: Based on the narrative and my project details, list 8-10 distinct failure modes organized into categories: People & Communication, Process & Execution, Technical & Quality, and External & Environmental.
3. **Probability-Impact Matrix**: Place each failure mode on a 2x2 matrix (High/Low Probability × High/Low Impact) and identify the top 5 'red zone' risks.
4. **Root Cause Drill-Down**: For each red-zone risk, apply the '5 Whys' technique to uncover the deepest root cause.
5. **Preventive Action Plan**: For each red-zone risk, define one preventive action (stops it from happening) and one contingency action (limits damage if it does happen). Assign a suggested owner role and a trigger date or signal.
6. **Early Warning Dashboard**: Create a table of 5 leading indicators I should monitor weekly that will signal the project is drifting toward failure, with specific thresholds for escalation.
7. **Cognitive Bias Check**: Identify 3 cognitive biases (e.g., planning fallacy, groupthink, sunk cost) most likely to affect this project and suggest one countermeasure for each.
💡 Tips for Better Results
Run the pre-mortem with your actual team if possible — share the AI output as a starting framework, then let each team member add failure modes anonymously to surface concerns people are afraid to voice. Schedule the pre-mortem when there is still time to change the plan (ideally before the kickoff, not after). Revisit the early warning dashboard in every weekly standup to catch drift early.
🎯 Use Cases
Project managers, team leads, and founders launching high-stakes projects who want to proactively surface hidden risks and build contingency plans before committing resources.