360 feedback done well

Key takeaways

• 360 feedback works when the purpose is development, not judgement. Get that purpose wrong and everything downstream, who you ask, how you frame it, what happens with the results, goes wrong too.
• Choose reviewers for what they'll actually see, not just seniority. A good 360 includes peers and, where relevant, direct reports, not only the manager.
• Frame questions around specific behaviours, not vague traits. "Do they follow through on commitments" beats "are they a good communicator" every time.
• The results are the start of a conversation, not the end of the process. Feedback that never turns into action was never worth collecting.
• The most common failure is treating 360 feedback as a rating exercise dressed up in development language. People can tell the difference, and it costs you their honesty next time.

A client once showed me a 360 report that ran to eleven pages, colour-coded and beautifully produced. She'd read it once, felt vaguely bad about herself for a week, and never opened it again. That report cost real money and changed nothing.

That's the risk with 360 feedback done badly. Done well, it's one of the most useful tools a leader can have. Here's the difference.

Start with the purpose, because everything follows from it

The single decision that determines whether a 360 process works is whether it's built for development or for judgement.

A development-focused 360 asks: what does this person need to see about themselves to grow? It's confidential and forward-looking, and the person receiving it decides what to work on and who helps them.

A judgement-focused 360 asks: how should we rate this person? It feeds into a decision, a rating, a promotion call, a pay outcome, and everyone involved knows it. The moment reviewers suspect their honest answer might affect someone's pay or job, the answers get softer and less useful. That's not cynicism. It's a reasonable response to the stakes you've created.

You can run a 360 for either purpose. You cannot run one that quietly tries to do both, because the incentives contradict each other. Decide first, then design everything else around that.

Who to include, and why it isn't just "pick senior people"

A 360 is only as good as the range of people giving it. Include only the manager's view and you've built an expensive one-on-one with extra steps.

A well-built reviewer group usually includes:

• The manager, for the strategic and performance view.
• Peers, who see how someone operates day to day in a way a manager often doesn't.
• Direct reports, where relevant, because how someone leads their team is exactly the thing they can't self-assess.
• The person themselves, so you can compare self-perception against how others experience them. That gap is often the single most useful piece of data in the process.

Aim for enough reviewers that no individual answer is identifiable, and be upfront with participants about that threshold. People write more honestly when they trust their name isn't attached to a specific comment.

How to frame it so the answers are actually useful

Vague questions produce vague, unusable answers. "Is this person a strong leader" gets you a number and nothing to act on. Behaviour-specific questions get you something real.

• Instead of "are they a good communicator", try "do they explain decisions in a way that makes sense, even when people disagree with them?"
• Instead of "are they collaborative", try "do they bring other people's ideas into their own thinking, or mostly defend their original position?"
• Instead of "are they a good leader", try "when things go wrong on their team, do they take it on, or does it land somewhere else?"

Specific questions give reviewers something concrete to answer honestly, and give the person something concrete to act on. "Be more collaborative" is a slogan. "Bring other people's ideas into your thinking before you land on a decision" is instructions.

Turning results into action

This is where most 360 processes quietly die. The report gets produced, the person reads it, and nothing structured happens next.

Debrief it with someone, not alone. A skilled coach or manager, reading the report with the person, catches patterns they might defend against or miss on their own. Reading it alone at your desk is how you end up feeling bad for a week and changing nothing, like the example I opened with.

Pick two or three things, not everything. A report with fifteen development areas produces zero development areas, because nobody can hold fifteen priorities. Pick the two or three that matter most, ideally the ones raised by multiple reviewers, and put the rest aside for now.

Connect it to ongoing conversations. A 360 pays off when it feeds regular coaching conversations afterwards, not a one-off action plan filed and forgotten. See coaching conversations that replace the annual review and continuous performance: beyond the annual review for how that rhythm works.

Close the loop with reviewers. A simple "here's what I'm working on based on what I heard" tells people their honest feedback mattered. Skip this and you'll get thinner answers next time.

Failure modes to avoid

I've seen the same handful of things sink an otherwise well-intentioned 360 process, over and over.

• Treating it as a rating exercise in disguise. If results feed into pay or promotion while you're calling it developmental, reviewers work that out fast, and the honesty disappears.
• Too few reviewers. Below a certain number, anonymity is theoretical, and people write for an audience they can identify.
• No follow-up. A report that goes nowhere teaches everyone the process doesn't matter, which makes the next round harder to get honest input for.
• Running it too often. A 360 asks a lot of people's time and honesty. Run it constantly and it becomes background noise, answered on autopilot.
• Vague, trait-based questions. "Is this person a good leader" gets you an opinion. A specific behavioural question gets you something a person can actually change.

Avoid these and a 360 becomes one of the most reliable ways to see yourself clearly. Keep tripping over them and it becomes an expensive ritual nobody quite believes in.

We built Whyser Work's performance module to hold that follow-up, so the two or three priorities from a 360 sit alongside a person's goals and their coaching conversations, not filed away as a PDF nobody reopens.

Frequently asked questions

How often should 360 feedback be run?

Once a year is common, and for most people, more than that starts to feel like a burden on their reviewers. What matters more than frequency is what happens afterwards. A 360 followed by real, ongoing coaching conversations is worth more than a more frequent process that never turns into action.

Should 360 feedback be anonymous?

Generally yes, with enough reviewers that individual comments can't be traced back to a person. Anonymity, done properly, is what gets you honest answers instead of diplomatic ones. Be transparent about how confidentiality is protected, because trust in the process is what makes the feedback worth collecting.

Who should see the full 360 report?

In a development-focused process, the person themselves, and usually their manager or coach to help interpret it. Wider access should be limited and agreed upfront, because the moment people suspect their feedback might travel further than expected, the honesty of future rounds drops.

What if the feedback contradicts what the person believes about themselves?

That gap is often the most useful thing a 360 reveals. It's worth sitting with, ideally with someone skilled at debriefing it, rather than dismissed or over-corrected for. A pattern that several reviewers independently noticed is worth taking seriously, even when it's uncomfortable to read.

If your last round of 360 feedback changed how someone actually leads, that's a process working. If it just produced a report that got read once and filed, what would it take to fix that before you run it again?