Why 360 Feedback Fails, and what to do about it
Most organisations have run a 360-degree feedback process at some point. Many run them every year. People fill in the surveys, the reports come back, there's a conversation with someone from HR or an external coach, and everyone agrees it was useful.
Then, twelve months later, the next 360 comes round, and the feedback is broadly the same. If that sounds familiar, the problem probably isn't the feedback, it's what happens next.
The comfortable failure
360 feedback fails quietly. There's no obvious moment where it goes wrong. It just...doesn't change anything.
That's what makes it such a persistent problem. A process that visibly failed would get fixed. A process that produces a thoughtful conversation and a set of development notes looks like it's working, right up until you compare this year's report with last year's and notice how little has moved.
There are three reasons this happens, and none of them is about the quality of the feedback itself.
Reason one: the feedback lands on the person, not the system
A 360 tells a leader how the people around them experience them. It's individual by design.
But most of the behaviours it surfaces aren't purely individual. A leader who "doesn't delegate enough" may be operating in a team where nobody else has been trained to take the work on. A leader described as "hard to reach" may be sitting in eleven hours of meetings a day. A leader whose communication is called inconsistent may be relaying decisions they only found out about that morning.
Hand that person a report telling them to delegate more, be more available, communicate more clearly, and you've given them an accurate description of a problem they cannot solve on their own.
The feedback isn't wrong. It's just aimed at the wrong level.
Reason two: knowing isn't the same as being able
Ask most leaders what they should do differently and they can tell you. The gap is rarely in awareness.
Someone who avoids difficult conversations usually knows they avoid difficult conversations. Telling them again doesn't help. What they're missing is the capability, the actual words, the structure, the practice. To do the thing they already know they should do.
This is where the well-intentioned development plan tends to fall over. "Have more direct conversations with your team" isn't a plan. It's a restatement of the feedback with a verb in front of it.
Behaviour change needs the same things any change needs: a clear picture of what good looks like, the skills to do it, and some reason to prioritise it over the forty other things competing for attention that week. A report alone supplies none of those.
Reason three: nothing changes around the leader
The third reason is the one organisations find hardest to hear.
A leader can leave a 360 debrief genuinely committed to changing something, and walk straight back into an environment that rewards exactly the behaviour they've just agreed to stop.
If the culture rewards fast decisions, a leader working on consultation will look slow. If the incentive structure is built entirely on individual numbers, a leader working on collaboration is choosing to score worse. If nobody's diary changes, a leader working on being more present has nowhere to put the time.
People are remarkably good at reading what an organisation actually rewards, and how that differs from what it says it values. When those two things disagree, the reward wins, and the 360 becomes an annual ritual of noting the gap rather than closing it.
What actually helps
None of this is an argument against 360 feedback. Used well, it's one of the few tools that shows a leader the difference between their intent and their impact, and that gap is where most leadership development actually lives.
But the report is the start of the process, not the process itself. A few things make the difference:
Diagnose before you prescribe. Before agreeing what a leader should do differently, work out what's actually missing. Is it a clarity problem, a capability problem, a motivation problem, or a resourcing problem? Each of those needs a completely different response, and treating all four as a "development need" guarantees that three of them go unaddressed.
Be honest about what one person can change. Some of what shows up in a 360 belongs to the leader. Some belongs to the team. Some belongs to the organisation. Naming which is which isn't letting anyone off the hook, it's the only way the parts that are individual get the attention they deserve.
Build the skill, don't just name the gap. If the feedback says a leader needs to handle conflict better, the follow-up should involve practising handling conflict, with support, more than once. Awareness is cheap. Capability takes reps.
Change something in the environment. One structural change; a diary, a meeting format, a decision-making protocol, how a result gets recognised, will usually do more for a leader's behaviour than another round of individual coaching. The environment is doing the heavy lifting whether you design it or not.
Make it a conversation, not an event. The single biggest predictor of whether a 360 changes anything is whether anyone talks about it again after the debrief. A three-month check-in costs almost nothing and changes the whole meaning of the exercise.
The uncomfortable bit
Here's the question worth sitting with: if you ran your last 360 process again tomorrow, how different would the results be?
If the honest answer is "not very," that's not a reflection on your leaders. It's a reflection on what the organisation did with what they were told.
The feedback did its job. It surfaced something real. Everything after that is a design choice, and design choices can be changed.
“I think quite a few of us, including me, read some of that 360 feedback and actually thought, ‘Oh my God, I can’t believe they still think I’m like this.’ But actually this is about us learning and growing and taking that feedback on board. It’s a really important part of the journey.”
At T2, we work with leaders and teams on exactly this gap: the distance between knowing what needs to change and being able to make it stick. If your 360 process is producing insight but not movement, we'd be happy to talk about what's getting in the way.