Leadership team analysing multi-source feedback data

A 360 assessment can produce a large amount of information: competency scores, respondent-group comparisons, self-other gaps and written comments. More data does not automatically create better insight. The quality of the analysis determines whether participants leave with a confusing collection of numbers or a clear set of development priorities.

Analyse themes, not isolated scores

Every rating is influenced by role, opportunity to observe and working context. Strong analysis looks for repeated signals. A single low score may reflect a specific interaction, while a pattern across several questions and respondent groups may indicate a behaviour worth exploring. Written comments can help explain what the numerical pattern looks like in practice.

Consider respondent perspectives

Managers, peers and direct reports often see different parts of someone’s role. Differences between groups can therefore be informative. For example, peers may value collaboration while direct reports want clearer delegation. The goal is not to average away those differences but to understand what each relationship requires.

Use self-other gaps carefully

A gap between self-ratings and ratings from others can signal a blind spot, an under-recognised strength or simply different interpretations of a question. Treat it as a prompt for inquiry rather than a verdict. Ask what examples might explain the difference and what evidence would help the participant test their understanding.

Prioritise by impact and readiness

Not every development opportunity deserves equal attention. A practical prioritisation discussion considers:

  • the importance of the behaviour to the current or future role;
  • the consistency of the feedback pattern;
  • the likely effect on colleagues and business outcomes;
  • the participant’s motivation and ability to practise change;
  • existing strengths that can support improvement.
Analysis test: a useful insight should be explainable in plain language and connected to an observable workplace behaviour.

Avoid false precision

Small score differences should not be over-interpreted. Ratings are perceptions, not laboratory measurements. Good analysis respects the structure of the data while keeping attention on conversations, examples and actionable themes.

Strong analysis makes feedback safer and more useful. It reduces the risk of reacting to outliers, helps participants understand multiple perspectives and creates a defensible basis for choosing development priorities.

Related pages