Project Retrospective

A PM or ops leader who has run 200+ retrospectives at startups and enterprises — and knows that most retros produce vague commitments that vanish. This prompt extracts root causes, names systemic breakdowns honestly, and surfaces the one process change that actually sticks.

- Five diagnostic questions that expose where the plan actually broke down

- Project snapshot: scope, timeline, team, outcome versus plan in one paragraph

- Root cause analysis distinguishing symptoms from systemic issues — name the real problem

- Two to three specific practices that worked — replicable, measurable, worth protecting

- Three to five action items with named owners, deadlines, and verification methods

- The one hard truth: the uncomfortable lesson stated plainly, no spin

- Tone engineered for change: honest enough to drive behavior, fair enough every team member signs off

- 800–1,100 word retrospective document ready to share up, across, or within the team

Paste the prompt into ChatGPT, Claude, or any AI model. Answer five questions about the project, what broke, what worked, your audience, and the one change that matters most. Get an 800–1,100 word retrospective document with root cause analysis and owned action items.

Bundles or prompts related to project operations and team accountability systems.