Guide · Teams
How to run a team feedback debrief in 60 minutes
A team survey produces numbers. The debrief is where the numbers turn into two or three things the team agrees to do differently — and it is the part of the whole exercise the research actually supports. This is the agenda we ship with every run, block by block, with the reasoning behind each block and the three ways it most often goes wrong.
About a 9-minute read · Sources at the foot · Last reviewed
Why the debrief matters more than the numbers
Most people assume feedback helps. The measured record is less flattering. In the largest review of feedback interventions, Kluger and DeNisi (1996) found that in 38% of measured cases feedback made performance worse, not better — across 12,652 participants. Feedback that draws attention to the self rather than the task is the version most likely to backfire.
Debriefs are the counter-evidence. Tannenbaum and Cerasoli (2013) pooled 46 samples (2,136 participants) of teams and individuals who debriefed against those who did not, and found an effect of d = 0.67. Read as a probability, a team that debriefs has about a 2-in-3 chance of outperforming a comparable team that does not. The authors describe it as a 20–25% improvement; that figure is a percentile shift, not a gain in output, and we say so because the difference matters when you repeat it to your own team.
The rule that follows: never hand a team its scores and walk away. If you cannot run the conversation, do not run the survey.
Before the meeting: three decisions
- Who is in the room. Everyone who answered. A debrief run for a subset turns a team exercise into a report about absent people. If the team lead was rated, the lead is in the room as a member, not as the chair.
- Who chairs. Ideally not the person with the most authority. A named facilitator, a peer, or the lead with an explicit agreement to speak last on each block. The facilitator’s job is to hold the clock and the rules, not to interpret.
- What is on the table. Only the team pack — the group numbers, the agreement and spread, the network picture, and the agenda. Individual notes are never discussed in the room. In Facets they cannot be: nobody but the person can open theirs.
The 60-minute agenda
This is the agenda the product generates from a team’s own results. The minute counts are fixed; the content of each block is filled from the data.
| Minutes | Block | Purpose | Trap |
|---|---|---|---|
| 0–10 | How to read this | Set expectations about what the numbers are and are not | Skipping it, then arguing about methodology at minute 40 |
| 10–20 | What is working | Name up to three strengths, with their means | Rushing past it to get to the problems |
| 20–35 | Where there is most room to improve | Up to three scales, and the spread behind each | Treating the lowest mean as a verdict |
| 35–45 | Who we go to | The network picture: who people go to for help and second opinions | Turning central people into heroes and peripheral people into problems |
| 45–60 | Decide | Two commitments, each with an indicator | Leaving with a list instead of a decision |
0–10 · How to read this
Open with three sentences, and say them even if everyone has read the pack. These are the team’s own ratings of the team, averaged. Nobody’s individual answers are shown. The results are based on however many of you submitted — if that was nine of twelve, say nine of twelve, and say what the completion means for how much weight the numbers can carry. Then the sentence that does the most work in the hour: where members disagree, the pack says so, and those scales are a conversation, not a verdict.
10–20 · What is working
Start with strengths and spend the full ten minutes. This is not politeness. A team that hears its strengths named specifically — “Coordination and process: hand-offs go smoothly, and people agree that they do” — has something to protect when the harder blocks arrive, and the facilitator has a reference point for later: “we said we were good at this; is that still true in the situation we are describing?”
20–35 · Where there is most room to improve
The pack names up to three scales with the most room. For each, put the spread on the table before the mean. A scale with a low mean and tight agreement is a shared experience; a scale with a middling mean and wide spread is two groups having different experiences of the same team, and the useful question is what might explain the difference? rather than why is this low? Resist diagnosis. The instrument measures behavior and climate; it does not know why, and neither does the pack.
35–45 · Who we go to
The network picture shows who people say they go to for help and for a second opinion. Read it as load and access, not popularity. A person everyone goes to is carrying something; a person nobody goes to may be new, remote, or in a role that does not generate requests. The question for the room is whether the pattern matches how the team wants work to flow, and what one change would move it.
45–60 · Decide
The pack offers two decision slots, not six. Each is a sentence with an indicator: “We will start each planning meeting with a two-minute risk round. Indicator: risks raised before the deadline, not after.” Two is deliberate — a debrief that ends with a backlog ends with nothing. Write the two down, name who checks the indicator, and put a date six weeks out in the calendar before anyone leaves.
Three ways a debrief goes wrong
- It becomes a performance conversation. The moment someone says “so who rated us low on X”, the exercise is over. Say at minute 0 that individual answers are not in the room and cannot be reconstructed; in Facets, question-by-question detail does not exist below 5 raters, and individual peer scores are withheld entirely on a team of three, precisely so this question has no answer.
- The mean is treated as a truth. A 3.4 against a 3.9 between two groups of six is well inside the noise. Read the spread and the interval; the pack shows both.
- The chair explains. The person with the most context is the person most tempted to say why a number is what it is. Every explanation offered from the chair closes the conversation for the people who were going to offer a different one.
After the meeting: the six-week check
Fifteen minutes, six weeks later, three questions: did we do the two things; did the indicator move; do we keep, change, or drop each. Do not re-run the survey to answer it. Individual change is not measurable at team size, and a second run six weeks on measures noise. What Facets sends instead is a two-minute pulse: everyone says how far each recorded commitment has happened, and answers the same two questions about speaking up and workload the run asked, so the check-in starts from the team’s own answers rather than impressions. Run the survey again when the team has changed enough that the questions would get different answers — a new quarter, a new composition, a new mandate.
The private notes each person received are the other half of the loop, and they stay private — below 3 raters they do not exist at all. What a person does with theirs is theirs to decide; the self–peer gap is usually the place to start.
Frequently asked questions
How long should a team debrief be?
Who should run a team feedback debrief?
What if the results are bad?
Should individual feedback be discussed in the debrief?
How soon should we re-survey?
Sources and notes
Kluger, A. N., & DeNisi, A. (1996). The effects of feedback interventions on performance. Psychological Bulletin, 119(2), 254–284. · Tannenbaum, S. I., & Cerasoli, C. P. (2013). Do team and individual debriefs enhance performance? A meta-analysis. Human Factors, 55(1), 231–245.
The agenda structure is the one generated by the Facets team survey and is published on the instrument page; the evidence is discussed in full on the research page.
Run a team survey that ends in this meeting.
Three to twelve people, twenty minutes each, and a 60-minute agenda built from your own results — with the private notes nobody else can open.