In this article
- Read 360 feedback in two passes
- Translate a label into an observable behaviour
- A hypothetical report review
- Share a useful commitment with the right people
- Choose one experiment with a review point
- Handle painful or questionable comments carefully
- Keep the report connected to everyday practice
- Separate development from administrative decisions
Harvard Business Review recommends dialogue after a 360 review. The steps here provide a practical preparation method; they do not interpret a particular assessment instrument or replace a qualified facilitator.
Read 360 feedback in two passes
On the first pass, understand the structure: who was eligible to respond, which dimensions were assessed and how the report handles anonymity. Do not begin by ranking the harshest comments.
CCL's 360-degree feedback paper distinguishes anonymous groups from named supervisor ratings. Check your instrument rather than assuming every response is anonymous.
On the second pass, look for repeated themes, differences between groups and examples that help explain a rating. A single comment can be useful, but it should not automatically outweigh the broader evidence.
Where the instrument includes norms or technical scoring, ask the facilitator how to interpret them. Avoid treating a small numerical difference as meaningful without understanding the method.
Record questions separately from conclusions. “Why do peers rate communication differently?” is a question. “My peers do not appreciate me” is an interpretation.
Translate a label into an observable behaviour
Comments such as “not strategic” or “poor communicator” are too broad to act on directly. Ask what work situation could produce that experience.
For communication, possibilities might include unclear decisions, late context, too much detail or insufficient listening. Each needs a different practice.
Write a provisional statement: “I may be sharing decisions before explaining the assumptions.” Treat it as something to investigate, rather than a verdict.
Use appropriate conversations to clarify the theme without asking anyone to identify a respondent. “What would a more useful decision update contain?” is safer than “Did you write that I lack transparency?”
If confidentiality rules limit discussion, follow the agreed process and work with the facilitator.
A hypothetical report review
Imagine a manager receives positive comments about technical judgement and mixed comments about involving others. Direct reports say decisions arrive late; peers say decisions seem sudden.
She identifies a possible pattern: she works through the options privately and only communicates when she has reached a conclusion.
Her experiment is to share the decision question and constraints earlier on one suitable project, while making clear which parts remain open.
She does not announce that the report proves she is controlling. She has chosen a behaviour that can be tested against the observed concern.
This hypothetical illustrates one interpretation path. A real report might support a different explanation, and the underlying evidence should guide the choice.
Share a useful commitment with the right people
You do not need to distribute the entire report. Share the theme you are working on, the change you will try and how colleagues can tell you whether it helps.
For example: “I want to make project decisions less surprising. On the next review, I will circulate the question and constraints before recommending an option.”
Avoid announcing a long list of weaknesses. It can shift the team’s attention towards reassuring you and create promises you cannot sustain.
Also avoid presenting strengths as a defence against concerns. Being technically capable does not settle whether colleagues have enough opportunity to contribute.
A balanced account can recognise both: “The report suggests my analysis is useful, and that I need to involve people earlier in shaping the decision.”
Choose one experiment with a review point
Define the situation, behaviour and feedback method. “Be more inclusive” is broad. “Ask each relevant function for constraints before drafting the recommendation” is observable.
Agree a time or number of suitable occasions for review. The right interval depends on how often the situation occurs.
Measure the experience and the work, not merely completion of the action. Sending an early note is not enough if nobody understands what input is requested.
Ask: Did colleagues receive the context in time? Did the discussion reveal information we would otherwise have missed? What remained difficult?
Do not claim a causal performance improvement from a small informal experiment. Use it to refine practice.
Handle painful or questionable comments carefully
A comment may be unfair, poorly expressed or influenced by bias. You can examine it without accepting it as a complete description of you.
Discuss concerns with the facilitator or appropriate support person. Check whether the comment points to an observable issue and whether other evidence supports it.
Do not confront suspected respondents or use work assignments to retaliate. That undermines the process and can make future feedback less usable.
If the report reveals a serious conduct concern, follow the appropriate organisational procedure rather than treating it solely as a personal development exercise.
Keep the report connected to everyday practice
Return to the chosen behaviour in normal reviews and development conversations. A 360 report becomes useful through the decisions and habits it informs, rather than through the intensity of your first reaction.
Peak Belt’s guides to trust and credibility and difficult conversations provide related support. Explore the TrueNorth hub for the wider leadership cluster.
Separate development from administrative decisions
Understand how your organisation uses the review. A developmental conversation, promotion assessment and formal performance process may have different rules and consequences. Do not assume that a confidential development report can be shared for another purpose. Ask the facilitator or responsible team what use is permitted before distributing excerpts or drawing conclusions about someone else's employment decisions.
Before your next feedback discussion, choose one theme, one behaviour and one review question. Keep the identity of respondents out of that plan.
AI-assisted researched guidance from PeakBelt. Hypothetical examples are labelled in the text. See our editorial approach.