360 Feedback vs. Performance Review
360-degree feedback is developmental; performance reviews are evaluative. That is the fundamental distinction. 360 feedback surfaces how a leader is perceived by the people around them. Performance reviews assess what a leader produced against their goals. They use different inputs, produce different outcomes, and serve different audiences. Using one as a substitute for the other weakens both. Most organizations need both, running on separate cadences with separate audiences.
The core difference
A performance review is evaluative. It looks backward at what someone accomplished, assesses their output against goals, and typically informs decisions about compensation, promotion, or role fit. It is primarily a manager's judgment of an employee's results.
A 360-degree feedback review is developmental. It looks at how someone leads and relates to the people around them, not what they produced, but how they show up. The input comes from peers, direct reports, and sometimes the manager, all contributing anonymously. The output goes to the leader being reviewed, not to HR or senior management.
Side-by-side comparison
| Dimension | 360 Feedback | Performance Review |
|---|---|---|
| Purpose | Development | Evaluation |
| Input source | Peers, direct reports, manager | Manager (primarily) |
| Anonymity | Anonymous respondents | Named reviewer (manager) |
| What it measures | Leadership behavior and interpersonal effectiveness | Output, goals, results |
| Who sees results | The leader being reviewed | Manager, HR, leadership |
| Tied to compensation? | No (and it shouldn't be) | Usually yes |
| Cadence | Quarterly, biannual, or on demand | Annual or biannual |
| Key output | Self-perception gap, blind spots | Rating, promotion decision |
Why you shouldn't use 360 feedback for compensation decisions
Tying 360 feedback to compensation corrupts the data. The moment respondents believe their ratings could affect a colleague's pay, they inflate scores to avoid being the source of negative consequences. Developmental-only 360 programs produce wider variance in scores, which means more honest differentiation between dimensions. The same people who would give specific, critical feedback in a safe developmental context will rate 5 out of 6 on every dimension when compensation is involved.
This is not a theoretical problem. It is the single most common reason 360 programs fail to produce useful data. Organizations that insist on linking 360 feedback to compensation end up with expensive surveys that tell leaders what they already believe about themselves.
What performance reviews miss
Performance reviews rely on a single perspective: the manager's. A manager sees deliverables and attends selected meetings, but observes only a fraction of how a leader actually operates day to day. They do not see how the leader runs team standups, handles bad news from a direct report, gives real-time feedback, or behaves under pressure when no senior audience is present. The manager's view is also colored by their own relationship dynamics with the person being reviewed.
The people who can answer those questions are peers and direct reports. That is the information 360 feedback surfaces that performance reviews cannot.
What 360 feedback misses
360 feedback is not designed to assess output. Whether a leader hit their sales target, shipped the product, or kept the team on budget. These are performance questions, not 360 questions. A team can give a leader high marks across all leadership dimensions and that leader can still fail to deliver results.
360 feedback measures how someone leads. Performance reviews measure what someone delivered. Run 360 feedback for behavioral insight and self-awareness. Use performance reviews for output accountability and compensation decisions. Both are necessary, and neither replaces the other.
Decision guide: which tool answers which question
Different leadership questions require different assessment tools. Here is how to match the question to the right process.
| Question | Tool | Why |
|---|---|---|
| How does my team experience my leadership? | 360 feedback | Only peers and direct reports can answer this. A manager sees too little of the day-to-day to assess interpersonal dynamics. |
| Did this person hit their goals this quarter? | Performance review | Output measurement requires context on targets, resources, and constraints that only the manager and business data can provide. |
| Is this person ready for promotion? | Both, separately | Promotion decisions should consider output (performance review) and leadership readiness (360 feedback), but the data should come from separate processes run at different times. |
| What are my blind spots as a leader? | 360 feedback | Blind spots are, by definition, things you cannot see yourself. Anonymous multi-rater feedback is the only reliable way to surface them. |
| Should this person receive a raise? | Performance review only | Compensation must be tied to output evaluation, never to 360 feedback. Linking 360 data to pay destroys respondent honesty. |
| How can I improve my communication with direct reports? | 360 feedback | Direct reports are the only people who experience your communication daily. Their anonymous, structured input reveals specific patterns you cannot observe yourself. |
How to design an annual cadence using both tools
The most effective approach runs 360 feedback and performance reviews on separate schedules. Here is one effective annual structure that maintains that separation.
Q1: 360 feedback round
Run a developmental 360 review early in the year. Results go only to the leader. No connection to compensation. Focus: identify 1 to 2 development priorities for the year ahead.
Q2: Development focus
Leaders work on their identified priorities from the 360 round. No formal assessments. Coaching or peer accountability groups are useful here.
Q3: Mid-year performance check-in
Manager and employee review progress against goals. Forward-looking: what needs to shift to finish the year well? This is evaluative but low-stakes.
Q4: Annual performance review
Formal output assessment tied to compensation decisions. Based on the manager's evaluation of results against goals. Completely separate from the Q1 360 data.
The key design principle is temporal separation. Running 360 feedback in a different quarter from performance reviews makes it structurally clear that the two are not connected. This separation protects the honesty of 360 responses.
What to say when stakeholders push to combine them
If a stakeholder pushes to combine the two processes for efficiency, the answer is that combined processes produce less useful data, not more efficient data. Performance reviews answer 'what did you deliver?'; 360 feedback answers 'how do people experience working with you?' A combined process forces respondents into a conflict of interest: they want to give developmental feedback, but they know it might affect their colleague's compensation. Two focused processes of 15 minutes each yield better data than one 30-minute process trying to serve both purposes.
When to run a 360 review
- When a leader wants to understand how their team actually experiences their leadership
- At the start of a new role, to establish a baseline
- After a major organizational change or team restructure
- When a leader's self-perception seems significantly misaligned with their results
- As part of a leadership development program, separate from the review cycle
Related guides
- What is 360-degree feedback? A complete guide to how 360 reviews work and how to run one.
- How to give 360 feedback. A practical guide to writing feedback that is specific and actionable.
- 50 best 360 feedback questions for managers. The complete question bank organized by leadership dimension.
- Free 360 feedback template. A complete template you can run in any tool.
- 360 Feedback for Remote Teams. How to run effective 360 reviews with distributed teams.
- 360 Feedback Software Compared. See how the leading tools stack up on features and pricing.
Frequently asked questions
What are the key differences between 360 feedback and performance reviews?
There are five core differences: purpose, audience, who sees the results, how the data is used, and cadence. Purpose: 360 feedback is developmental; performance reviews are evaluative. Audience: 360 collects from peers, direct reports, and the manager; performance reviews come primarily from the manager. Visibility: 360 results go only to the leader being reviewed; performance reviews are shared with HR and senior management. Use: 360 informs personal development; performance reviews inform compensation, promotion, and role decisions. Cadence: 360 typically runs on a developmental schedule separate from the formal review cycle. Combining them collapses the data quality of both.
Can 360 feedback replace a performance review?
No. 360 feedback cannot replace a performance review because they measure different things. Performance reviews evaluate past output and inform compensation decisions. 360 feedback measures leadership behavior and informs personal development. Combining them corrupts both: respondents inflate ratings to protect colleagues' pay, and the developmental value of honest feedback is destroyed. Organizations that run both as separate processes with separate audiences get better data from each.
How often should you run 360 feedback vs. performance reviews?
Most organizations run formal performance reviews annually or twice a year. 360 feedback is most valuable when run on its own cadence: either once a year as a development exercise, or any time a leader wants a fresh read on how they are landing. Some leaders run a 360 review every six months.
Who should see the results of a 360 review?
Only the leader being reviewed should see their individual 360 results. This confidentiality is what makes honest feedback possible. When 360 results are shared with HR or senior management, the dynamic shifts: respondents inflate ratings to avoid consequences for their colleagues, leaders become defensive rather than curious, and the feedback loses its developmental value. The one exception is multi-leader programs where aggregated, anonymized data (not individual reports) is shared with program administrators for trend analysis.
Is 360 feedback more accurate than a manager performance review?
For measuring leadership behavior and interpersonal effectiveness, 360 feedback is significantly more accurate than a single manager's assessment. Peers and direct reports observe the day-to-day leadership reality that managers miss, including communication patterns, conflict handling, and psychological safety. However, for assessing output quality, goal achievement, and strategic contribution, a manager's evaluation is more appropriate because they have context on business priorities and resource constraints.
How do you run 360 feedback without it feeling like a performance review?
Three design choices separate 360 feedback from performance reviews in practice. First, results go only to the leader being reviewed, never to HR or management. Second, the process runs on a completely different schedule from the performance review cycle. Third, the framing is explicitly developmental: the invitation to respondents should state that this is for the leader's personal growth, not for any organizational decision. When all three are in place, respondents treat it as a development tool rather than a hidden evaluation.
Can managers be included as respondents in a 360 review?
Yes, and in most 360 reviews they should be. The manager provides one perspective among several: peers, direct reports, and the manager each see different aspects of leadership. The key difference from a performance review is that the manager's input in a 360 is one anonymous voice weighted equally with other respondents, not a singular evaluative authority. Including the manager gives the leader a complete picture of how all stakeholder groups perceive them.
What happens if you use 360 feedback data in a performance review?
Data quality collapses. When respondents learn that their anonymous feedback influenced a compensation or promotion decision, trust in the 360 process breaks permanently. Future rounds will produce inflated, undifferentiated scores as respondents protect themselves and their colleagues. Rebuilding that trust typically takes 2 to 3 cycles of proven confidentiality. The short-term convenience of combining data sources creates a long-term cost in feedback quality.