Retrospective questions for quiet teams: 15 prompts to try

Silence in a retrospective can mean several things. People may need time to think, feel the prompt is too broad, prefer writing or doubt that the meeting will change anything. It can also mean they are uncomfortable discussing a topic in this group. Do not assume a quiet teammate has nothing to contribute.

Explain what you want to learn and give everyone a few minutes to write before speaking. Offer a pass when inviting comments. If someone raises a sensitive concern, agree an appropriate follow-up instead of asking them to disclose more detail on a shared board.

Choose one or two of these prompts and name a recent period of work. Asking about an event gives people something concrete to recall. You can leave the questions on the board before the meeting so the fastest speaker does not set the whole agenda.

1. When did you have the information you needed at exactly the right moment?
2. Which task took more waiting than working this week?
3. What was one decision you had to ask someone to explain?
4. When did a teammate make a difficult piece of work easier?
5. What surprised you after we thought a task was finished?

Keep the discussion about working practices rather than asking people to rate each other. For example, a missed handover can lead to a useful conversation about timing and context without turning the board into a list of personal complaints.

6. Where did a handover leave you guessing about the next step?
7. Which meeting helped you make a decision, and what made it useful?
8. When was it difficult to ask for help?
9. What did we explain well to someone joining the work?
10. Which useful contribution might otherwise go unnoticed?

Use these after the group understands an example. Asking for solutions too early can produce a familiar list of fixes without showing whether they address what happened.

11. What information would have made that moment easier?
12. What is one part of this process we could simplify next week?
13. Which useful practice should we make easier to repeat?
14. What could we try once before deciding on a permanent change?
15. What would we need to see to know that the experiment helped?

Read written notes without immediately defending the existing process. Ask whether you have understood the example, then invite another perspective. An optional round gives each person an opening to speak; keeping the pass option makes it an invitation rather than a performance.

In Retro, private reflection separates note writing from the reveal. Explain that this is not anonymous feedback: shared notes retain authorship. Do not use it to promise confidentiality the board does not provide.

Finish by recording what the team will do with the feedback, including topics you cannot resolve today. Revisit the agreed action next time. If people have repeatedly raised the same issue without a response, address that history rather than relying on a new question format.