Run a realistic project pre-mortem analysis

Spot overlooked failure modes and blind spots before launching a project. Best used during planning stages to build concrete safeguards.

You getA markdown table with four columns: Failure Mode, Root Mechanism, Early Warning Indicator, Preventive Guardrail. End with a 2-item checklist titled Immediate Launch Safeguards.

Prompt

Prompt
Act as a risk analyst running a pre-mortem on a proposed initiative. Assume the project launched six months ago and turned into an absolute disaster.
- Identify 4 specific, plausible failure modes across operational, technical, team, and market factors.
- Skip generic advice like poor communication and name concrete breakdown mechanisms.
- For each failure mode, list an early warning sign and one preventive guardrail.
Output format: A markdown table with four columns: Failure Mode, Root Mechanism, Early Warning Indicator, Preventive Guardrail. End with a 2-item checklist titled Immediate Launch Safeguards.

The project details and plan are below:

Example output

Example for: migrating an internal CRM to a cloud-based vendor within three months

Failure ModeRoot MechanismEarly Warning IndicatorPreventive Guardrail
Sales rep boycottCustom fields and daily workflows were not mapped correctly to the new layout, doubling data entry time.Daily active usage drops below 40% during the pilot week with complaints about missing lookup tables.Embed two daily super-users directly into field mapping validation before import.
Data corruption in historical recordsLegacy billing schemas lacked unique constraint keys, producing duplicated accounts after the batch transfer.Account totals diverge between the legacy database and the test sandbox by more than 1%.Run a dry-run migration on a cloned staging database with automated checksum comparisons.
Scope-creep delayDepartment leads submitted 18 custom reporting requests outside the core scope two weeks before launch.Unscheduled sprint backlog items grow by more than 15% during month two.Establish a hard freeze: no non-essential report migrations permitted until 30 days post-launch.
Vendor API rate throttlingReal-time pipeline sync hit undocumented API burst limits during month-end closes.Error 429 warnings in sandbox integration logs during load tests.Build an asynchronous event queue that buffers high-volume record updates automatically.
Immediate Launch Safeguards
  1. Sign off on an automated fallback procedure to restore the legacy system within 4 hours if sync fails on launch day.
  2. Appoint one dedicated operations lead with the authority to reject scope requests after week four.
Written by AI from this prompt. Your results will vary.

Paste your project plan or proposal at the end of the prompt in Claude, ChatGPT, or Gemini. As a follow-up, ask the model which single failure mode poses the highest financial risk.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Critical Thinking & Decisions
Critical Thinking & Decisions

Set upfront kill criteria for new initiatives

Establish measurable off-ramps and stop conditions before launching a project. Use this to protect budget and team focus from the sunk cost fallacy.