Skip to main content

Conversation Starters

Sprint Retrospective Questions Beyond "What Went Well"

The default sprint retro is a "what went well / what could be improved / action items" template that produces shallow surface-level discussion most weeks. The good retros — the ones that actually change how a team works — go past that template. They surface what was hard to talk about, name patterns no one had named yet, and produce action items that land.

The questions in this guide are designed to do exactly that. We have built sets for different retro contexts: standard sprint retros, post-incident or post-launch retros, quarterly retros, and the trickier "the team is in a bad chapter" retro. Each set produces real conversation and useful output.

There is also a section on the specific questions to use when the retro template stops working — when the team has been doing the same retro for so long that the answers have become rote. Most teams hit this wall after 6-12 months. The fix is not a new template; it is a different set of questions.

Workplace facilitation editors

The Samtalekort Editors

We design icebreakers, retro questions, and team-meeting prompts used inside engineering, design, and ops teams. Our work-focused decks are calibrated against feedback from facilitators running standups, retros, and offsites.

Published

What makes a great retro question

A great retro question surfaces things that are not surfacing in the default template. The strongest pattern: questions that name a specific pattern, ask for a small specific story, or invite reflection on the *how* of the team's work, not just the *what*. "What is one thing this team did this sprint that we should keep doing?" is a generic question. "What is one moment from this sprint where we made a decision faster than usual — and what made that possible?" is a specific question that produces real insight.

Try the deck

Retro questions to break out of the template

Pull one of these into your next retro instead of running the same "went well / improve" template. Each produces specific, actionable insight rather than generic surface-level discussion.

Open the colleague deck
  1. Card 1

    What is your favorite vacation destination and why?

  2. Card 2

    How can humor be used to break down barriers between colleagues without hurting anyone?

  3. Card 3

    What is the worst meeting you have been in — and why?

  4. Card 4

    How do you show empathy toward a colleague who's going through personal challenges?

  5. Card 5

    What usually puts you in a good mood when you are tired at work?

  6. Card 6

    How do you keep things balanced when a colleague is also a close friend outside of work?

  7. Card 7

    What song can you listen to over and over without getting tired of it?

  8. Card 8

    How would you react if you discovered a colleague doing something unethical at work?

  9. Card 9

    What is the best gift you have ever received?

Want the full deck? Play 200+ more for free →

Sprint retro questions beyond the default template

  1. What is one decision we made this sprint that I would make differently in retrospect?
  2. What is one moment this sprint where we made a decision faster than usual — and what made that possible?
  3. What is one thing we struggled with this sprint that we have struggled with for multiple sprints?
  4. What is one piece of work this sprint that we are most proud of, even if it did not ship?
  5. What is one assumption we are making about how we work that maybe deserves to be re-examined?
  6. What is something this sprint that worked because of a person, not a process?
  7. What is something this sprint that broke because of a process, not a person?

Post-incident or post-launch retro questions

For specific event retros — incidents, big launches, big failures. Calibrated for that specific energy.

  1. What is one moment in this incident or launch where the team performed better than expected?
  2. What is one moment where we made a decision under pressure that we should formalize as a process?
  3. What is one signal we missed earlier that we should have noticed?
  4. What is something the team handled well that nobody outside the team will see?
  5. What is one thing about how we communicated during this event that we should keep doing?

Quarterly retro questions

For the longer quarterly retros where the team has time to reflect on patterns rather than events.

  1. What is one pattern in our work this quarter that I had not consciously noticed?
  2. What is something we have been doing for the entire quarter that has stopped serving us?
  3. What is one thing that worked well this quarter that we should formalize?
  4. What is one thing we said we would do this quarter and did not — and is it still worth doing?
  5. What is one thing about this team that has changed this quarter, in any direction?

Retro questions for teams in a hard chapter

For when the team is genuinely struggling — burnout, conflict, after losses, or in a tough product moment. Calibrated to be useful without being heavier than the moment can hold.

  1. What is one thing this team is still doing well, even now?
  2. What is one thing each of us has done recently that supported a teammate?
  3. What is one piece of work this past sprint that you are personally proud of?
  4. What is one thing leadership could do that would actually help us right now?
  5. What is one small change we could make that would meaningfully reduce friction in our week?

How to run retros that actually change how the team works

  1. 1

    Rotate the format.

    Same template every retro for six months produces increasingly rote answers. Rotate between the standard template, focused-question retros (one specific question), pattern-spotting retros (looking across the last 4 sprints), and reflective retros (asking about how the team works, not what it shipped).

  2. 2

    Anonymize when needed.

    For retros where psychological safety is the bottleneck, anonymous input via a shared doc or polling tool can produce dramatically more honest answers than open round-robin. Use sparingly — full anonymity all the time prevents the team from learning to be honest in person.

  3. 3

    End with one concrete change.

    Every retro should produce one specific, owned, time-boxed change. "We will try X for the next sprint, owned by Y" beats "we should communicate better." Without this discipline, retros become group venting.

  4. 4

    Hold the action items accountable.

    Reference last retro's action items at the start of this retro. Without this, retros produce action items that are forgotten by Monday. The simple act of starting with "did we do what we said?" transforms retro culture.

  5. 5

    Time-box the venting.

    Some retros need 10 minutes of pure venting before useful conversation can happen. That is fine — but bound it. After 10 minutes, the facilitator should redirect to specific questions.

  6. 6

    Use specific questions, not abstract ones.

    "What went well" produces generic answers. "What is one moment this sprint where we made a decision faster than usual" produces useful insight. Specific questions outperform open ones in retros consistently.

  7. 7

    Have the facilitator answer first.

    For deeper retro questions, the facilitator answering first sets the depth. A polished facilitator answer caps the team's honesty.

Common pitfalls to avoid

  • The retro becoming a complaint dump.

    Without structure, retros can become unproductive group venting. Time-boxing the complaint phase and pivoting deliberately to action items keeps the retro useful.

  • Action items that no one owns.

    "We should improve communication" is not an action item. "Sara will draft a one-page communication norm doc by Friday" is. Without ownership, retro decisions evaporate.

  • Skipping retros when busy.

    Busy weeks are when retros matter most. Cancelling them when stakes are highest is the move that lets bad patterns calcify into team culture.

Try the deck

For the quarterly retro that needs to go deeper

Bigger questions for the longer retros where the team has time and intention to reflect on bigger patterns. Save these for the once-a-quarter retro, not the weekly.

Open full deck
  1. Card 1

    Is it better to have loved and lost than never to have loved at all? Does that apply to everything in life?

  2. Card 2

    When did you last lie to protect someone — was it right?

  3. Card 3

    What do existentialists say about the fear of the absurd, and can meaninglessness be a driving force?

  4. Card 4

    If you could know exactly when you'll die, would you want to know?

  5. Card 5

    If you knew you would die tomorrow, what would you regret most not having said?

  6. Card 6

    How can minimalism, as a philosophical approach, challenge a materialistic society?

Want the full deck? Play 200+ more for free →

Frequently Asked Questions

What are good retrospective questions?

The best retro questions are specific rather than generic. "What is one moment this sprint where we made a decision faster than usual — and what made that possible?" produces more useful insight than "what went well." Specific questions force specific reflection, which produces specific changes.

How do I make retros less repetitive?

Rotate the format. The standard "went well / could be improved / action items" template gets rote after a few months. Try focused-question retros (one specific question), pattern-spotting retros (looking across multiple sprints), and reflective retros (about how the team works, not what it shipped).

How long should a retro be?

For weekly or biweekly sprint retros, 30-45 minutes is enough if the format is tight. For monthly or quarterly retros, 90 minutes lets the team reflect on bigger patterns. Anything longer becomes a meeting that wears out the team.

How do I run a retro for a team that is struggling?

Calibrate the questions to what the team can hold. Hard chapters need retros that surface what is still working as much as what is broken. Asking only about problems when the team is already overwhelmed produces despair, not improvement. The best questions for a struggling team mix problem-spotting with strength-spotting.

What action items should come out of a retro?

One specific, owned, time-boxed change per retro is the realistic target. More than that and the team cannot actually execute. The discipline of "one change per retro, follow up next retro" produces compound improvement over a year that sprawling retros do not.

How do I keep psychological safety high in retros?

Have the facilitator answer first when asking deeper questions, allow real passes, and follow up on what people share. The biggest psychological safety killer in retros is when someone shares something hard and it is met with silence or with rapid-fire problem-solving. Acknowledge what people share before moving on.

How do post-incident retros differ from sprint retros?

Post-incident retros need to be blameless — focused on systems and decisions, not people. They should also surface what worked under pressure, not just what failed. The questions for an incident retro lean toward "what made our response better than it could have been" alongside "what failed."

How do quarterly retros work?

Quarterly retros work best when they look at patterns across multiple sprints, not at any specific event. Specific questions about how the team has changed, what habits have crept in, and what assumptions might need revisiting work better than reviewing each sprint individually.

How do conversation cards help with retros?

They prevent the rote-template problem. Pulling one specific question from a deck for the start of each retro produces variety and depth that the same template cannot. Used selectively — once or twice a quarter — the deck approach refreshes the retro format without abandoning the structure.

What is the biggest mistake teams make in retros?

Producing action items that nobody owns and nobody follows up on. Retros that produce vague "we should communicate better" decisions become rituals without consequence. The discipline of one specific owned change per retro, followed up at the next retro, is the difference between retros that improve teams and retros that waste 45 minutes.

Try the decks

Jump straight into a relevant deck

Continue from the article and try the card decks that best match the topic.

Colleague

Get to know your colleagues better

Open deck

Philosophy

Reflect on life's big questions

Open deck

Related conversation starter pages

If this one was useful, these adjacent use cases probably are too.

Keep reading

Run retros that actually change how the team works

A small deck of work-tone questions in your facilitator notes refreshes retros that have gone stale. One specific question per session. The team starts noticing what it could not see before.

Open the colleague deck