360-Degree Feedback: How to Design, Run and Use It for Development

360-degree feedback gives people a richer picture of how they are seen at work than any single manager can provide. It can accelerate leadership development, improve collaboration and surface issues before they become problems. It can also go badly wrong — anonymous criticism without context, surveys that feel like popularity contests, or results used for pay decisions they were never designed for. This guide explains how 360 feedback works, when to use it, how to design questions, how to protect anonymity, how to deliver results and how to turn them into development.

What is 360-degree feedback?

360-degree feedback, also called multi-rater feedback, is a process in which an employee receives confidential feedback from people around them — typically their manager, peers, direct reports and sometimes external stakeholders — and compares it with their own self-assessment. Feedback usually combines ratings on specific behaviours with written comments.

The name reflects the full circle of perspectives. A manager sees results and how someone handles upward relationships; peers see collaboration and reliability; direct reports see leadership in practice. Differences between these views — and between others’ views and the person’s self-perception — are often the most useful insight. 360 feedback complements, rather than replaces, regular manager feedback and the performance review process.

Should 360 feedback be used for development or evaluation?

Most experts recommend using 360 feedback mainly for development. When ratings feed into pay, promotion or performance ratings, raters become more cautious or political, employees become defensive and the quality of feedback falls. Development-focused 360s produce more honest feedback and more change.

Some organisations use 360 input as one data point in performance discussions, especially for leaders, where how results are achieved matters as much as the results themselves. If you do this, be transparent about it from the start, keep it as one input among several, and never use individual comments or raw scores mechanically. Our guide to performance calibration explains how multiple inputs can be combined fairly.

Who should participate in a 360 review?

360 feedback is most valuable for managers, leaders and senior individual contributors whose roles depend on influence and collaboration. Each participant typically chooses or agrees five to twelve raters across groups, with enough people in each group — usually at least three — to protect anonymity.

The participant should propose raters who have worked closely with them recently, including people who will offer a balanced or critical view, not only allies. The manager reviews the list to make sure it is representative. Avoid running 360s for everyone at once; it overloads raters, who may be asked to complete many surveys in the same week. Prioritise new managers, leaders in development programmes and people who request it.

How do you design good 360 questions?

Base questions on a clear competency or leadership framework and focus on observable behaviours, not personality traits. Use a consistent rating scale, keep the survey short enough to complete in 10–15 minutes and include two or three open questions that invite specific, constructive comments.

Useful open questions include: “What should this person continue doing?”, “What could they start doing to be more effective?” and “What could they stop or do less of?” Ask raters to give examples. Avoid double-barrelled questions that combine two behaviours, and include a “not observed” option so raters do not guess.

How do you protect anonymity and confidentiality?

Report ratings only for rater groups with a minimum number of respondents — commonly three — combine smaller groups, present comments without names, remove identifying details where possible and restrict access to reports. The manager’s feedback is often shown separately, since it cannot be anonymous.

Explain clearly to raters how their input will be used, who will see the report and how anonymity is protected. Data protection rules apply, especially if feedback is stored in HR systems; see our GDPR for HR guide. Specialist 360 platforms or the 360 modules of performance management software handle thresholds and anonymisation automatically; our performance management software comparison covers the options.

How should 360 results be delivered?

Deliver results in a one-to-one debrief with a trained coach, HR partner or skilled manager, not by simply emailing a report. The debrief helps the participant interpret patterns, recognise strengths, understand gaps between self and others’ ratings, manage emotional reactions and identify two or three development priorities.

A good debrief starts with strengths, then looks for themes rather than individual scores, explores the biggest gaps between self-perception and others’ views, and treats surprising comments with curiosity rather than defensiveness. Participants often focus on the one negative comment among many positive ones; the debriefer helps keep perspective. End with agreed priorities and next steps.

How do you turn 360 feedback into development?

Agree a short development plan with two or three priorities, specific actions — practice, coaching, training, stretch assignments — and a timeline. Encourage the participant to thank raters and share their priorities, which builds support. Revisit progress in one-to-ones and consider a follow-up pulse after six to twelve months.

The 70-20-10 model is a useful guide: most improvement comes from deliberately practising new behaviours on the job, supported by feedback and coaching, with formal learning playing a smaller role. Our guides on coaching and mentoring and leadership development programs explain how to support this. The participant’s manager plays a key role in reinforcing change through regular one-on-one meetings.

How do you introduce 360 feedback to an organisation?

Start with a clear purpose — usually leadership development — and pilot with a group that volunteers or is part of a development programme. Explain the process to participants and raters in advance, train debriefers, and gather feedback on the experience before expanding. Senior leaders going first sends a powerful signal.

Communication matters. Raters need to know why their input is requested, how long it will take, how anonymity is protected and how feedback will be used. Participants need to understand that the goal is development, how the debrief will work and what support they will receive. Avoid launching 360s during periods of restructuring or major change, when trust is fragile and feedback may reflect wider anxieties rather than individual behaviour.

Evaluate the pilot: completion rates, rater feedback on the survey, participant views on usefulness and, after some months, whether development priorities were acted on. Use the findings to refine questions and processes before rolling out more widely.

How should raters give useful 360 feedback?

Raters should focus on observed behaviour, be specific, balance strengths and development areas, offer examples and suggestions, and avoid personal attacks or speculation about motives. A short guide for raters, with examples of helpful and unhelpful comments, significantly improves feedback quality.

Encourage raters to complete surveys when they have uninterrupted time, rather than rushing through many at once. Quality matters more than speed.

How do 360 results differ for leaders at different levels?

For first-line managers, 360 feedback often highlights basics: clarity of expectations, regular feedback, fairness and availability. For senior leaders, themes shift towards strategic communication, building trust across functions, developing other leaders and creating a healthy culture. Tailor competency frameworks and questions to the level.

Senior leaders also face a specific challenge: people may be reluctant to give them honest feedback. Strong anonymity, a credible external debriefer and visible commitment from the leader to act on results help. When senior leaders share their own development priorities openly with their teams, it encourages candour throughout the organisation.

What does a 360 development plan look like?

A 360 development plan lists two or three priorities drawn from the feedback, specific behaviours to practise, the support needed — coaching, mentoring, training or stretch assignments — and how progress will be checked. It should fit on one page and be revisited regularly with the manager or coach.

For example, a manager whose feedback shows strong delivery but limited delegation might commit to handing over two recurring responsibilities to team members within a quarter, using a simple delegation checklist, and asking the team for feedback after three months. Concrete, observable commitments make change visible and give raters a reason to notice progress in the next round.

Which tools can run 360 feedback?

Dedicated 360 platforms, performance management suites and some engagement tools offer 360 modules with rater selection, reminders, anonymity thresholds, reports and development planning. Small organisations can run simple 360s with survey tools, provided anonymity is handled carefully.

Look for flexible question libraries, clear reports that highlight themes and gaps, integration with your HRIS, data-protection controls and support for debriefers. Our performance management software comparison covers suites with built-in 360 capability.

Whichever tool you choose, pilot it with a small group first and ask participants and raters how easy it was to use before scaling up.

Check that participants can access their own reports easily and that reports remain available for later development conversations.

Frequently Asked Questions