Log in
← All posts

30 Anonymous Questions for Your Team's Next Retro

6 min read

Good anonymous team retro questions are specific, cover both wins and problems, and ask about the work rather than individual people. Below are 30 of them, grouped into what went well, what didn't, process, communication and morale. Pick three to five per retro, collect answers anonymously before the meeting, and spend the meeting deciding what to change.

Why run an anonymous retro?

Retrospectives only work if people say what actually happened. In a live meeting, that's hard. The newest person won't contradict the lead. Nobody wants to be the one who brings up the deadline everyone quietly missed. And the loudest people end up setting the agenda.

Collecting answers anonymously first helps with all of that:

  • Quieter people get an equal voice. Everyone writes, not just those who speak up fastest.
  • Hard topics come up earlier. It's easier to write "the handoff to QA keeps breaking" than to say it in front of the person who owns it.
  • The meeting gets shorter and better. You start with the answers already in, so you can spend the time discussing them.
  • The focus stays on the work. Without names attached, people react to the point, not to who made it.

Anonymity is a tool, not a cure. It works best on a team that already wants to improve, with a facilitator who treats every answer seriously. For more on why people hold back and how to make honesty feel safe, see how to get honest feedback when people are too nice to tell you.

Anonymous team retro questions: what went well

Start here. It sets a constructive tone and tells you what to protect.

  1. What's one thing we did this sprint that we should keep doing?
  2. Who or what made your work easier this time? (Describe the help, no need to name anyone.)
  3. What went better than you expected?
  4. What's a small win that didn't get enough credit?
  5. Which decision this sprint turned out to be the right one?
  6. What did you learn that the rest of the team should know?

What didn't go well

Ask these plainly. The point is to find problems early, not to find someone to blame.

  1. What slowed you down the most?
  2. What's one thing that went wrong that nobody has talked about yet?
  3. Where did we lose time to rework or misunderstandings?
  4. What did you have to work around instead of fixing?
  5. Was there a moment you felt stuck and didn't ask for help? What stopped you?
  6. If we could redo one thing from this sprint, what should it be?

Process

These are about how work moves through the team: planning, estimates, reviews, handoffs and tools.

  1. Did our planning match what actually happened? Where did it drift?
  2. Which meeting would you shorten, change or cancel?
  3. Where does work tend to wait the longest before someone picks it up?
  4. Is there a step in our process that no longer earns its place?
  5. Are our priorities clear enough that you know what to work on next?
  6. What's one tool or workflow change that would save you time every week?

Communication

Good communication is hard to see when it works and easy to feel when it doesn't.

  1. Did you have the information you needed, when you needed it?
  2. Where did a message get lost, misunderstood or arrive too late?
  3. Do you feel comfortable disagreeing in our meetings? If not, what would help?
  4. Are decisions explained well enough that you understand the reasons?
  5. Is there someone outside the team we should be talking to more?
  6. Is there anything you think the team or its leads should know but doesn't?

Morale

These questions are more personal, which is exactly why anonymity matters here. Keep them optional.

  1. How would you describe your energy at work this sprint, in one word?
  2. Did your workload feel manageable? If not, what made it too much?
  3. What's one thing that would make this team a better place to work?
  4. Do you feel your work is recognized? What would good recognition look like for you?
  5. Is there anything making you less excited about this work lately?
  6. What's one thing you'd like to try or learn next sprint?

Tips for running an anonymous retro

Pick three to five questions, not all thirty

Fewer questions get longer, better answers. A good mix is one "went well," one "didn't go well" and one or two from process, communication or morale. Rotate them so the retro doesn't go stale.

Collect answers before the meeting

Send the questions a day or two ahead and give people time to think. Answers written calmly after the fact are usually more useful than ones blurted out in the room.

Set expectations clearly

Tell the team what will happen with their answers: who will read them, whether they'll be shared with the group, and that you're looking for problems to fix, not people to blame. A short line like "Be honest, be kind" sets the tone.

Don't play detective

The fastest way to end honest retros is to try to work out who wrote what. Treat every answer as coming from the team. If you're the lead, say this out loud.

Read the answers together

Group similar answers into themes before the meeting, then share the themes with the team. Talk about the patterns, not individual comments.

Keep personal issues out of the retro

If an answer is about one person's behavior, don't discuss it in front of the group. Handle it privately and carefully. Retros are for the team's work.

How to act on the answers

A retro is only as useful as what changes afterward.

  1. Group answers into themes. Look for what several people mentioned.
  2. Pick one to three actions. Fewer, smaller changes are more likely to happen.
  3. Give each action an owner and a date. "Someone should fix the build" won't get done. "Sam will try a shorter build check by Friday" will.
  4. Say what you won't do, and why. People notice when their answers disappear. A short "We heard this, but we're not changing it yet because..." keeps trust.
  5. Start the next retro by reviewing last time's actions. It shows answers lead to change, and that makes people more honest the next time.

Run your next retro with one Frankly link

You can collect anonymous answers for a whole retro with a single Frankly post:

  1. Create a post titled with your sprint or project, like "Retro: Sprint 14."
  2. Paste your three to five questions into the post.
  3. Share the one link in your team channel. Only people with the link can open the post.
  4. Teammates leave notes, each one under a random name like Quiet Otter. You see what was said, never who said it.
  5. Bring the themes to your retro meeting.

Create one Frankly link and share it with your team.

If you're also looking for questions to help someone grow outside of work, try these 50 questions to ask friends for honest feedback.