A 360-degree review collects feedback about an employee from everyone they work with: their manager, peers at the same level, direct reports and sometimes external clients. Unlike a top-down review, the method gives a well-rounded picture of behavior and competencies rather than one person's opinion.
The tool is appropriate when you need to assess soft skills (leadership, communication, teamwork), build a talent pool or understand the causes of conflict in a team. For purely results-based metrics (sales plan, deadlines), KPIs are a better fit, and 360 complements them rather than replacing them.
Goals and objectives of a 360 review
Goals:
- get an objective picture of an employee's behavioral and communication competencies;
- reveal blind spots — qualities a person does not see in themselves but colleagues notice;
- lay the groundwork for a development plan and the talent pool;
- give HR and the manager an additional perspective for promotion decisions.
Objectives:
- Collect ratings from several groups: manager, 3–5 peers, direct reports (if any), self-assessment.
- Bring the results to a single scale for each competency.
- Compare the self-assessment with others' ratings and find gaps.
- Prepare feedback and a development plan based on the results.
It is important to decide up front whether the 360 review will affect pay and bonuses. Most often it is kept purely developmental — that way people answer more honestly.
How to run a 360 review: 7 steps
Each step has its own typical risk — below is how to neutralize it before it derails the whole process.
| Step | What we do | Risk and how to neutralize it |
|---|---|---|
| 1. Preparation | Define the purpose of the review, the list of participants and the timeline. | The purpose is vague or not agreed with management — put the purpose and the rules for using the results in writing before the start. |
| 2. Questionnaire and competencies | Draw up a short list of qualities (5–8) and a rating scale. | An overloaded questionnaire and vague wording — test the questionnaire on a pilot group and use specific behavioral indicators. |
| 3. Respondents | Select 5–8 raters at different levels. | The employee picks “friendly” raters — the list is approved by the manager or HR, not by the employee. |
| 4. Data collection | Launch the survey in the HR system. | Low response rate or formal answers — guarantee anonymity and remind people why honest answers matter. |
| 5. Analysis | Aggregate the ratings and compare them with the self-assessment. | Distortion from one harsh answer — remove outliers from the sample and look at the mean and spread of answers. |
| 6. Feedback | Hold a one-on-one session with the employee. | Stress and defensiveness — train the manager to run the conversation using the “fact → impact → action” model. |
| 7. Development plan | Set 2–3 development goals and deadlines. | The plan is forgotten after the meeting — schedule a checkpoint in 1–2 months. |
The cross-cutting risk that overrides every step is loss of trust in anonymity. If even one employee finds out who wrote what, the whole process loses its value for the future.
A practical example: reviewing a sales department head
The head of the sales department at a telecom company goes through a 360 review before being added to the talent pool for the role of division head.
Competencies in the questionnaire: setting tasks, giving feedback, considering the team's interests, resolving conflicts, strategic thinking.
Respondents: the sales director, 2 fellow department heads, 4 sales managers reporting to him, self-assessment.
Result: self-assessment on leadership — 4.5 out of 5; the average rating from direct reports — 3.1. The gap pointed to a harsh management style and weak feedback that the manager himself had not noticed.
Action: the development plan included two specific goals: weekly 1:1s with each manager and training on giving feedback. The promotion was postponed for a quarter.
Three months later, a follow-up survey of direct reports showed the rating had risen to 3.8 — not perfect, but the movement in the right direction was obvious.
How to use the results
- Link them to development, not punishment. The results go into the IDP, not into an order cutting a bonus: otherwise the next survey will get only formal answers.
- Look at the trend, not the number. One cycle gives a snapshot; two or three cycles give a trend. Compare a person with their past self, not only with colleagues.
- Aggregate for team-level conclusions. Department-level data reveals systemic management gaps that are invisible at the level of one person.
- Record specific steps and deadlines. A report without an action plan is forgotten within a week.
- Do not publish named breakdowns without consent. Even inside the company, showing answers by respondent name destroys trust in the tool.
How a 360 review affects the company
When implemented properly, the effect goes beyond the individual employee:
- A feedback culture. When feedback becomes a regular practice, it is easier for people to raise problems directly, without escalation.
- Management quality. Managers see their style through the team's eyes and adjust their behavior before it turns into staff turnover.
- Retention. Employees see that their opinion influences decisions rather than disappearing into an anonymous questionnaire with no consequences.
- Better HR decisions. Promotion and talent pool decisions rest on a wider set of data than one manager's impression.
The flip side: if the process is run as a formality or without protecting anonymity, it undermines trust in any future HR initiatives and increases turnover among strong employees. So introduce 360 only when you are ready to see the process through — with feedback and an action plan, not just collecting questionnaires.
Email template for employees
The email works if it openly addresses three things at once: why this is needed, how anonymity is protected and what will happen to the results. The template below can be adapted to your corporate tone.
Subject: Our 360 review is starting — your opinion matters
Hello,
From [date] to [date], the company will run a 360 review — a survey in which peers, managers and direct reports give each other feedback on key work skills.
Why we are doing this. The purpose of the survey is to help everyone see their strengths and areas for growth through their colleagues' eyes. The results will feed into individual development plans. They do not affect pay, bonuses or disciplinary decisions — this is a tool for development, not control.
Anonymity is guaranteed. Answers are collected anonymously and shown only as averages by respondent group (for example, “peers” or “direct reports”), never by name. Neither your manager nor HR will see who wrote what.
Honesty matters more than comfort. The value of the survey depends directly on how honestly you answer. Straight “fives” across the board help neither your colleagues nor you.
What it takes. 15–20 minutes of your time before [date]. The link to the questionnaire will come in a separate email. If you have questions, contact HR — [contact].
Thank you for taking the time to answer sincerely — it determines how useful the result will be for the whole team.
[Signature of the manager or HR]
Three details that build trust: the email is sent by the head of the company or a division head, not only by HR; the wording about there being no consequences is repeated after the survey ends; and the promise of anonymity holds even if a manager asks to “reveal” specific answers.
