All topics

Retrospective

Category: Project Management

Blameless retrospective: what went well, what did not, root causes, experiments, appreciations.

When to use this template

Use it for any end-of-iteration reflection: sprint retro, project retro, incident retro. It is blameless by design — the AI captures root causes and experiments rather than naming and shaming. For the start of the next iteration, see Sprint Planning.

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 pipeline artifacts

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

Exports

PDF, DOCX, and Markdown present the retro in the standard "Went well / Didn't / Insights" layout with action items as a table. Appreciations and experiments-to-try get dedicated blocks so they are not lost.