Project post mortem questions: a retro on Regret and Pride

The project is over. It shipped late, or it shipped fine, or it was cancelled halfway and the team moved on the next Monday. You book a room for the post mortem, and the room fills with a list of what went wrong. This guide gives a PM two lenses for that meeting, Regret and Pride, and twelve project post mortem questions that ask about both. Each lens works with a word written on a whiteboard. If the team wants a lighter closing round, the free online table deals the cards.

Why a post mortem needs both sides

A review that covers only failures leaves out half of what the team knows. Ellis and Davidi ran after-event reviews with soldiers during a training course. One group was debriefed on its failures and its successes after each training day. The other group reviewed only its failures. The first group improved more. Before the reviews, people in both groups held a richer picture of what went wrong than of what went right, and that gap closed over later measurements (Ellis and Davidi 2005). A software team is a different setting from a training field, so read this as a lead. Still, the pattern can show up in a post mortem: the team can explain the outage, and nobody can say why the migration went smoothly.

Regret and Pride are a simple way to hold both sides. Regret collects what the team would change. Pride collects what the team would keep. Each one is a single word, so it fits on a sticky note and doesn’t need a template.

The Regret lens: count what nobody did

Regret can pull toward the loud mistakes first: the bad release, the missed estimate, the wrong vendor. Those belong in the review. A second kind is easier to miss. Gilovich and Medvec reviewed research on regret and describe a time pattern. Things people did cause more regret in the short term. Things people didn’t do cause more regret over the long run (Gilovich and Medvec 1995). A project post mortem happens in the short term, so the room may list actions first. Ask about the inactions on purpose: the risk someone noticed and didn’t raise, the user test that got skipped, the question nobody asked the client.

Regret
Lamp
Card 09: Regret / Lamp. Tap to turn it over.

Regret has Lamp on its back. On a project team, Regret can be read as the decision to cut testing, the week nobody pushed back on a deadline, or a hire that came too late. The Lamp side gives a gentler way in. Someone might talk about the late evenings at the desk with one lamp on. Someone else might use it as a picture of what the team couldn’t see until the end.

The Pride lens: name what to repeat

At work, Pride can sound like taking credit, so the answer shrinks to “it went okay.” The fix is to ask for the specific thing, not the feeling. “What are you proud of?” can get a shrug. “What did you do on this project that you’d do the same way next time?” is easier to answer. Ask the person to name the work and the reason it worked. That turns Pride into a list the next project can use.

Pride
Calculator
Card 02: Pride / Calculator. Tap to turn it over.

Pride has Calculator on its back. It suits a project team because pride at work can show up as numbers: the load time that dropped, the budget that held. The Calculator side lets someone talk about the estimate they got right, or about the quiet person who checked every figure in the plan.

Twelve project post mortem questions

The questions below are grouped in pairs, so each regret has a pride question next to it. Pick four to six for one session:

  1. What’s one decision you’d make differently if the project started tomorrow?
  2. What’s one decision you’d make the same way?
  3. What did we notice early and not act on?
  4. What did we act on early that saved us later?
  5. Which meeting, report or step could we drop next time?
  6. Which habit from this project should the next team copy?
  7. Where did a handoff between people or teams lose something?
  8. Where did someone help outside their role?
  9. What did we promise the client or users that we couldn’t keep?
  10. What did we deliver that nobody asked for and people used?
  11. What would you tell yourself on day one?
  12. What are you glad you’ll take into the next project?

A session in four parts

The order below puts Pride first, so the things to keep are on the board before the list of problems grows. Then comes Regret, then actions.

  1. Facts. Put the timeline on the board: start, key dates, end. No opinions yet.
  2. Pride. Each person answers one Pride question from the list. Write each answer down as a thing to repeat.
  3. Regret. Each person answers one Regret question. Include question 3, so the inactions get a turn.
  4. Actions. Pick two or three items from both lists and give each an owner and a place where the next project will see it.

Keep regrets about decisions and steps, not people. “We didn’t test on older phones” is a step. Naming who skipped it can move the room from the project to a person, and the next speaker may say less.

When the project was cancelled

A cancelled project needs a post mortem as much as a finished one. The team can feel that the work went nowhere. The Pride round matters most here. Ask what the team built or learned that still exists: code, research, a client relationship, a way of working. Then ask the Regret questions about the signals before the cancellation. What the team learns about those signals is useful for the next project, even if this one is closed.

A card round to close the project

After the actions are written down, a team may want a softer end. A short card round works for that. Draw a card, pick a side: the idea or the thing. Roll the die. Its six words are MEMORIES · BODY · PEOPLE · VALUES · CHILDHOOD · FUTURE, and the only instruction is “Look at the word from that side.” The rules say: “Say as much or as little as you like. The others ask, gently.” The rule card gives three short examples: What did that feel like? Who else was there? Has it always meant that to you?

At work, set the pass rule first. The rules put it plainly: “Before you start, decide together how passing works.” Agree that anyone can pass with no reason, and say it before the first turn. The rules also say: “What is said at the table stays there.” In a post mortem that line covers the card round, not the action list.

Success
Notebook
Card 17: Success / Notebook. Tap to turn it over.

Success has Notebook on its back. It fits the end of a project because the team can talk about what success meant, which can differ from the goal in the plan. The Notebook side opens the practical version: the notes someone kept from day one, or the page of lessons nobody reread.

Roll the die

To finish, the rules suggest a last round: “each player names one thing they discovered about someone today.”

Before you book the room

Write the two words, Regret and Pride, at the top of the invite, and pick your four to six questions from the list. The cards above have their own pages: Regret, Pride and Success. For a shorter round at the end of a regular meeting, see check-out questions for meetings. For more on running it at work, see Thesis for teams and classes. For the studies behind the deck, see the research page. See the rules and the box.