Post Mortem Retro

A reflective format for looking back on a finished project or major milestone. The team gathers what it liked, what it missed, what individuals learned and what to do differently next time, closing with appreciations. The wider lens makes it ideal for drawing lasting lessons rather than tweaking the last sprint.

What we liked

What held up under pressure and should stay

Roman

Rollback worked exactly as documented

Maria

The incident channel kept everyone out of each other's way

What we missed

Gaps the incident exposed: alerts, docs, access

Anna

No alert on failed payments — a customer told us

Daria

The runbook pointed at a dashboard that no longer exists

What I learned

What each person now knows that they did not before

Maria

Learned the retry storm came from our own client, not traffic

Kirill

Learned two people had never run the rollback before

For next time

Follow-ups with an owner so the same failure is caught earlier

Daria

Add alerting on payment failure rate — Dana, this week

Roman

Rehearse a rollback every quarter with a different person

Appreciations

Credit for people who carried the incident

Kirill

Thanks to Sam for staying calm and narrating every step

Anna

Thanks to support for holding the line with customers

Try Template

What is the Post-Mortem retrospective?

A Post-Mortem reviews a completed project or a closed incident to learn from it. The goal is not blame but understanding: what really happened, why, and how to do better next time. A structured, blameless format helps the team capture honest lessons instead of repeating the same mistakes.

What we liked — what worked well
What we missed — gaps and shortfalls
What I learned — personal takeaways
For next time — changes to apply
Appreciations — thanks to teammates

What we liked

The team records what genuinely worked: good decisions, smooth handling, effective collaboration. These are the practices worth keeping and repeating in future work.

What we missed

Here people name gaps, mistakes and things that fell through the cracks. Stated factually, these become learning material rather than a search for someone to blame.

What I learned

This column captures personal insights — skills gained, assumptions broken, lessons that will change how each person works going forward.

For next time

For next time turns reflection into intent: concrete changes the team commits to applying in the next project or to prevent the next incident.

Appreciations

Appreciations closes the review on recognition — thanking people for effort, support and steady work, especially valuable after a hard project or stressful incident.

Benefits of the Post-Mortem retrospective

Turns finished work into durable lessons
Keeps the review blameless and psychologically safe
Captures both team and personal learning
Converts hindsight into concrete next steps
Prevents the same mistakes from recurring
Ends on appreciation, even after tough incidents

How to run a Post-Mortem retrospective

Create a board in QRetro from the Post-Mortem template.
Set a blameless tone focused on learning, not fault.
Have everyone add cards across all five columns.
Discuss the key themes column by column.
Agree on the most important changes for next time.
Assign owners and due dates to those action items.

Similar templates

Other formats teams pair with this one — open any of them as a board in one click.

Rose Bud Thorn

A gentle, well-balanced format that gives equal weight to the good, the painful and the promising. The rose marks what went well, the thorn what hurt or got in the way, and the bud what shows potential and is worth nurturing. Including the bud keeps the conversation forward-looking instead of dwelling only on the past.

Hopes and Fears

A forward-looking format best used at the start of a project, quarter or initiative. The team shares its hopes for what could go right alongside its fears about what might go wrong. Naming both early builds shared understanding and surfaces risks while there's still time to act on them.

Good Bad Better Best

A four-column format that turns reflection into a ladder of improvement. The team names what was good and what was bad, then pushes further to what could be better and recognizes the very best results, performances and people. Ending on the high note of best keeps the energy positive and celebrates standout contributions.

Likes / Wishes / Wonders

A concise, exploratory format that blends feedback with curiosity. Participants share what they liked, what they wish were different and what they wonder about going forward. The wonders column invites open questions and fresh ideas, making it a great fit for teams exploring new ways of working.

OKR Template

A goal-focused format that ties reflection to objectives and key results. The team reviews its objectives, examines the key results that measure progress and aligns on the initiatives that will drive them forward. It's a strong choice for connecting day-to-day retrospectives with the bigger goals the team is accountable for.

Retrospective Template: WWW

A nuanced take on the classic what-went-well format that adds a middle ground. Instead of a strict worked-or-didn't split, the team also captures what kinda worked — the partial successes and half-measures. That extra shade often holds the most useful insights, where small adjustments can turn a near-miss into a win.

Try Template