Skip to main content
OperationsRisk IdentificationadvancedFeatured

Project Delivery Risk Pre-Mortem & Mitigation Matrix

Conduct a pre-mortem analysis to anticipate hidden technical and operational project delivery failures.

Compatibility & Specs

Compatible AI Models
ClaudeChatGPTGemini
Last UpdatedOct 3, 2026
Customizable Variables3 parameters

How to Use This Prompt

Follow this 3-step workflow to extract high-signal responses from any compatible AI model.

01

1. Tailor the Parameters

Use the interactive customizer above to substitute the bracketed placeholders with your exact context, requirements, and constraints.

02

2. Send to AI Model

Copy the prompt and paste it into Claude, ChatGPT, Gemini, or Copilot. These models follow structured multi-step constraints reliably.

03

3. Review and Iterate

Review the output against the verified benchmark below. Follow up in the conversation to stress-test edge cases or refine tone.

Prompt Variables & Parameters

Reference breakdown of every dynamic variable embedded in this prompt template.

PlaceholderParameter NameTypeStatusDescription & Guidance
[project_scope]Project Scope & Key DeliverablestextareaRequiredWhat the project aims to deliver and main milestonesDefault: Migrating 150,000 active customer accounts from a legacy monolithic billing system to Stripe Billing and automated invoicing, including custom historical contract terms.
[stakeholders_deps]Stakeholders & External DependenciestextareaRequiredTeams involved and external vendors or APIs relied uponDefault: Finance & Accounting, Sales Operations (maintaining custom CRM rate cards), Core Backend Engineering team, and Stripe Professional Services.
[constraints_context]Timeline, Budget & Team CapacitytextRequiredHard deadlines and bandwidth limitationsDefault: Hard regulatory deadline of December 31 before legacy billing vendor shuts down API. Team of 3 backend engineers and 1 part-time QA analyst.

Example Execution & Benchmark Output

Sample input arguments and the verified AI response demonstrating expected quality and formatting.

Sample VariablesInputs
[project_scope]
Migrating 150,000 active customer accounts from a legacy monolithic billing system to Stripe Billing and automated invoicing, including custom historical contract terms.
[stakeholders_deps]
Finance & Accounting, Sales Operations (maintaining custom CRM rate cards), Core Backend Engineering team, and Stripe Professional Services.
[constraints_context]
Hard regulatory deadline of December 31 before legacy billing vendor shuts down API. Team of 3 backend engineers and 1 part-time QA analyst.
Expected AI ResponseVerified Result
### Project Pre-Mortem: Enterprise Billing System Migration #### 1. Future Failure Post-Mortem Narrative (Assume It Failed on Dec 31) *'The migration failed because 15% of our highest-paying enterprise customers possessed unmapped custom discount clauses buried in PDF contracts rather than our database. When the automated Stripe billing cutover script ran on Dec 15, it double-charged 40 enterprise clients and locked out 1,200 accounts, triggering an emergency rollback 10 days before the legacy vendor sunset.'* #### 2. Risk Exposure Matrix | Risk Event | Category | Likelihood | Impact | Score (L x I) | | :--- | :--- | :--- | :--- | :--- | | **Data Schema Drift:** Legacy contract edge cases fail validation | Technical | High | High | **Critical (P0)** | | **Double-Billing Webhook Loop:** Race conditions in dual-run phase | Technical | Medium | High | **High (P1)** | | **Finance Reconciliation Delay:** Ledger mismatches halt cutover | Operational | High | Medium | **High (P1)** | | **Key Person Dependency:** Only 1 engineer understands legacy schema | Resource | High | High | **Critical (P0)** | #### 3. Leading Indicator Smoke Signals * *Smoke Signal 1:* The migration validation script fails on more than 2% of staging records during initial test runs. * *Smoke Signal 2:* Finance is unable to reconcile sample customer ledgers within 48 hours of weekly test runs. #### 4. Circuit Breakers & Mitigations * **Shadow Dual-Run Architecture:** Run legacy and Stripe billing in parallel for 45 days. Verify 100% invoice penny-accuracy in shadow mode before issuing live customer charges. * **Legacy Knowledge Colocation:** Require pair-programming on all migration scripts; document legacy edge case dictionary in shared repository.

Best Use Cases

Scenarios and roles where this prompt produces maximum leverage.

Technical Program Managers conducting pre-mortems before critical software cutovers
Engineering leads evaluating dependencies and hidden single points of failure
Executive sponsors establishing risk thresholds for enterprise digital transformations

Tips for Best Results

Techniques to elevate response fidelity

  • •Provide rich background context rather than one-sentence inputs to receive deep, non-generic responses.
  • •Engage in multi-turn conversation: use the initial output as a baseline, then ask the AI to sharpen specific sections.
  • •Prompt the model to highlight any hidden assumptions or missing trade-offs in its recommendations.

Common Mistakes to Avoid

Frequent failure modes and anti-patterns

  • •Giving minimal context and expecting nuanced, expert-level strategic output.
  • •Not validating factual references, citations, or statistical claims with verified primary sources.
  • •Skipping the customization step and pasting raw bracketed template variables into the AI chat.

Part of Curated Collections

This prompt is sequenced as part of these goal-oriented workflows

View all collections

Related AI Prompts

Complementary workflows in Operations

View all Operations prompts
Operationsbeginner

Chaotic Meeting Notes to Structured Action Item & RACI Matrix Converter

Transform messy, unstructured meeting transcripts and bullet points into crystal-clear accountability matrices.

claudechatgptgemini
#operations#meeting-notes#action-items
Operationsintermediate

Executive Project Status Report & RAG Health Dashboard Generator

Generate concise, executive-level project status reports using the RAG (Red-Amber-Green) health framework.

claudechatgptgemini
#operations#project-status#executive-reporting
Codingadvanced

Architectural Decision Record (ADR) Analysis & Trade-Off Matrix

Evaluate competing technical architectures, state assumptions, and document a formal Architectural Decision Record.

claudechatgptgemini
#system-architecture#adr#trade-offs

Related Engineering Guides

Deep-dive playbooks and system prompt methodologies for Operations

View all guides