Guide · Choosing
360 review vs peer feedback vs engagement survey: which one answers your question?
The three get bought for each other’s jobs constantly — a 360 rolled out to “fix team dynamics”, an engagement survey read as a manager scorecard, a peer survey used as a performance input. Each answers one question well and the others badly. Here is the difference, in a table and then in the cases where it matters.
About a 8-minute read · Sources at the foot · Last reviewed
The one-line versions
- Peer feedback (a team survey): one team rates each other on observable behavior, and the team talks about the result together. The unit is the team.
- 360 review (a Leadership 360): many people around one person — reports, peers, sometimes a manager — describe what working with that person is like. The unit is the individual.
- Engagement survey: everyone in the organization answers the same questions about their own work and their own team, once, and results are reported as group numbers. The unit is the organization and its units.
A 180 is a 360 with one direction removed — usually the reports rating the manager without peers or self. A pulse is an engagement survey run short and often. Neither changes the row it belongs to below.
Side by side
| Row | Peer feedback / team survey | 360 review | Engagement survey |
|---|---|---|---|
| Question it answers | How does this team work, as its members see it? | How does this person land on the people around them? | How do people across the organization experience their work and their teams? |
| Who rates whom | Everyone on the team rates everyone, including themselves | 3–25 colleagues rate one subject; the subject predicts what they will say | Everyone rates their own experience; nobody rates a person |
| Typical size | 3–12 people | One subject, several raters | Whole organization, in headcount bands |
| What is rated | Specific behaviors over a recent window, plus team climate | The subject's leadership behaviors and their effect | Team climate, engagement, intent to stay, likelihood to recommend |
| What comes back | Team pack (group numbers), a private note per person, a debrief agenda | A private report for the subject; themes, never verbatim comments | Group numbers with intervals for organization, unit, manager; themes from open text |
| Who sees individual answers | Nobody with an account | Nobody, including the subject — only aggregates above a floor | Nobody at the organization |
| Smallest reportable group | 3 raters; 5 for question-level | 3 raters, or nothing is shown; 5 for question-level | 5 respondents by default, subtraction-safe |
| Follow-up built in | Yes — a 60-minute debrief | The subject's own reflection | Reporting only; a unit that wants a debrief runs a team survey |
| Developmental or evaluative | Developmental; walled off from any performance record | Developmental; the subject controls sharing | Organizational; not about individuals |
| How it is priced (in Facets) | Per run, per team | Per leader | Per cycle, by headcount band |
Which one you actually need
“Something is off on my team”
Peer feedback. The information you need is inside the team — who goes to whom, whether people agree about what is going wrong, and how each person’s self-view compares with how teammates see them. A 360 on the lead alone answers a different question; an engagement survey will show the team’s climate score but cannot produce the conversation. The debrief is the deliverable. How to run it.
“I want to know how I land as a leader”
A 360. It is about one person, it needs enough raters that no single voice can be recovered, and it should be private to the subject — the point is self-knowledge, not a file. Ask two things of any 360 before using it: whether raters’ comments are ever shown verbatim (they should not be), and whether the subject is asked to predict their raters’ answers before seeing them, which turns a score into a gap worth talking about. Why the prediction matters.
“Leadership wants a number for the whole company”
An engagement survey. It is the only one of the three designed to be summed. What to insist on: error bars with every mean (a difference of 0.3 between two teams of six is noise), a reporting floor, and — the part that is easiest to skip — protection against recovering a hidden small group by subtracting the visible ones from the total. Read the thresholds guide before choosing a vendor.
“We want to combine them”
Combine the instruments, not the data. Asking the same team-climate questions in the engagement survey that the team survey asks means a unit’s numbers mean the same thing wherever they came from — that is worth having. Joining the data — reading peer feedback into a manager’s file, or a 360 into a performance rating — destroys the thing that made people answer honestly. Keep a wall between developmental feedback and any evaluative record, and make it structural, not a policy.
The mistakes that happen when they are confused
- The 360 rolled out as a team intervention. Twelve people each get a private report about themselves and nobody gets a shared picture of the team. Twelve conversations that never happen.
- The engagement survey read as a manager league table. A unit mean of 3.6 against another’s 3.9, with no interval and no headcount, becomes a ranking of managers. It was never precise enough to be one, and the moment managers know it is used that way, next year’s answers move.
- Peer feedback as a performance input. The first time a peer rating affects someone’s review, the rating stops being about behavior and starts being about alliances. Every subsequent run measures politics.
- A pulse instead of a decision. Asking monthly and acting annually teaches people that answering changes nothing.
How the three are built in Facets
Facets sells all three, on one instrument and one set of rules, which is why the comparison above can be exact rather than generic.
- The team survey is peer feedback: 3–12 people rate each other on 16 behaviors across 8 dimensions, rate themselves, predict how they were rated, and answer 40 statements about the team’s climate. Results are a team pack, a private note each, and a 60-minute debrief agenda. Priced per run. For teams.
- The Leadership 360 invites 3–25 colleagues; nothing is shown to the leader below 3 raters, question-level detail needs 5, and comments are never quoted. The leader predicts their raters’ answers first. Priced per leader. The Leadership 360.
- The engagement cycle asks everyone the same 40 climate statements about their own team plus 6 about their own work and 2 optional open questions; reports group numbers with 95% intervals for the organization, each unit and each manager; withholds groups under 5 and any sibling that would reveal one. Priced per cycle, by headcount band. Engagement cycles.
- The manager tools sit on the other side of a wall: a record a leader keeps for their reports. Nothing crosses from the feedback side unless the person it is about sends it. For leaders · Every price on one page.
Frequently asked questions
What is the difference between a 360 review and peer feedback?
Is an engagement survey the same as a 360?
Can 360 feedback be used for performance reviews?
Which is better for a small team: a 360 or a team survey?
How often should each be run?
Sources and notes
Definitions follow conventional usage in the organizational-feedback literature and vendor documentation reviewed in 2026; the Facets specifics are read from the published instrument and pricing pages. The point about 360s and pay is practitioner consensus rather than a single cited study; the research page discusses what feedback does and does not do.
Start with a team survey.
One team, 3–12 people, everyone rates everyone, and the results become a debrief. The 360 and the engagement cycle are there when the question changes.