Synthesize past project lessons into kickoff safeguards

Turn historic post-mortem archives into practical governance rules, charter additions, and pre-mortems for upcoming projects.

You getPast Failure Analysis, charter Safeguards & Policy Updates and kickoff Pre-Mortem Questions

Prompt

Prompt
Act as an enterprise project operations director. Review these post-mortem reports from completed projects and convert their failure modes into proactive kickoff safeguards for our new project.

Follow these rules:
- Identify the top 3 systemic failure points that repeated across past efforts.
- Draft specific clause language or checklist items for the new project charter to prevent each failure.
- Formulate a 5-question pre-mortem exercise for the project kickoff team.
- Keep all recommendations concrete, enforceable, and measurable.

Output format:
- Past Failure Analysis
- Charter Safeguards & Policy Updates
- Kickoff Pre-Mortem Questions
- Governance Checklist (columns: Milestone, Preventive Check, Responsible Role)

Past project notes are below:

Example output

Example for: past post-mortems of three enterprise CRM rollouts

Past Failure Analysis
  1. Unvalidated Data Migration: In all three projects, legacy data cleanup began after configuration, creating 6-week delays at cutover.
  2. Stakeholder Availability Collapse: Department leads missed UAT windows due to routine operational duties.
  3. Vendor Dependency Gaps: Third-party integrations were planned without written confirmation of vendor release schedules.
Charter Safeguards & Policy Updates
  • Data Readiness Gate: System configuration will not start until 80% of legacy records pass schema validation scripts.
  • Protected Allocation Policy: Charter must include explicit 10 hours per week committed business lead availability signed by executive sponsors.
  • External Interface Contract: Integration milestones require written technical design signoff from third-party vendor leads prior to Sprint 1.
Kickoff Pre-Mortem Questions
  1. If this project launches 60 days late, did we fail on data cleansing or stakeholder signoff?
  2. What missing sandbox environment could stall integration testing in Month 3?
  3. Which specific business process owner lacks a designated backup when on leave?
  4. What assumption about our source database schemas have we not physically verified?
  5. If our external vendor misses their delivery date, what fallback workflow exists?
Governance Checklist
MilestonePreventive CheckResponsible Role
Project KickoffSigned time commitments from business unit heads secured.Project Director
Sprint 0Legacy source data audit completed and error log quantified.Lead Data Architect
UAT Initiation100% of test scenarios pre-validated with cleaned production-like data.QA Lead
Written by AI from this prompt. Your results will vary.

Paste closing summaries or post-mortem notes from two or more past projects into Claude, Gemini or ChatGPT. Ask the model to adjust the governance checklist based on your team size.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Project Management
Project Management

Audit a RACI chart for split accountability

Identify dangerous governance flaws, duplicate owners, and delivery bottlenecks in an existing RACI matrix. Use this before launching high-stakes projects.