Performance
360-degree feedback: a step-by-step guide and sample survey
When 360 feedback gives people honest input, and when it just damages team relationships. A step-by-step process, a ready-to-use survey with a rating scale, and how to read the gaps between self-assessment and peer ratings.
In short
- 360-degree feedback collects input on an employee's behaviour from their manager, peers and direct reports, plus a self-assessment, all against the same set of competencies.
- It's a development tool, not a way to set bonuses or decide on dismissals. As soon as money depends on the result, the answers stop being honest.
- At least 3 raters in each group, anonymity, 5–7 competencies, a 15–20 minute survey and two weeks to collect responses.
- The most valuable part is the gap between self-assessment and how others see the person. You discuss it in a 1:1 and turn it into 1–2 development goals.
What is 360-degree feedback
The 360-degree method gathers feedback on an employee from every direction: their manager, peers at the same level, direct reports (if they have any) and sometimes internal clients from neighbouring departments. The employee fills in the same survey about themselves.
It assesses behaviour, not results: how the person makes decisions, delegates, keeps their commitments and helps colleagues. Results are measured with employee KPIs, and the two tools complement each other. A head of sales can beat their target every month and still burn out the team. KPIs won't show that, but a 360 review will.
The output is a report with average scores per competency broken down by rater group, the gaps between self-assessment and others' ratings, and anonymous comments.
When the 360 method works and when it doesn't
It works
- For managers and people being prepared for management roles: their direct reports and peers see their work better than their boss does.
- For roles with a lot of interaction: project managers, account managers, team leads, HR business partners.
- When you need material for an individual development plan, not just "you're doing fine".
- In teams with a basic level of trust, where people aren't afraid to speak honestly.
It doesn't work
- For calculating bonuses or deciding on dismissals. Colleagues will start protecting each other or settling scores, and the data becomes meaningless.
- In small teams of 3–4 people. Anonymity is impossible: the employee will easily work out who wrote what.
- During layoffs and conflicts. Deal with the situation first, or you'll get an outpouring of emotion instead of an assessment.
- For frontline staff doing simple, routine tasks. A warehouse operative or line operator benefits more from clear KPIs and regular feedback from their supervisor.
If you're unsure about the level of trust, run an anonymous pulse survey first and check your eNPS. If the score is strongly negative, it's better to hold off on 360.
How to run 360-degree feedback: step by step
Step 1. Define the competencies
Pick 5–7 competencies, no more. Describe each one through 3–4 observable behaviours: things you can actually see, not personality traits. "Responsible" is a trait. "Flags the risk of a missed deadline in advance, not on the day it's due" is a behaviour.
For managers, the usual set is: setting tasks, developing the team, giving feedback, decision-making, cross-department collaboration and a focus on results.
Step 2. Choose the raters
- Manager — 1 person.
- Peers — 3–5 people who actually work with the employee, not just sit nearby.
- Direct reports — at least 3, otherwise their answers aren't shown separately.
- Self-assessment — mandatory.
The employee proposes the list of raters and the manager approves it. That way the person trusts the result, and they can't just pick their friends. Limit the workload: one person fills in no more than 5–6 surveys per cycle, or they'll rush through the last ones without reading.
Step 3. Guarantee anonymity
Peer and direct-report responses are shown only as a group average, and only if the group has at least 3 responses. Comments appear without names. The only non-anonymous rating is the manager's: there's just one, it's shown separately, and that's fine.
Announce the rules before you start: who will see the report (the employee, their manager, HR), that the report doesn't affect pay, and how the results will be used. Without that email, people will give everyone a 4 out of 5.
How it works in TapHR
In the Performance module, a 360° review is launched from a competency template: HR picks the participants, the system sends out surveys and reminders, and peer and direct-report responses appear anonymously in the report. You can carry the results straight into a 1:1 meeting and an individual development plan.
Step 4. Prepare the survey
The survey should take 15–20 minutes to complete. That's roughly 20–25 rated statements and 2–3 open questions. You can copy and adapt the example below.
360 survey: an example for a manager
Scale: 1 — never does this; 2 — rarely; 3 — sometimes; 4 — often; 5 — always does this; N/A — can't assess.
Setting tasks
- Sets tasks with a clear outcome and deadline.
- Explains why a task matters and how it connects to the department's goals.
- Doesn't change priorities without explaining why.
Feedback
- Raises problems with work right away, not a month later.
- Recognises good work specifically, not in general terms.
- Takes criticism calmly.
Developing the team
- Delegates tasks that help people grow.
- Holds regular one-on-one meetings.
- Helps people figure things out instead of doing the work for them.
Collaboration
- Delivers on commitments to other departments on time.
- Shares the information colleagues need to do their jobs.
- Resolves conflicts by talking, not by escalating.
Open questions
- What should this person keep doing?
- What should they start doing?
- What should they stop doing?
The "N/A" option is a must. Without it, a colleague from accounting will give a 3 for "holds regular one-on-one meetings" with no idea how that actually works, and drag the average down.
Step 5. Set the timeline
- One week before launch — an email with the rules and the rater lists for approval.
- Collecting responses — 10 working days, with reminders on day 4 and day 8.
- Reports — within a week of closing the survey.
- 1:1 meetings on the results — within two weeks of the report, while the feedback is still fresh.
The whole cycle takes 5–6 weeks. It makes sense to repeat it once a year, or every six months for managers with an active development plan.
Step 6. Build the report
Each employee's report should include: the average score for each competency by group (self, manager, peers, direct reports), the 3 highest- and 3 lowest-rated statements, the gaps between self-assessment and others' ratings, and comments grouped by theme.
Don't rank employees by overall score or publish a leaderboard. That instantly turns a development tool into a competition.
How to read the gaps between self-assessment and others' ratings
A gap is the difference between how a person sees themselves and how others see them. Calculate it for each competency.
Gap = self-assessment − average rating from others (excluding self)
On a five-point scale, a gap of up to 0.5 is usually not significant. From 0.8 upwards, it's worth a conversation.
| Situation | What it means | What to discuss |
|---|---|---|
| High self-rating, lower ratings from others | Blind spot: the person doesn't see how their behaviour comes across | Specific situations from the comments, without hunting for "who wrote it" |
| Low self-rating, higher ratings from others | Hidden strength: the person underestimates themselves | Where to use this strength more, for example in mentoring |
| Both ratings high | Confirmed strength | How to build on it in new tasks |
| Both ratings low | Acknowledged area for growth | The easiest case: straight into the development plan |
| Manager and direct reports disagree | The employee behaves differently "upwards" and "downwards" | Different examples from different groups |
An example. A warehouse manager in Almaty rated himself 4.6 on "feedback". His direct reports gave 3.1, and his peers 3.8. The gap with his reports is 1.5 points. One comment keeps coming up: "we find out about mistakes at the general team meeting". That's a concrete topic: switch to reviewing mistakes one-on-one.
The 1:1 conversation after a 360 review
A report without a conversation is almost useless: the person reads it, gets upset over a couple of comments and closes it. The meeting is run by the manager, and for difficult reports, together with HR.
Structure of a 1:1 meeting after a 360 review (45–60 minutes)
- Ask what the employee saw in the report and what surprised them. Start with their view, not yours.
- Go through 2–3 strengths confirmed by different groups.
- Go through the 1–2 biggest gaps. Ask them to recall situations where this might have shown up.
- Don't discuss who wrote what. If the employee tries to guess the author, bring the conversation back to behaviour.
- Agree on 1–2 development goals with specific actions and a deadline.
- Schedule a follow-up in 4–6 weeks to check progress.
Record development goals in the individual development plan, not in meeting notes nobody will ever open. If a goal requires training — for example, a feedback course for managers — it's easy to assign through the learning platform.
Common mistakes
- Linking it to bonuses. The biggest mistake. As soon as the result affects money, people agree to give each other high scores.
- A survey that's too long. 60 questions for each of 6 colleagues, and by the third survey the rater answers "4" to everything.
- Abstract competencies. "Leadership" or "strategic thinking" without a description of behaviour means something different to everyone.
- Broken anonymity. All it takes is one case where a manager "figured out" who wrote a comment and confronted them, and the next cycle will come back empty.
- A report with no meeting and no plan. People spend time on surveys and see no consequences. They won't want to take part a second time.
- Rolling it out to the whole company at once. Start with 10–20 managers, fine-tune the survey and the process, then expand.
Where to start tomorrow
360 feedback launch checklist
- Choose a pilot group: 10–20 managers or future managers.
- Describe 5–7 competencies in terms of observable behaviour.
- Build a 15–20 minute survey based on the example above, with a 1–5 scale and an "N/A" option.
- Write an email with the rules: anonymity, who sees the report, no link to bonuses.
- Approve the rater lists: at least 3 in each group, no more than 6 surveys per person.
- Collect responses over 10 working days with two reminders.
- Hold 1:1 meetings within two weeks and record 1–2 development goals for each person.
- After 2–3 months, ask participants what was useful and adjust the process before the next cycle.
