Practice knowledge base
360-Degree Feedback
360-degree feedback gathers observations from the manager, peers, direct reports, and the employee themselves to turn recurring signals into a development plan.
Documentation sections
What it is
This is a developmental feedback process where the employee gets perspectives from different professional angles, not just the manager's evaluation. The practice helps reveal behavioral patterns: how a person interacts, makes decisions, listens to others, and influences the team. It works better as a development tool, rather than as a covert appraisal or a basis for disciplinary actions.
When it helps
- Employees receive feedback only from above and do not see how their work style impacts colleagues.
- Managers debate an individual's development without factual data from different work contexts.
- There is tension in the team around behavior, but people are hesitant to speak directly.
- The company is preparing a talent pipeline and wants to provide participants with a more comprehensive view of their growth areas.
- Surveys indicate that feedback exists formally but does not translate into concrete actions.
How to start
- 1 Define the cycle's objective: employee development, leadership preparation, or talent pipeline support.
- 2 Select respondent groups and establish minimal anonymity rules so that responses cannot be easily linked to a single individual.
- 3 Formulate a concise set of questions focusing on observable behaviors, rather than personal traits.
- 4 Prepare participants: explain how to provide specific and respectful feedback.
- 5 Review the results with the employee and document 2–3 development actions for the upcoming period.
Expected effect
The practice provides the employee with a more accurate picture of how their behavior is perceived by different work groups. It makes it easier for the manager to discuss development based on recurring signals rather than isolated impressions.
Common pitfalls
- Launching 360 as a covert appraisal for disciplinary actions: people quickly start writing cautiously or vindictively.
- Failing to explain confidentiality rules: participants fear giving honest answers, and the recipient attempts to identify comment authors.
- Collecting too many questions: respondents become fatigued and provide superficial answers.
- Leaving results without a development plan: the employee experiences stress but does not understand the next step.
- Delivering raw comments without facilitation, especially if the topic is sensitive or there is team conflict.
Further reading
- Book: Marshall Goldsmith, What Got You Here Won't Get You There
- Book: Center for Creative Leadership, Leveraging the Impact of 360-Degree Feedback
- Research: London and Smither, Feedback orientation and 360-degree feedback
- Book: Douglas Stone and Sheila Heen, Thanks for the Feedback
FAQ
Who should own the process?
Typically, the HR or People team owns the process, while the manager assists in selecting relevant work contexts and supports the development plan. It is crucial for the owner to enforce confidentiality rules and monitor question quality.
Can we start without an external consultant?
Yes, if the cycle is small, questions are straightforward, and the organization is prepared to carefully moderate result discussions. An external specialist is beneficial when the topic is sensitive, participants distrust the process, or feedback impacts career decisions.
Should responses be anonymous?
For peers and direct reports, anonymity usually reduces fear and helps to get more honest signals. But the rules need to be explained in advance: who sees the data, how responses are grouped, and which comments are not shared verbatim.
How can you tell if the practice is working?
After the cycle, the employee should have clear development areas, several specific actions, and a follow-up meeting with the manager. In subsequent discussions, it should be evident that recurring behavioral signals are being discussed, not general impressions.