Skip to content
Convergo360

How to run a 360 feedback debrief

Hold the 360 debrief within two weeks of release, run by a coach or the person's manager, then agree a development plan with 2 or 3 focus areas in 30 days.

· 8 min read · Convergo360 team

A 360 feedback debrief is a private 60 to 90 minute conversation in which a coach or the person's own manager helps them read their report and decide what to work on. Hold it within two weeks of the report being released. Close the process by agreeing a written development plan with two or three focus areas within 30 days.

The debrief is where a 360 turns into changed behaviour. Without it, the person reads the report alone and tends to dwell on the lowest score.

Who should run a 360 feedback debrief?

Either a coach or the manager can run it well:

Facilitator When it works best What to watch
External or internal coach Senior leaders, first 360 cycles, reports with large gaps or hard comments Agree up front what, if anything, the coach shares with the manager
The person's own manager Teams with an open working relationship and a manager who has read the report beforehand The person can hold back if they feel the conversation links to pay or ratings

Whoever runs it needs access to the full report before the session and enough time to prepare. In a well run cycle the report goes to the person rated and their coach through a secure sign-in link, never as an email attachment, so the facilitator is someone the person already knows will see it.

If the manager runs the debrief, keep it separate from the performance review conversation. Our guide on 360 feedback vs a performance review explains why the two work better apart.

When should the 360 debrief happen?

Schedule the debrief within two weeks of the report's release. People start forming their own story about the results from the moment they open the report. A long gap gives that story time to set, and it gets harder to shift in the session.

Two timing habits help:

  1. Book the debrief before reports are released, so the date is already in both diaries.
  2. Tell the person when the report will arrive and suggest they read it once, then put it down until the session.

How do you prepare for a 360 debrief?

The facilitator should spend 45 to 60 minutes with the report beforehand. Use this checklist:

  1. Check the response summary. Note how many people responded in each group (Manager, Peers, Direct Reports, Other Staff) and whether any group is too small to show separately.
  2. Read the competency summary and note which areas sit in each colour band.
  3. List every gap of 0.5 or more between Self and All Others, in both directions.
  4. Read the top 5 and bottom 5 behaviours.
  5. Read every written comment and group them into two or three themes.
  6. Pick one or two questions to open the session with, such as "What stood out when you read it?"

Ask the person to prepare too. Two questions are enough. What surprised you? Which result would you most like to understand better?

What does a good 360 debrief agenda look like?

This agenda fits a 90 minute session. For 60 minutes, shorten the comments and plan steps and book a 30 minute follow up.

Time Step What happens
0 to 5 min Open Confirm the session is confidential and the purpose is development. Explain the agenda.
5 to 15 min First reactions The person says what they noticed, liked and found hard. The facilitator listens.
15 to 30 min Overall picture Walk through the response summary and competency summary. Look at where most scores sit.
30 to 45 min Self vs others Go through blind spots and hidden strengths with a gap of 0.5 or more.
45 to 60 min Top 5 and bottom 5 Look at the highest and lowest rated behaviours and link them to examples from work.
60 to 75 min Comments Read the comments by theme. Look for patterns that match the scores.
75 to 90 min Focus areas Choose two or three areas to work on. Set the date for the written plan.

How do you read a 360 feedback report?

Read the report from the broad picture down to the detail. Starting with the lowest score pulls the whole conversation towards it. You can see the full layout in our sample report.

Start with who responded

The response summary shows how many people in each rater group gave feedback. A view from 1 manager and 6 direct reports carries different weight from a view based on 2 peers. Anonymity rules mean small groups are combined or hidden, and the anonymity page explains how that works.

Use the colour bands

Scores run from 1 (Rarely) to 5 (Almost always), with "Not observed" left out of averages. The colour coding groups results into three bands:

Band Meaning in the debrief
4.0 and above Behaviours others see often. Good material for strengths to keep using.
3.0 to 3.9 Seen some of the time. Often where the most useful development sits.
Below 3.0 Rated lower by others. Worth exploring with examples before deciding what to do.

Compare Self with All Others

The gap is the Self score minus the All Others average, where All Others combines Manager, Peers and Direct Reports. The report lists any statement where the gap is 0.5 or more either way.

  • Positive gap (possible blind spot). The person rated themselves higher than others did. Example, Self 4.5 and All Others 3.8 gives a gap of 0.7.
  • Negative gap (hidden strength). Others rated the person higher than they rated themselves. Example, Self 3.2 and All Others 4.1 gives a gap of minus 0.9.

Hidden strengths deserve as much time as blind spots. Many leaders undervalue something their team relies on, and naming it gives them a strength to build on.

Look at the top 5 and bottom 5

The top 5 and bottom 5 behaviours give a short list to discuss. Ask for a recent example of each. The bottom 5 always contains five items, even when every score is above 4.0, so read them alongside the colour band before treating them as development areas.

Read comments for themes

Comments are listed alphabetically within each rater group, so they do not appear in the order people submitted them. Look for ideas that repeat across two or more comments or groups and match the scores.

How do you handle defensiveness in a 360 debrief?

Most people feel some sting when they read how others see them. That reaction is normal and it usually passes within the session if the facilitator gives it room.

Try these approaches:

  1. Let the first reaction run. Ask "What's your reaction to that?" and listen without correcting.
  2. Separate data from intent. The person can mean well and still be seen differently. "Your intent was to give the team space. Some of them read it as distance."
  3. Ask for examples. "When might someone have seen you do that?" moves the talk from the score to behaviour.
  4. Point to the pattern. If peers and direct reports show the same result, say so. Agreement across groups is hard to dismiss.

If the person becomes distressed, stop the agenda and book a second session for the plan.

What should you avoid in a 360 debrief?

The most damaging habit is trying to work out who said what. Guessing at authors breaks the promise made to raters, and people who suspect they've been identified give blander feedback next time. Our article on 360 feedback anonymity covers why this protection matters.

Habit to avoid What to do instead
Guessing who wrote a comment or gave a score Talk about themes across groups
Working through all 21 statements one by one Focus on gaps, the top 5 and bottom 5, and comment themes
Comparing the person with colleagues Compare the person's Self view with how others see them
Linking results to pay or ratings Keep the debrief for development only
Agreeing ten action points on the day Choose two or three focus areas and write the plan later
Using harsh labels for lower scores Say "rated lower by others" and ask for examples

If a comment raises a serious concern such as harassment, follow the process agreed for the cycle. The independent administrator reviews comments before reports are generated and escalates serious ones, before the report reaches the debrief.

How do you turn a 360 report into a development plan?

Agree a written development plan within 30 days of the debrief. Limit it to two or three focus areas. More than three spreads effort thin, and the people who gave feedback won't notice a change.

A good focus area usually combines one hidden strength or high scoring behaviour to use more, and one or two behaviours rated lower by others or flagged as blind spots.

For each focus area, write down:

Field Example
Behaviour Listens actively before responding
Why it matters Direct reports rated it 3.1 and Self 4.2, a gap of 1.1
What to try In one-on-ones, ask two questions before giving a view. Summarise what you heard before deciding.
Who will notice Direct reports and peers in weekly meetings
Support Monthly check-in with coach, short reading on listening skills
Review date 90 days after the plan is agreed

The report includes a development plan page, so the person can work from the same document they were debriefed on. Ask them to share the focus areas with their team. Saying "I'm working on listening before I respond" invites people to notice the change and gives them a reason to keep giving feedback.

Book a short check-in at 90 days and plan the next 360 for 12 to 18 months later, so the person can see whether others notice a shift. For the wider process, see our guide to 360 feedback in South Africa.

Next step

Book debrief dates for each leader before reports are released, and send the facilitators the preparation checklist above. To see how reports reach the person and their coach in Convergo360, read how it works.

Common questions

Who should run a 360 feedback debrief?

A trained coach or the person's own manager. A coach suits senior leaders and first cycles, while a manager who has been briefed on the report works well when the relationship is open and trusting.

How long should a 360 debrief take?

Plan for 60 to 90 minutes in one sitting. That gives time to read the overall picture, look at gaps between self and others, and choose two or three focus areas.

How soon after the report is released should the debrief happen?

Within two weeks. Book the date before the report is released so the person is not left alone with the results for long.

What is a blind spot in a 360 report?

A behaviour where the person rated themselves at least 0.5 higher than the average of everyone else. A hidden strength is the opposite, where others rate the person at least 0.5 higher than they rated themselves.

Should the person try to work out who wrote a comment?

No. Guessing who said what damages trust and makes raters less candid next time. Focus on the themes that appear across several comments and groups.

See a sample report and how a cycle runs

A 30-minute walkthrough with someone who has run 360s before.

Book a demo