360 Feedback gives employees a broader view of how their behaviour is experienced at work. Instead of relying on input from only one manager, it brings together feedback from several people, such as colleagues, direct reports and other stakeholders who regularly work with the employee.
One manager only sees part of how someone works. Colleagues may experience their collaboration differently, while direct reports see their leadership style up close. By combining these perspectives, 360 feedback can help employees recognise strengths, identify development areas and turn feedback into practical actions.
What is 360 feedback?
360 feedback is a structured method of collecting feedback about an employee from multiple people around them. These may include a manager, colleagues, direct reports, project members or other stakeholders who regularly work with the employee. A self-assessment is often included as well, so employees can compare their own view with how others experience their behaviour.
The method is also known as 360-degree feedback, a 360 review, 360 assessment, multi-rater feedback or multi-source feedback. Its main value lies in bringing different perspectives together and using those insights to support employee development.
What are the benefits of 360 feedback?
The biggest advantage of 360 feedback is that it provides a wider view of behaviour at work. A manager may see how someone performs against objectives, while peers experience their collaboration and direct reports see how they communicate, delegate or give feedback. Those different perspectives can reveal patterns that would be difficult to spot from one working relationship alone.
360 feedback can also improve self-awareness. Employees may discover that a strength they take for granted is highly valued by others, or that a certain behaviour has a different effect than they intended. This can make development conversations more concrete and help employees focus on behaviours they can actually change.
How does 360 feedback work?
A good 360 feedback process starts before the questionnaire is sent. First decide what you want to learn. Are you focusing on leadership, collaboration, communication or competencies linked to a specific role? A clear purpose makes it easier to choose the right respondents and ask questions that produce useful answers.
The feedback is then collected through a questionnaire, usually combining ratings with open questions. Once the responses have been gathered, they can be brought together in a report or overview. The employee can then discuss recurring themes with a manager, HR professional or coach and decide which development actions deserve attention.
The process becomes most useful when the feedback is followed by action. A report on its own changes very little. The value comes from discussing what the feedback means, choosing a small number of priorities and checking later whether behaviour has changed.
Who should provide 360 feedback?
The best respondents are not necessarily the people who know an employee personally best. They are the people who have enough recent and relevant working experience with that employee to comment on the behaviour being assessed.
For one employee, that group may include a manager, several peers and direct reports. For another role, project members, internal stakeholders or customers may also have useful input. The mix depends on the role and the purpose of the feedback.
Quality matters more than simply increasing the number of responses. Someone who has barely worked with the employee will usually add less than a colleague who regularly sees how that person communicates, makes decisions or collaborates under pressure.
What are good 360 feedback questions?
Good 360 feedback questions focus on behaviour people can actually observe. Broad questions such as “Is this person a good leader?” leave a lot of room for interpretation. A more specific question such as “Does this person explain the reasoning behind decisions clearly?” gives respondents something concrete to assess.
For communication, you could ask whether someone shares relevant information at the right time or listens to different perspectives before making a decision. For collaboration, you might ask how well someone involves colleagues when their input is needed or how they respond when plans change.
Open questions can add useful context to ratings. Examples include “What is one behaviour this person should continue?” and “What could this person do differently to make collaboration easier?” The aim is to gather feedback the employee can recognise and act on, rather than vague opinions about personality.
How is 360 feedback different from a performance review?
A performance review and 360 feedback can both contribute to employee development, but they are not the same process. A traditional performance review is usually led by a manager and may include objectives, results, responsibilities and formal performance decisions.
360 feedback adds observations from several people who work with the employee in different situations. That makes it particularly useful for understanding behaviour, working relationships and development areas.
The purpose should therefore be clear from the start. If people believe their comments directly influence a colleague’s pay or promotion, they may approach the questionnaire differently. For development-focused 360 feedback, it is usually more useful to create an environment where respondents can concentrate on specific, constructive observations.
Should 360 feedback be anonymous?
There is no single setup that works for every organisation. Some organisations make individual responses anonymous or combine feedback from groups, while others use a more open process. What matters most is that everyone understands the rules before they take part.
Be clear about whether responses are identifiable, how feedback is grouped, who can see open comments and who has access to the final results. Confidentiality is especially important when feedback comes from direct reports or peers, because people may be less candid if they are unsure how their comments will be handled.
Employee feedback can also involve personal data. Organisations therefore need to consider how feedback is accessed, stored, protected and retained, particularly where data protection rules such as the GDPR apply.
When should you use 360 feedback?
360 feedback is most useful when there is a clear development question and the employee works with enough different people to make multiple perspectives meaningful. It can support leadership development, preparation for a broader role, cross-team collaboration, competency development or reflection after a substantial project or change.
It is less suitable when respondents barely know the employee’s work or when the organisation has not decided what it wants to do with the results. Timing matters as well. During an unresolved team conflict or a period of very low trust, a new feedback round may produce more noise than useful insight.
360 feedback also works best as one source of information rather than the only measure of someone’s development. Other input, such as manager observations, coaching conversations and skills assessments, can add useful context.
What are the common pitfalls of 360 feedback?
One common mistake is starting with a questionnaire before deciding what the organisation wants to achieve. Without a clear purpose, questions easily become too broad and employees may not understand what will happen with their answers.
Another pitfall is choosing respondents based on convenience rather than relevant working experience. This can result in generic feedback that tells the employee very little. The same happens when questions focus on abstract characteristics instead of observable behaviour.
There is also a risk of giving too much weight to one comment or one low rating. 360 feedback is most useful when you look for recurring themes across different respondents. Individual remarks can provide context, but they should not automatically determine the overall conclusion.
Finally, the process loses value when there is no follow-up. Collecting feedback and sending a report is easy. Helping someone decide what to do differently is the part that requires attention.
What should you do with the results of 360 feedback?
Start by looking for patterns rather than trying to respond to every individual comment. Which strengths appear several times? Which development areas are mentioned by different groups? And where is there a noticeable difference between the employee’s self-assessment and the way others experience their behaviour?
From there, choose a small number of priorities. “Improve communication” is too broad to be useful. A clearer action could be “Explain the reasoning behind important decisions before asking the team to act on them.” That gives the employee something specific to practise and makes progress easier to discuss later.
The results can then become part of a wider development conversation. HR can help make the process clear and workable, but the employee should understand the feedback and take an active role in deciding what to work on. That is what turns 360 feedback from a survey into something that can actually support development.