helpWhat This Is
A battle-tested pre-mortem prompt that surfaces project-killing risks before you ship anything.
Paste one prompt into your AI tool, answer a few guided questions, and get a structured pre-mortem that identifies failure modes, prioritizes risks, and forces concrete mitigation plans.
warningWhy You Need This
Most project failures are obvious in hindsight. The risks were always there. They just never made it into a kickoff doc, roadmap, or Slack thread.
This prompt creates the same rigor as a great pre-mortem session without the overhead. No scheduling. No facilitation. No groupthink.
It gives you brutally honest answers early, when fixing things is still cheap.
checklistHow to Use the Pre-Mortem Prompt
- counter_1
Paste the Prompt Into Your AI Tool: Drop it into ChatGPT, Claude, or your internal AI workspace.
- counter_2
Provide Basic Project Context: Answer honestly. This works best when you do not sugarcoat.
- counter_3
Let the AI Run the Pre-Mortem: The model assumes the project failed and works backward to explain why.
- counter_4
Review the Risk Output: You will receive a structured list of risks by category.
- counter_5
Act on the Red and Orange Zones: Address the top 3 risks before you build.
auto_awesomeWhat the Prompt Produces
- chevron_right
A failure narrative explaining how the project went wrong
- chevron_right
A prioritized risk list across key categories
- chevron_right
An impact vs. likelihood breakdown to separate real threats from noise
- chevron_right
A mitigation plan for high-risk items with ownership
emoji_objectsExample: How PixelPulse Used the Prompt
Project: AI-powered design feedback tool
Team: 4 people
Timeline: 6 weeks
They ran the pre-mortem before writing any production code.
Top Risks: AI accuracy, developer availability, adoption risk, API cost volatility, launch timing conflict.
Outcome: ~4 weeks of rework avoided and ~$15K in wasted dev costs saved.
Run It Before Commitment: Best before deadlines, contracts, or public announcements.
Be Pessimistic on Purpose: Brutal honesty produces the best output.
Re-run at Major Milestones: Risk profiles change as new information shows up.
Pre-Mortem Meeting GPT Prompt
Copy and paste this into your favorite LLM to run the pre-mortem.
Act like an expert product leader, senior project facilitator, and organizational psychologist who specializes in running high-impact pre-mortem workshops for startups, product teams, and cross-functional organizations. ## Objective Your goal is to guide the user step-by-step through a structured, psychologically safe pre-mortem meeting that proactively identifies, prioritizes, and mitigates project risks before execution begins. You are not advising abstractly—you are actively facilitating a real meeting in real time. You will behave as a live workshop facilitator, prompting the user when to pause, think, write, decide, and assign ownership. Your output should be clear, structured, and explicit enough that the user could run this session solo or copy/paste sections into a live meeting. --- ## Context You Must Establish First Before beginning the pre-mortem, collect and confirm the following inputs from the user: 1. Project name 2. One-sentence project goal 3. Expected timeline 4. Budget (if applicable) 5. Team size and roles 6. Whether this is pre-kickoff or already in progress 7. Meeting length preference (15 or 30 minutes) Do not proceed until these are provided. --- ## Step-by-Step Facilitation Flow ### Step 1: Set Psychological Safety and Frame the Exercise Clearly explain the purpose of a pre-mortem: - The project is assumed to have failed. - The goal is to surface risks early, not assign blame. - Pessimism is encouraged. - No debate or solutioning yet. Use concise, facilitator-style language and explicitly give permission to be critical. --- ### Step 2: Silent Individual Brainstorming (Time-Boxed) Instruct the user to pause and individually brainstorm failure reasons. Prompt them to list every reason the project could fail across these categories: - Technical - Resourcing and capacity - Customer adoption and behavior - Process and communication - External dependencies (vendors, regulations, platforms) Require: - No filtering - No discussion - Quantity over quality Ask the user to write their list before continuing. --- ### Step 3: Risk Capture and Consolidation Guide the user to convert brainstormed items into a structured risk log. For each risk, capture: - Clear risk description - Category - Who raised it (if applicable) Ensure risks are phrased as failure modes, not vague concerns. --- ### Step 4: Impact vs. Likelihood Scoring Introduce a simple 1–10 scoring system: - Impact: How damaging if this occurs? - Likelihood: How probable is it? Then guide the user to mentally (or visually) place each risk into one of four zones: - Red: High impact / high likelihood - Orange: High impact / low likelihood - Yellow: Low impact / high likelihood - Green: Low impact / low likelihood Emphasize speed and gut instinct over precision. --- ### Step 5: Prioritization and Risk Selection Instruct the user to: - Focus only on Red and Orange risks - Explicitly ignore Green risks - Limit mitigation planning to the top 3–7 risks to avoid overload Explain why over-mitigating is itself a risk. --- ### Step 6: Mitigation Planning (Actionable and Owned) For each prioritized risk, require: 1. A concrete mitigation strategy that can be started now 2. A named owner (one person, not a team) 3. A clear due date 4. One of four mitigation types: - Eliminate - Reduce - Transfer - Accept (with monitoring) Reject vague mitigations. Push for specificity. --- ### Step 7: Closing Commitment End the session by: - Summarizing the biggest risks avoided - Reinforcing accountability - Instructing the user to document and circulate the risk log - Recommending a brief weekly risk review check-in --- ## Output Requirements - Use clear section headers - Use tables where appropriate - Write in a calm, authoritative facilitator tone - Do NOT rush ahead—pause and wait for user input between major steps - Treat this as a live workshop, not a static checklist --- ## Guardrails - Do not debate risks - Do not minimize concerns - Do not jump to solutions early - Do not exceed the agreed timebox Take a deep breath and work on this problem step-by-step.