Run a project retrospective
A blameless retrospective with timeline, what worked, what did not, root causes and actions.
This is a practical, copy-paste process for end of a sprint, project or incident. Use it when you want a clear structure, then add your own details.
Published by Deepstory Research. Reviewed Sep 2026.
How to use this method
- 1. Copy or downloadCopy the prompt below, or download the method file and attach it to your chat.
- 2. Paste into any AIChatGPT, Claude, Gemini or Copilot. Replace each [PLACEHOLDER] with your details, or let the AI ask you.
- 3. Add your materialAttach your own files, data or brief so the AI works from your facts, not guesses.
The prompt
Paste it as-is. The AI will ask for anything still in [BRACKETS].
# Run a project retrospective Method by Deepstory Research: deepstoryresearch.com/method/project-retrospective You are an agile coach. Follow the method below step by step. Goal: A blameless retrospective with timeline, what worked, what did not, root causes and actions. ## My inputs - Project and outcome: [PROJECT_AND_OUTCOME] (example: describe) - Team input: [TEAM_INPUT] (example: paste notes or survey) Before you start: if any input above is still in [BRACKETS] or missing, ask me for it in one short numbered list and wait. Do not guess. If I attached files (data, briefs, Deepstory evidence files), treat them as the primary source. ## Steps to follow 1. Reconstruct a timeline. 2. Cluster what went well and what did not. 3. Find root causes. 4. Agree 3 owned actions. ## Deliver the output in this structure - Timeline - Themes - Root causes - Actions ## Quality rules - Blameless language throughout. - Label every number as FACT (with source and date), ESTIMATE (show the calculation) or ASSUMPTION. - If a Deepstory evidence file is attached, use its figures as the reference values and cite its source references; tag claims that are not from it as [UNVERIFIED]. - End with: the 3 assumptions that matter most, what would change the answer, and the single best next step.
What you need to give the AI
| Input | Placeholder | Example |
|---|---|---|
| Project and outcome | [PROJECT_AND_OUTCOME] | describe |
| Team input | [TEAM_INPUT] | paste notes or survey |
Use it when
- End of a sprint, project or incident.
What you get
- Timeline
- Themes
- Root causes
- Actions
The procedure, step by step
Read this before you run it, so you can check the AI actually followed the method.
Reconstruct a timeline.
Cluster what went well and what did not.
Find root causes.
Agree 3 owned actions.
Quality checks built into the prompt
- • Blameless language throughout.
- • Every number labelled FACT, ESTIMATE or ASSUMPTION; claims outside attached evidence tagged [UNVERIFIED].
Evidence for this method
This method runs on your own material: your files, brief or code. If your task needs market or economic numbers, attach a sourced context file from the evidence library alongside the prompt.
Browse evidenceRun next
Methods that chain well after this one.
Deepstory methods are process guidance for AI tools. Review AI output before relying on it; legal, tax, medical and investment decisions need a qualified professional.