All topics

Retrospective meeting notes template

Category: Project Management

A retrospective meeting notes template is for end-of-iteration reflection: sprint retro, project retro, or incident retro. It is blameless by design - the structure captures root causes and experiments rather than naming and shaming. Pair it with Sprint Planning when the next cycle starts.

The AI fills period / sprint label, what went well, what did not, insights and root causes, action items (owner, due date, success metric), experiments to try, appreciations, and a parking lot for off-topic items. The Project Manager role view is available on this template; study mode is not.

Fields: Period/sprint · What went well · What didn’t · Insights & root causes · Action items · Experiments · Appreciations · Parking lot · Key takeaways.

Artifacts: Email draft · Project Manager role view.

Sample outline (demo data)

Sprint 13 retro

Went well: Feature flags cut rollback time; design joined grooming early.
Didn’t: Flaky e2e suite burned half a day; unclear owner on mobile crash.
Insights: Test parallelization debt + missing on-call rotation for mobile.
Action items: Sam - quarantine flaky specs by Fri (metric: <2 flakes/day). Alex - publish mobile on-call roster (metric: roster in #eng).
Experiments: Time-box “bug bash Friday” for one sprint.
Appreciations: Jordan for the launch checklist.
Parking lot: Revisit monorepo tooling in Q4.

Fields captured

Period / sprint - what just ended (e.g. "Sprint 13" or "Q3 - Sprint 2").
What went well - patterns and wins to keep doing.
What didn't go well - friction and pain points to address.
Insights & root causes - the "why" behind what did not go well.
Action items - each with owner, due date, and a success metric.
Experiments to try - small, low-cost ideas to try in the next cycle.
Appreciations - shout-outs and thanks to teammates.
Parking lot - off-topic items set aside for later.
Key takeaways - the AI's prioritized summary points.

The standard summary, attendees, and per-section summaries also apply.

Sub-views, role views, and artifacts

Sub-views: none.
Role views: Project Manager.
Artifacts: Email draft (recipient, tone, optional subject hint).
Study mode: not available.

Exports

PDF/DOCX/Markdown use the classic Went well / Didn’t / Insights layout with action items as a table; appreciations and experiments get dedicated blocks.