Analysis Retrospective
Project: [name]
Analyst(s): [names]
Date of retro: [YYYY-MM-DD]
Framework used: Start/Stop/Continue / 4Ls / Timeline / Solo
Time spent on retro: [X minutes]
Project Summary
What we delivered: [1 sentence]
Planned timeline: [start] → [end]
Actual timeline: [start] → [end]
On time? Yes / No (+[X] days)
Stakeholder satisfaction: Positive / Mixed / Negative
What Went Well
- [What worked and should be repeated]
- [What worked and should be repeated]
- [What worked and should be repeated]
What Didn't Work
| Issue | Root cause (5-whys) | Category |
|---|---|---|
| [e.g. Data access took 2 days longer than expected] | [Didn't raise the access request until day 2 of the project] | Planning |
| [e.g. Stakeholder changed the scope after kickoff] | [Requirements weren't documented and signed off] | Scoping |
Categories: Planning / Data quality / Scoping / Communication / Technical / Estimation / Other
Surprises
Things we didn't anticipate that materially affected the project:
- [Surprise 1 — what it was and how it affected the project]
- [Surprise 2]
Learnings Worth Capturing
| Learning | Where it goes | Owner | Status |
|---|---|---|---|
| [e.g. Always check Salesforce data freshness before using — it can lag by 48h] | [data catalog entry for Salesforce] | [name] | Open |
| [e.g. Add a "data access confirmed" milestone to every analysis plan] | [analysis_plan_template.md] | [name] | Done |
Action Items
| Action | Owner | Due date | Status |
|---|---|---|---|
| [specific, measurable action] | [name] | [date] | Open |
Next Retro Check-in
Date: [YYYY-MM-DD] — will review whether this retro's actions were completed.