Team Reflection Questions: 40 Prompts for Better Retros

The best team reflection questions are short, open and about the work, not the people: What was supposed to happen? What actually happened? What worked, what didn't, and why? What will we do differently next time? Below you will find 40 prompts grouped by what you want to learn, a way to run the conversation so people answer honestly, and a method for turning answers into actions that survive the next busy week.

TL;DR

• Start with the simple core: what was planned, what happened, what worked, what didn't, and what you would change.
• Pick one theme per session (results, communication, workload or a hard moment) and use five to eight questions, not forty.
• Collect answers individually and anonymously first, then discuss themes together, focusing on what happened and why, not who did it.
• End every session with specific actions: an owner, a timeline and a way to check it got done.
• Reflection works only when people feel safe to speak, so the manager's job is to set the structure and then step back.

Table of Contents

• What team reflection questions are for
• Choose the right moment and the right format
• Questions to review what went well and what didn't
• Questions about communication, collaboration and decisions
• Questions about workload, stress and burnout
• Questions to capture lessons from a project
• Questions for a difficult situation
• How to run the session so people tell the truth
• A 45-minute agenda you can use this week
• Turn answers into actions
• Our perspective
• Make reflection part of a reset
• FAQ
• Sources

What team reflection questions are for

Team reflection questions are prompts that get a group to look back at its goals, processes or outcomes on purpose. Researchers call this practice team reflexivity. Harvard Business School's review of the research describes it as an information-processing and self-regulatory activity that helps teams spot problems, solve them, learn and improve performance.

In plain terms: a team that never pauses to look at how it works repeats the same friction every quarter. A team that pauses for 45 minutes after a launch, a busy season or a rough patch can fix the handoff that kept slipping, rebalance work that was quietly unsustainable, and keep the habits that made the good weeks good.

You may know these sessions as retros, retrospectives, after-action reviews, debriefs or lessons learned. The names differ, the questions overlap, and the questions below work for all of them.

Choose the right moment and the right format

Reflect at natural endpoints: the end of a project, a sprint, a quarter, a major client deadline, a reorganization or a year. Also reflect after something goes wrong, while memories are fresh, but give emotions a day or two to settle first.

Three simple formats cover most needs:

The plan-versus-reality sequence comes from the after-action review method. Better Evaluation's guide lists its core prompts: what was supposed to happen, what actually happened, what the differences were, what worked, what didn't, why, and what you would do differently next time. Those steps build a shared understanding, examine successes and failures and their causes, and lead to specific, achievable, future-oriented recommendations.

The Stop/Start/Keep and Plus/Delta formats are described in Atlassian's guide to team reflections. Plus/Delta asks which moments and tasks to continue and which items need to change. Stop/Start/Keep splits the conversation into things to stop doing, start doing and keep doing.

Questions to review what went well and what didn't

Start here if you only have time for one set. These prompts work for almost any team and any piece of work.

1. What were we trying to achieve?
2. What was our plan, and how did it change along the way?
3. What actually happened?
4. What went well, and why?
5. What could have gone better, and why?
6. What are we doing well as a team right now?
7. What resources or support made our successes possible?
8. What challenges got in the way of our goals?
9. What would we do differently next time?
10. What two or three lessons would we want another team to know?

The "why" in questions 4 and 5 does the real work. "The launch was late" is an observation. "The launch was late because approvals sat in one person's inbox for a week" is something you can fix. The University of Wisconsin–Madison's retrospective guidance for teams recommends asking what the team does well, which resources or support enabled success and which challenges affected goal achievement, which maps to questions 6 to 8.

Questions about communication, collaboration and decisions

Most recurring team problems live in the seams: who knows what, who decides, who hands off to whom. These prompts expose them. Several are adapted from a retrospective template that covers collaboration, meetings and handovers.

11. Did collaboration within our team and with other teams work smoothly?
12. Were our meetings focused, or did they drift?
13. Were handovers clear, so the next person knew what to do?
14. Were blockers and risks raised and addressed quickly?
15. Were decisions documented, so we could find them later?
16. Did we understand the goal and the definition of success from the start?
17. Did scope change midstream, and did we talk about it openly?
18. Could people speak up about problems?
19. When we disagreed, was the conflict handled respectfully?
20. What one change would most improve how we communicate?

Questions 18 and 19 are really about trust. If your team goes quiet when you ask them, that is data too. Our psychological safety exercises for managers and HR give you scripts for building that trust before you run a retro, and our mindful communication exercises help teams practice listening in the room.

For a broader health check, a team health retrospective such as Vital Signs groups questions under energy and morale, collaboration and communication, trust and psychological safety, and clarity of goals, priorities and roles. Those four headings make a useful skeleton if you want a quarterly pulse instead of a project debrief.

Questions about workload, stress and burnout

This is the set most teams skip, and the one that matters most for teams running hot. Ask these only after you have established that the room is safe, and consider collecting answers anonymously.

21. Was our workload sustainable over this period?
22. Could people take breaks and time off without guilt?
23. Were stress levels manageable?
24. When things got tough, did we adjust scope or priorities, or did we just work longer?
25. What energized you in this stretch of work?
26. What drained you?
27. How could our teamwork improve so the load feels lighter?
28. How could leadership support the team better right now?

Questions 21 to 24 come from the workload section of a retrospective template. Questions 25 to 28 follow the structure of an employee engagement retrospective, which asks what energizes people, what drains them, how teamwork can improve and how leadership can help. That template also recommends anonymous input for sensitive feedback, and we agree: people will tell a survey tool what they won't tell their manager across a conference table.

A caution for managers. These questions describe work conditions, not medical states. If someone discloses that they are struggling beyond ordinary work stress, respond by listening, then point them to your employee assistance program, HR or their own health care provider rather than trying to diagnose or counsel them yourself.

If the answers show a team that is depleted, the fix is rarely a single session. Look at scope, deadlines and staffing first, then add recovery practices. Our resilience workshop agenda for HR walks through one way to structure that.

Questions to capture lessons from a project

Use these at the close of a project or a period of work, when the goal is to leave something useful behind for the next team.

29. What did we set out to achieve, and did we get there?
30. What surprised us?
31. Which decision would we make again, and which would we reverse?
32. What do we know now that we wish we had known at the start?
33. What is one key lesson you will apply to future teamwork?
34. What should we write down so the next team doesn't start from zero?
35. What next for us on this project, if anything?

The closing question about one lesson per person is recommended in the UW–Madison retrospective guide. It is a good habit because it makes everyone say something, including the quietest person on the call.

Questions for a difficult situation

When something went wrong, a missed deadline, a lost client or a tense exchange, general prompts can feel evasive. Atlassian's guide to team reflections suggests prompts that cover feelings, decision-making, causes, expectations, prevention, and what would have changed the outcome. Adapted:

36. How did you feel when it happened, and how do you feel now?
37. What decisions were made, and what information did we have at the time?
38. What caused it, as far as we can tell?
39. What did we expect to happen, and what did we need?
40. What could have prevented it, and what would we do to prevent it next time?

Notice that none of these ask "who." That is deliberate, and it leads to the part that decides whether any of this works.

How to run the session so people tell the truth

Good questions in a tense room produce polite silence. The structure around them matters as much as the wording.

Set the ground rules first

The World Health Organization's After Action Review facilitator manual says the discussion should focus on what happened and why, not on who did it. It treats the session as a learning exercise about events and contributing factors rather than an evaluation of individual blame. Say that out loud at the start, and then hold to it when someone slips into naming names.

The APQC explanation of after-action reviews adds the reason: honest reviews depend on psychological safety. People need to believe they can speak up and admit what they would do differently. If the last person who admitted a mistake was punished, no list of prompts will fix that.

Collect input individually, then discuss

The UW–Madison guidance suggests a sequence that works well in practice:

1. Collect individual input anonymously before the meeting.
2. Identify common themes and unique issues.
3. Agree on discussion norms: active listening, dialogue rather than debate, curiosity and respect.
4. Share the themes visibly, on a screen or a wall.
5. Discuss in small groups, then as a whole team.
6. Record actions and take a moment for appreciation.

The Overseas Development Institute's paper on after-action reviews makes the same point from another angle: collect individual input first when openness or time is a concern, then facilitate group discussion around the themes. It also recommends involving all team members, appointing a facilitator who creates an open environment, and using an uninvolved note-taker so the facilitator can focus on the room.

Facilitate, don't own the conversation

Managers should provide structure, but the team should fill it. Atlassian's guidance frames it this way: the manager facilitates rather than owns the conversation, leaving room for the team to reflect on its work. If you are the person whose decisions are under discussion, consider asking a peer or someone from another team to facilitate.

It also helps to understand what a group brings into the room. When people carry competing needs or unspoken tension, a surface-level retro can miss what is actually going on. This piece on facilitating competing needs and unspoken tension is a good companion for creating the conditions for candid, blame-free reflection.

Use the body, not just the whiteboard

People arrive at a retro straight from back-to-back calls, with shoulders tight and attention scattered. A one-minute settling practice at the start changes the quality of what follows. Try three slow breaths together, or one of the exercises in our 1-minute team mindfulness guide. If your team bristles at forced sharing, our meeting energizers that avoid the cringe are a gentler way in.

A 45-minute agenda you can use this week

Send the individual questions at least two days ahead, with five to eight prompts drawn from the lists above. More than that and the answers get thin.

Turn answers into actions

A retro that ends with "good discussion, everyone" has changed nothing. The WHO manual's advice is to turn themes into improvement activities with an implementation timeline, responsible people, the support needed and indicators for monitoring completion, and to make each action clear, specific and achievable.

The ODI paper illustrates why specificity matters: it contrasts a vague recommendation with a concrete action that names the contact, the information to obtain and the timing. Here is the same idea applied to a team:

• Vague: "Improve handovers."
• Specific: "Maya adds a handover checklist to the project template by Friday; we review whether it was used at the next sprint close."

Then close the loop. Open your next reflection by asking which actions from the last one were completed and what changed. Teams that skip this step teach people that reflection is theater.

Our perspective

We work with Dallas and North Texas teams that are good at the work and short on recovery. In our experience, the questions are rarely the weak point. The weak point is the state people are in when they answer them. A team that arrives wired and defensive gives defensive answers.

That is why we treat reflection as part of how a team operates, not a once-a-year exercise. A few minutes of breath, quiet or gentle movement before the conversation lowers the temperature enough for honest answers. Mr. Namaslay, who facilitates our programs, brings 30 years in fitness and hospitality, including a path from busser to restaurant manager and consultant. He has seen how pace and pressure show up in a team, and how quickly a room softens when people are given permission to pause.

Our advice: choose fewer questions, ask them in a calm setting, and be willing to act on what you hear, even when it points at workload or leadership. Questions without follow-through cost trust.

— Chris

Make reflection part of a reset

If you want your next retro, offsite or leadership gathering to start from a settled place, we design sessions for exactly that. DCFB Wellness offers facilitated group sessions, sound therapy, rhythm and focus practices, and alcohol-free social experiences, tailored to your team and the moment, whether that is the close of a hard quarter or a leadership event. Pricing is quoted per project, so get in touch about a corporate wellness session and tell us what your team has been through.

For events where a social element helps, Limitless Libations can add crafted mocktails as a complement to the experience, so everyone can join in regardless of whether they drink.

FAQ

How many reflection questions should I ask in one session?

Five to eight is plenty for a 45-minute session. Choose one theme, such as communication or workload, and go deep on each prompt by asking "why." Save the other sets for future sessions.

How often should a team reflect?

There is no single right rhythm, but tie it to natural endpoints: the close of a project or sprint, a quarter, and after any significant setback. Short Plus/Delta check-ins fit regular cycles, while longer plan-versus-reality reviews fit projects.

What if nobody answers honestly?

Switch to anonymous input before the meeting and share themes on a screen. Restate that the goal is understanding what happened, not assigning blame, and consider having a neutral facilitator lead. If silence persists, the issue is trust, which is worth tackling before the next retro.

What is the difference between a retro and an after-action review?

The two overlap heavily. A retrospective is common in software and project teams and often follows a fixed cadence. An after-action review is usually tied to a specific event and compares what was planned with what happened. Both end with lessons and next steps.

Can managers ask about burnout in a team retro?

Yes, if they frame it around work conditions such as workload, breaks and priorities, and offer anonymous input. Do not ask people to disclose health details. If someone raises a personal concern, direct them to HR, your employee assistance program or their health care provider.

Sources

• Team Reflexivity, Harvard Business School Faculty & Research
• After action review, Better Evaluation
• Retrospectives, UW–Madison Professional Development
• The benefits of team reflections and how to lead one
• Team retrospective questions template for sprints
• Vital Signs team health check template
• Employee engagement retrospective template
• After Action Review facilitator manual, World Health Organization
• Knowledge Sharing and Learning: After Action Reviews and Retrospects, ODI
• What Is an After-Action Review?, APQC

Recommended

• Team Connection Activities That Work: 15 Ideas and a Rollout Plan
• Mindful Communication Exercises for Work Teams
• Meeting Energizers: No Cringe or Forced Sharing for Managers
• Psychological Safety Exercises: 6 Scripts for Managers and HR