Retrospective templates
Retrospective guides Updated 8 min read

Retrospective examplescards, themes, and action items

See realistic retrospective card examples and how teams turn vague complaints into specific, testable actions.

Useful retrospective examples are specific enough to discuss and small enough to act on. A card should describe an observed event, behavior, or condition and its effect—not merely name a topic such as “communication.”

Retrospective card examples

Use these as patterns for specificity. Replace the details with evidence from your own team.

Went well

  • Pairing on the first migration story exposed the data issue two days earlier.

  • The smaller pull requests kept review waiting time under one day.

  • Support joined refinement and clarified the top customer failure.

To improve

  • Three stories entered the sprint without confirmed dependency owners.

  • Release approval waited until the only reviewer returned.

  • The staging dataset hid the performance problem we saw in production.

Risks

  • Only one teammate understands the rollback path.

  • The launch estimate assumes an unconfirmed vendor limit.

  • Support capacity has not been planned for the migration week.

Team and morale

  • The incident handoff left one person carrying decisions alone.

  • People challenged the design safely during the written review.

  • The repeated priority changes made completed work feel disposable.

Action items

  • Dependency clarity: For two sprints, Ana adds an owner check to high-risk refinement; review returned stories next retro.

  • Review flow: Sam creates a backup reviewer rotation by Friday; track pull requests waiting over one day.

  • Release safety: Mina runs a production-volume test before launch approval and posts the result on the release card.

From vague card to useful evidence

A useful card names what happened and why it mattered. These rewrites give the team something concrete to discuss.

Vague card Useful evidence
CommunicationThe release decision changed in a private chat and reached support after customers did.
Planning was badTwo stories were returned because the payment dependency was missing from refinement.
More testingThe staging dataset did not include the volume that triggered the production timeout.

Frequently asked questions

What is an example of a good retrospective card?

“The product demo exposed missing acceptance criteria before development began” is useful because it describes an event and its effect.

What is an example of a retrospective action item?

“For the next two sprints, Priya adds a dependency check to refinement and tracks stories returned for missing dependencies” has an owner, duration, behavior, and signal.

How do you improve a vague retro card?

Ask what happened, when it happened, what effect it had, and whether the writer can name a representative example.

Should every retrospective card become an action?

No. Group cards into themes, prioritize, and select one or two actions with the best expected impact and feasible ownership.

Turn the next retro into a working session.

Choose a focused template, invite the team, collect feedback, vote, and leave with an owned next step.