What it means
A line manager sees how an employee reports upward but may not see how that person delegates, treats customers or helps colleagues. Multi-rater feedback fills those gaps by combining views from different relationships, including the person's own self-assessment.
Start with a clear purpose, for example improving how team leaders coach or communicate, and tell participants whether the results will feed into appraisals and who can read the report. Do not change those rules after people have answered.
Choose raters who have worked directly with the person recently, and include more than one relationship group instead of collecting eight opinions from the same team. Ask about behaviour people can observe, such as "explains deadlines clearly", rather than vague labels such as "is a good leader".
Leave room for written examples, because a score alone shows a pattern but rarely explains what to change. Confidentiality needs careful wording.
Averages across a peer group protect individuals better than separate comments, yet in a small team or with a distinctive comment the author can still be guessed, so tell respondents what is anonymous, what is merely confidential and what cannot be guaranteed. Average scores help organise the results but hide disagreement, which is why the spread of answers matters as much as the mean.
Show the number of responses, and avoid ranking people on small samples. The report only helps if there is a debrief and a follow-up.
A facilitator or trained manager should help the person find repeated themes, pick two or three realistic actions and set a date to check progress, remembering that a later survey will involve different raters and circumstances.
In practice
Real-world examples.
Example
The founder of a design agency asks supervisors, peers and direct reports to rate how four team leads delegate work. She then holds a separate development conversation with each lead. Each conversation starts with strengths and ends with two practical actions.
Example
A hospital ward manager scores herself highly on explaining priorities, while several nurses describe changes made late in the shift. Her director asks for examples before agreeing a clearer handover routine. The ward then trials a short written summary at each shift change.
Example
A six-person software team cannot safely promise that written comments will be anonymous. The organiser says so openly and reports only grouped themes rather than individual remarks. Team members say they feel safer answering honestly as a result.
Formula
Calculation
Average rating = sum of valid ratings / number of valid ratings.
Take a question scored from 1 to 5 and answered by eight raters. In scenario A all eight give a 4, so the total is 8 x 4 = 32 and the average is 32 / 8 = 4.0. In scenario B two raters give a 2 and six give a 5, so the total is (2 x 2) + (6 x 5) = 4 + 30 = 34 and the average is 34 / 8 = 4.25.
Scenario B has the higher average, yet two raters are clearly seeing a problem that the other six are not. Always record the distribution and any "not observed" answers alongside the average; the average is a summary, not a verdict.Case study
Seen in the real world.
This illustrative and entirely fictional case follows Horizon Engineering, an invented small firm. Its project leaders delivered work on time, but new employees said handovers were confusing, so the owner ran a developmental 360 survey with questions about observable handover behaviour for direct reports, peers and supervisors.
One leader's self-score was high while several groups mentioned unclear task ownership. The leader began ending meetings with a written owner and deadline for each task, then checked six weeks later whether the team could find past decisions. The case does not claim the survey alone solved the problem; it simply gave the leader specific evidence to act on.
The owner repeats a shorter version of the survey a year later, with a note that raters and projects have changed. She treats the results as a conversation starter rather than a score to beat, and the leaders are asked to share what they tried instead of what they scored.
Watch out
Common mistakes.
- Treating an average score as a formal verdict without looking at examples, rater groups and sample size.
- Promising anonymity that a small group or a distinctive written comment cannot actually provide.
- Collecting the report and then offering no debrief, realistic development goal or follow-up.
Questions
People also ask.
What is 360-degree feedback?
It is structured feedback from several groups that see different parts of a person's work, usually used to guide development, with the purpose set before responses are collected.
Is it anonymous?
Not always. Responses may be grouped or kept confidential, but a small group or a distinctive comment can expose a respondent, so check the stated protections before answering.
What is it used for?
Usually leadership or employee development. An employer may design other uses, but it must tell participants and should not mistake the survey for complete performance evidence.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%Related