How to Run a 360 Review: Step-by-Step

Before you set up anything, be clear on why you're running this 360. Is it for individual development? Leadership coaching? Succession planning? The purpose determines who should be evaluated, how many raters to include, and how you'll use the results.

Also decide on scope: Are you running this for one person, a team, or the entire organization? Start small if this is your first time — one person or a small cohort is easier to manage and gives you a chance to learn the process before scaling.

360 feedback works for any role, but it's most valuable for people whose effectiveness depends heavily on working with others — managers, team leads, senior individual contributors, and executives.

If this is a pilot, pick someone who is open to feedback and genuinely curious about their development. A successful first evaluation makes it easier to roll out the process more broadly.

Rater selection is critical. Poor rater selection produces meaningless data.

Guidelines: - Manager: 1 person (their direct manager) - Peers: 3–5 people who work closely with the subject - Direct reports: 3–5 (if applicable) — never fewer than 3 to protect anonymity - Self: always include

Avoid: close friends who will only give positive feedback, people who have had recent conflicts and might be biased negatively, or people who rarely interact with the subject.

Ideally, the subject should have input into rater selection, but a manager or HR should have final approval.

Communication before the survey launches dramatically improves response rates and data quality.

For the subject: Explain the purpose (development, not rating). Tell them who their raters are and when they'll receive the survey. Set expectations about what the report will look like.

For raters: Explain that their responses are anonymous. Tell them the survey takes 10–15 minutes. Emphasize that honest, specific feedback is more useful than polite, vague feedback. Give them a clear deadline.

If you're using 360Feedbacks, this takes under 5 minutes. Create the evaluation, add the subject's information, invite raters by email with their category (manager, peer, direct report), and set a deadline.

Raters receive a unique link and can respond without creating an account. All responses are anonymous.

Recommended timeline: give raters 10–14 days to respond. This is enough time to be thoughtful without letting it drag on.

Track who has responded and send reminders to non-respondents at the midpoint and 2–3 days before the deadline.

A simple message: "Just a reminder that the 360 feedback survey for [Name] closes on [Date]. It takes about 10–15 minutes. Your input is valuable and anonymous."

With 360Feedbacks, reminders are sent automatically — you don't need to chase anyone manually.

When all raters have responded, the report is generated automatically. Before sharing it with the subject, review it yourself.

Look for: unusually low scores in any category, significant gaps between self-perception and rater scores, and patterns in the qualitative feedback. This prepares you to guide the development conversation effectively.

Also check: are there any responses that seem outlier-level extreme? While rare, occasionally a single rater submits clearly biased responses. If one category has scores dramatically different from all others, flag it for context in the conversation.

This is the most important step. A well-designed 360 process with no follow-up conversation is a waste of everyone's time.

Schedule a dedicated 1-on-1 — at least 60 minutes. Start by asking the subject how they feel about the feedback before offering your interpretation. Let them process it.

Focus the conversation on: 1. Strengths — what the feedback confirms they're doing well 2. 1–2 development areas — not everything, just the highest-impact items 3. Specific behaviors — not "improve communication" but "give more frequent project updates to your team" 4. A 90-day action plan — concrete, measurable, followed up on

Set a follow-up in 30–60 days to check in on the development plan. Ask: What have you tried? What's been hard? What support do you need?

This follow-up signals that the feedback matters and that you're invested in their development — not just running a process for its own sake.

At the next 360 cycle (typically 6–12 months later), you'll be able to see whether the development actions have resulted in changed perceptions from raters. This closing of the loop is what separates 360 feedback programs that create real change from those that don't.

The most common failure. If people complete a 360 survey and nothing changes, they'll be skeptical the next time you ask them to participate.

More than 10 raters creates survey fatigue and dilutes the signal. 5–8 total raters is optimal for most roles.

Emailing the PDF without a guided debrief is a mistake. People need help interpreting the data, especially if it contains feedback they weren't expecting.

If you're using 360 feedback to build a case for firing or demoting someone, you're misusing the tool. It's a development instrument, not an HR paper trail.

Run your first 360 review in 5 minutes

Everything in this guide, automated. Free to start.