A 360-degree review gathers feedback on a leader from the people around them, including their manager, peers, direct reports, and sometimes external stakeholders, rather than relying on a single top-down evaluation. Done well, it gives leaders a view of themselves they can’t get any other way. Done badly, it becomes a box-ticking exercise that erodes trust and changes nothing.
This guide walks through how to run one properly, what to avoid, and how to make sure the feedback actually leads to better leadership.
What a 360 review is, and what it isn’t
A 360 review measures how a leader behaves, as seen from multiple perspectives. It is a development tool. It works because the people who experience a leader’s behavior daily, including the team they manage and the peers they negotiate with, often see patterns the leader themselves cannot.
It is not a performance appraisal, and the fastest way to ruin a 360 program is to treat it like one. The moment employees believe their feedback will determine someone’s bonus or promotion, candor disappears and the data becomes worthless. Keep 360 reviews separate from formal performance and pay decisions, and say so explicitly to respondents.
Step 1: Decide what you’re actually measuring
Before anyone fills in anything, define the leadership behaviors and competencies you want to assess. Generic questionnaires measure generic things. If your organization values, say, “developing others” or “decisiveness under pressure,” the review should measure those, not a borrowed list that has nothing to do with how leadership works in your business.
Write this down as a competency framework before you do anything else. Every question in the review should map back to one of these competencies.
Step 2: Choose the right respondents
A useful 360 needs enough perspectives to be balanced, but not so many that it becomes a logistics problem.
A practical range is roughly 8 to 18 respondents per leader, including the leader’s own self-assessment. A typical mix:
- The leader (self-assessment)
- Their direct manager
- 3–5 peers
- 3–5 direct reports
- 0 or 3+ other stakeholders (internal clients, cross-functional partners). This category is optional, but if you include it, use at least 3 so individual responses stay anonymous.
A rule worth applying across the board: any feedback category should have at least 3 respondents. Below that, individual answers become identifiable and people stop being candid. The leader and their direct manager are the two exceptions, since those ratings are not anonymous by nature.
Beyond the numbers, respondents should be chosen for genuine working proximity, not friendliness. A 360 stacked with allies tells you nothing.
Step 3: Ask questions that produce useful answers
Good 360 questions are behavioral and specific. “Is this person a good leader?” produces noise. “How effectively does this person give clear direction when priorities change?” produces something a leader can act on.
Combine two question types:
- Rating questions (quantitative), which let you compare across competencies and spot perception gaps between how the leader rates themselves and how others rate them.
- Open-text questions (qualitative), which capture the “why” behind the ratings and the specific examples that make feedback land.
The gap between self-perception and others’ perception is often the single most valuable output of the whole exercise.
Step 4: Protect anonymity and explain the purpose
Tell every respondent, before they start: who the feedback is for, that it’s for development rather than punishment, and how their anonymity is protected. People give honest, useful feedback only when they trust how it will be used. A two-line framing message at the start of the questionnaire materially improves the quality of what you get back.
Step 5: Don’t hand over the report and walk away
This is where most 360 programs fail. The leader receives a detailed report, feels briefly exposed or defended, files it, and changes nothing.
A report is data, not development. The value comes from a structured debrief, ideally with a coach or trained facilitator, that helps the leader interpret the feedback without becoming defensive, separate signal from noise, and turn two or three themes into concrete behavior changes. Feedback without a follow-up conversation is one of the most common reasons 360 reviews fail to produce any change.
Common mistakes that quietly sink a 360 program
- Using it for performance or pay decisions. Destroys candor. Keep it developmental.
- Too few respondents. Three responses isn’t a 360; it’s gossip with a spreadsheet.
- Generic questions. If the review isn’t tied to your own leadership competencies, the results won’t be either.
- No debrief. The report is the start of the work, not the end of it.
- Running it once and stopping. A single 360 is a snapshot. Re-running it 9 to 12 months later is what shows whether anything actually changed.
Making the process easier
Running all of this manually, including building the framework, distributing questionnaires, chasing responses, and aggregating ratings and written comments into a readable report, is where most HR teams lose time and momentum.
This is the problem CoreVision360 was built to solve. It’s Onward’s proprietary 360-degree feedback assessment: you nominate the respondents, the questionnaire is tailored to your organization’s leadership competencies, and the report (combining quantitative ratings and qualitative feedback) generates automatically once everyone has responded. Because Onward also delivers executive coaching, the debrief in Step 5 can be built straight into the engagement, so the feedback actually turns into changed behavior.
If you’re planning a leadership development cycle and want to see what a structured 360 report reveals, you can request a CoreVision360 demo.