360 feedback vs performance reviews, what's the difference
A 360 gathers anonymous feedback on a leader's behaviour for development. A performance review is a manager's assessment of results, often tied to pay.
· 6 min read · Convergo360 team
360 feedback collects anonymous ratings of a leader's behaviour from their manager, peers, direct reports and other staff, and is used to help that leader develop. A performance review is a manager's assessment of an employee's results against agreed goals, and it usually feeds decisions on pay, bonuses and promotion. The two answer different questions, so most organisations run them as separate processes.
What is the main difference between a 360 and a performance review?
The difference is in the question each one answers. A performance review asks whether a person delivered what was agreed for the period. A 360 asks how a leader goes about their work and how that comes across to the people around them.
That difference drives everything else. A performance review needs a decision at the end, such as a rating or an increase, so the manager owns it and signs it. A 360 needs candid input from people who have little power over the leader, so it has to protect their identity and stay away from decisions about money.
360 feedback vs performance review at a glance
| 360 feedback | Performance review | |
|---|---|---|
| Main purpose | Leadership development | Assess results and inform pay, bonus and promotion |
| What is measured | How often the leader shows specific behaviours | Delivery against goals, targets and job requirements |
| Who gives input | Self, Manager, Peers, Direct Reports, Other Staff | Mainly the line manager, sometimes with a self-assessment |
| Anonymity | Anonymous for every group except the manager, with a minimum of 3 responses per group | Named, the reviewer is known and the employee usually signs |
| Link to pay | None | Usually direct |
| Who sees the result | The leader and their coach or debrief partner | The employee, their manager, HR and often a moderation panel |
| How often | Every 12 to 18 months | Once or twice a year, often with quarterly check-ins |
| Typical output | A report with gaps, strengths and a development plan | A rating, an outcome on pay or bonus, and goals for next period |
| Who runs it | Ideally an independent administrator | Line manager and HR |
Who gives input in each?
In a performance review, the line manager does most of the work. The employee often completes a self-assessment first, and some organisations add input from a second-level manager or a moderation meeting where managers compare ratings across teams.
A 360 widens the circle on purpose. The leader rates themselves, and so do their manager, three to five peers, their direct reports and a group of other staff who deal with them from outside their reporting line. Each group sees different behaviour. A manager sees how the leader reports upward and delivers on commitments, while direct reports see how they give feedback, recognise good work and handle disagreement. Our guide to choosing 360 raters explains how to build a balanced list.
Should 360 feedback be linked to pay?
Keep 360 results away from pay, bonuses and promotion decisions. Once raters know their scores affect a colleague's income, many of them rate more generously, and comments become cautious and general. Leaders notice the stakes too and spend the debrief defending scores instead of working out what to change.
Research on rating purpose points the same way. A meta-analysis by Jawahar and Williams (1997), covering 22 studies, found that ratings collected for administrative purposes such as pay and promotion were about a third of a standard deviation higher than ratings collected for development or research. The gap was larger when practising managers rated their own staff in workplace settings.
For this reason, the purpose of a Convergo360 cycle is stated to raters in the survey introduction as leadership development, separate from pay and performance ratings.
How often should you run each?
A formal performance review usually runs once or twice a year, linked to the financial year and the increase cycle, with shorter check-ins in between.
A 360 works on a longer rhythm. Behaviour takes time to shift and for colleagues to notice, so 12 to 18 months between cycles suits most leaders. Running a 360 more often adds survey load for raters without giving the leader enough time to work on their plan. A full 360 cycle, from briefing to development plan, takes about six to eight weeks. The complete guide to 360 feedback in South Africa sets out each step.
Try to schedule the two processes in different months. If a 360 survey opens in the same weeks as year-end reviews, raters assume a link even when there isn't one.
Is a performance review anonymous?
A performance review is a named, two-way document. The employee knows who assessed them and can respond, query a rating or follow the organisation's grievance process. That openness is necessary because the review leads to decisions about their pay and career.
A 360 depends on the opposite. Direct reports and junior colleagues give candid feedback about someone with authority over them only when they trust it can't be traced. Common safeguards include:
- At least 3 responses before a group's results are shown on their own, with smaller groups merged into "Others"
- Manager feedback shown separately and labelled as not anonymous, because it comes from one person
- Comments listed alphabetically within each group, never in the order they were submitted
- An administrator who removes identifying details from comments before release
Our article on 360 feedback anonymity explains each rule, and the anonymity page shows how Convergo360 applies them.
Why does mixing them make feedback less candid?
When a 360 feeds a performance review, three groups change their behaviour at once.
Raters start thinking about consequences. A direct report who would rate "gives regular, constructive feedback" a 2 will think twice if that score could cost their manager a bonus, and peers who compete for the same promotion have a reason to rate each other down. The ratings drift away from what people see day to day.
The leader reads the report differently. With money attached, a gap between self and others becomes a threat to argue with. In a development setting, the same gap is information the leader can use.
Managers and HR also face a fairness problem. A 360 score depends on who was invited, how many responded and how generous each group tends to be. Those factors are fine for a private development conversation but hard to defend in a pay decision that has to be consistent across teams.
Once trust is lost, it carries into the next cycle. Raters who suspect their answers fed into someone's increase give safer answers the following year, and the 360 loses the candour that made it useful.
When should you use a 360 and when a performance review?
Use a performance review when you need to:
- Assess delivery against goals for a set period
- Decide on increases, bonuses or promotion
- Document performance concerns and agree a formal improvement plan
- Set goals for the next period
Use a 360 when you want to:
- Show a leader how their behaviour comes across to different groups
- Set a baseline at the start of a leadership or coaching programme
- Support a new manager in their first year
- Find development themes across a leadership team
Can a 360 inform a performance review at all?
It can, in a narrow way that keeps the scores private. After the debrief, the leader writes a development plan with one to three behaviours to work on. The leader can choose to share that plan with their manager, and the manager can then ask about progress in regular check-ins or the next review. The conversation is about the actions the leader committed to, and the ratings and comments stay with the leader and their coach.
Agree this rule before the cycle starts and include it in the briefing to raters, so everyone knows exactly where the 360 results go. The 360 feedback debrief guide covers how to turn a report into a plan the leader will follow.
Next step
Check the timing of your current review cycle and pick a 360 window at least a month away from it. Then draft the one paragraph you will send to raters explaining that the 360 is for development and who will see each report. The sample report shows what a leader receives at the end.
Sources
- Jawahar, I. M. and Williams, C. R. (1997), Where all the children are above average, a meta-analysis of the performance appraisal purpose effect, Personnel Psychology 50(4)
Common questions
What is the difference between 360 feedback and a performance review?
A 360 collects anonymous ratings of a leader's behaviour from several rater groups to support development. A performance review is the manager's assessment of results against agreed goals and usually feeds pay, bonus and promotion decisions.
Can 360 feedback be used in a performance review?
Keep the scores out of it. The leader can choose to share their development plan with their manager, and progress on that plan can be discussed, but the ratings and comments should stay with the leader and their coach.
How often should you run a 360?
Every 12 to 18 months suits most leaders. That leaves enough time to work on a development plan and for colleagues to notice any change.
Are performance reviews anonymous?
No. The manager who writes the review is named and the employee usually signs it. A 360 protects rater anonymity by grouping responses and only showing groups with at least 3 replies.