Practice knowledge base
Peer-to-Peer Feedback (360°)
Regular feedback from colleagues, cross-functional partners, and managers helps create a broader view of work behavior than the opinion of a single manager alone.
Documentation sections
What it is
Peer-to-Peer Feedback, or 360-degree feedback, gathers observations from people who regularly work with an employee or team. The practice helps reveal recurring behavior patterns: how a person collaborates, makes decisions, responds to agreements, and influences others. It is useful when feedback is used for development rather than as a hidden tool for punishment.
When it helps
- An employee’s evaluation depends almost entirely on the opinion of their direct manager.
- Teams complain about interaction style but cannot point to recurring examples.
- Cross-functional partners regularly encounter delays, harsh responses, or broken agreements.
- A manager needs to prepare a development conversation based on observations rather than rumors.
- The company has strong horizontal connections, but feedback only flows from the top down.
How to start
- 1 Choose a small pilot: one team or one role that involves a lot of cross-functional work.
- 2 Define 3-5 observable criteria: keeping agreements, quality of collaboration, clarity of communication.
- 3 Assign a process owner who will collect responses, remove personal attacks, and prepare a brief summary.
- 4 Run the first cycle as developmental feedback without affecting pay or disciplinary decisions.
- 5 Set the rules: who gives feedback, how confidentiality is maintained, and how the employee discusses the conclusions.
Expected effect
The manager gets a fuller picture of an employee’s or team’s behavior. Participants see which actions support working well with colleagues and which repeatedly create friction, delays, or distrust.
Common pitfalls
- Using the practice as a hidden performance review: people start writing cautiously or vindictively.
- Collecting general opinions without examples of behavior, which makes the conclusions hard to discuss and verify.
- Not explaining who will see the responses and how they will affect decisions about the employee.
- Asking for feedback too often without showing what changed as a result.
- Mixing development, punishment, and salary decisions in one cycle without clear rules.
Further reading
- Book: Marshall Goldsmith, What Got You Here Won't Get You There
- Book: Douglas Stone, Sheila Heen, Thanks for the Feedback
- Research: Center for Creative Leadership, best practices in 360-degree feedback
- Book: Kim Scott, Radical Candor
FAQ
Who should own the process?
Usually, the owner is HR or a functional manager. The team manager takes part in choosing the criteria and discussing the conclusions, but should not single-handedly filter out uncomfortable feedback.
Can you start without an external consultant?
Yes, if the scale is small and the rules are clear. Start with a pilot, a short form, and a manual summary. External help is useful when the results affect career decisions or there is a high level of conflict.
How can you reduce participant resistance?
Explain the purpose, show the questions in advance, and separate the first cycle from punishment and salary decisions. People find it easier to participate when they understand how the responses will be used.
How can you tell whether the practice is working?
Look at whether specific agreements appear after the discussion, whether the manager returns to them in 1:1s, and whether the number of recurring complaints about the same work situations goes down.