Retrospective Questions: 60 Prompts That Get Real Conversations

"What went well?" produces a list of things that went well.

"What's one moment from this Sprint where you felt the team was at its best — and what made that possible?" produces a conversation about what specifically creates high performance and how to replicate it.

The question determines the depth of the answer. Most retrospective formats use the same four or five prompts in rotation, which produces familiar, predictable, increasingly shallow responses. The team learns what kind of answer is expected and provides it.

Better questions disrupt the expected pattern. They require more thought, generate more authentic responses, and — crucially — produce more actionable insights.

Here are 60 retrospective questions organised by what you're trying to accomplish. Use them to replace tired prompts, deepen specific phases, or unlock stuck conversations.

Check-In Questions (Set the Stage)

The check-in question is the first thing people say in the retrospective. It sets the tone, signals what kind of session this will be, and gives the facilitator data about the room's current state.

For psychological safety:

1. On a scale of 1–10, how comfortable would you be raising a significant concern in this retro? (Don't answer out loud — write it on a sticky note.)
2. What's one thing that's been on your mind about the team that you haven't said yet?
3. What word describes how you're showing up to this retrospective today?

For energy and mood: 4. What's your weather today? (Sunny, cloudy, stormy, foggy) 5. What's one thing outside of work that's affecting your energy right now? (No obligation to share personal details.) 6. If this Sprint were a movie, what genre would it be?

For reflection tone: 7. What's one thing you're proud of from this Sprint? 8. What's one thing you're still carrying from this Sprint that you'd like to put down? 9. Finish this sentence: "This Sprint felt like..."

For long-running teams: 10. What's changed about how you work in the past three months — good or bad? 11. What's something this team does better than any other team you've been on?

Data Gathering Questions (Gather Data Phase)

These prompts are for the phase where the team builds a shared picture of what happened. The goal is factual and experiential data — not yet interpretation.

Beyond "what went well": 12. What's one thing that happened this Sprint that you want to make sure we keep doing? 13. What moment from this Sprint would you want to show a new team member as an example of how we work at our best? 14. What's one decision from this Sprint that, in retrospect, you feel good about? 15. What unblocked the most value this Sprint?

Beyond "what could be improved": 16. What's the thing that cost us the most time this Sprint? 17. What's the thing nobody talks about that slows us down every Sprint? 18. What did we say we would do this Sprint that we didn't? (Not blaming — mapping reality.) 19. If you could replay one moment from this Sprint and handle it differently, what would it be? 20. What assumption turned out to be wrong this Sprint? 21. What did you have to work around rather than through? 22. What's the thing you'd fix first if you had one uninterrupted week to do it?

For emotional data: 23. What was your peak energy moment this Sprint? What was your lowest? 24. When did you feel most useful to the team this Sprint? 25. Was there a moment when you felt like your contribution wasn't valued? (Anonymous input works better for this one.) 26. How connected do you feel to the team's goal right now, on a 1–10 scale?

For process data: 27. What meetings from this Sprint were worth it? Which weren't? 28. What information did you need that you didn't have? 29. What work felt like flow? What felt like friction? 30. Where in the Sprint did we lose momentum?

Insight Generation Questions (Generate Insights Phase)

These prompts move from what happened to why it happened. This is the most intellectually demanding phase and the one most often rushed.

Root cause prompts: 31. Why do you think this keeps happening, Sprint after Sprint? 32. What would have to be true for this problem to disappear? 33. If a new team member did what we did this Sprint, what would we tell them to do differently? 34. What's the structural reason this happens — not the individual reason? 35. If you had to bet on whether this issue will appear in the next retro, what would your bet be?

Systems thinking prompts: 36. Who outside our team is affected by this pattern? Who outside our team is causing it? 37. What incentive in our system is maintaining this behaviour even when we agree it's a problem? 38. What's the difference between how we say we work and how we actually work? 39. What's the constraint that, if removed, would make everything else easier? 40. What are we optimising for that we shouldn't be?

Perspective shift prompts: 41. What would a new team member notice about how we work that we've stopped noticing? 42. What would our users think if they could see how we worked this Sprint? 43. What would we need to believe about ourselves to think this pattern is okay? 44. In 6 months, what will we wish we'd addressed sooner?

For stuck conversations: 45. What's the thing everyone is thinking but nobody has said? 46. If you had to guess the most controversial opinion in this room about our process, what would it be? 47. What's the thing we've avoided discussing for three or more Sprints?

Action Decision Questions (Decide What to Do Phase)

These prompts help the team move from insight to concrete, owned, measurable decisions.

For sharper action items: 48. What specific behaviour would be different next Sprint if we solved this? 49. How would we know, by end of next Sprint, that this action item worked? 50. Who is the single person most responsible for this action? (Not "the team.") 51. What's the smallest possible change we could make that would have the biggest impact? 52. What would stop us from doing this action — and how do we prevent that?

For prioritisation: 53. If we could only do one thing differently next Sprint, what would have the most impact? 54. Which of these problems is within our control to fix? Which do we need to escalate? 55. What's the action item we've agreed to before but never done — and why is this time different?

Closing Questions (Close the Retrospective Phase)

For reflection on the session itself: 56. What's one thing about today's retrospective that worked well? 57. What would have made this retrospective more useful? 58. What's one thing you're taking from this session? 59. Did you say everything you wanted to say? (Important question — often people leave with things unsaid.) 60. What's your commitment heading into the next Sprint?

Using These Questions Effectively

Don't use more than 3–4 questions per phase. Too many questions creates cognitive overload and prevents depth. Pick the ones most relevant to where this specific team is right now.

Silent writing before verbal sharing. For almost any of these questions, 3–5 minutes of individual written reflection produces richer answers than immediate verbal discussion. This is especially true for emotionally charged questions.

Anonymous input for sensitive questions. Questions 2, 14, 25, 35, 45, 46, 47 — these are the high-value questions that surface what people won't say publicly. Run them through an anonymous tool when the psychological safety to say difficult things doesn't yet exist.

Rotate questions across Sprints. The same question asked repeatedly becomes a genre exercise — people know the kind of answer expected. New questions produce new thinking.

Let the question do the work. Resist the urge to explain or re-word questions after asking them. A question that generates silence is often the most interesting one. Wait it out.

The most common mistake in retrospective facilitation is asking questions and then filling the silence before the team has answered. The better answers take a moment to arrive. Make space for them.