360 feedback questions that actually surface blind spots
Read more 360 Reviews
Most teams put off their first 360 review for the same reason: it feels like a project.
You picture spreadsheets. Scheduling. Chasing people for responses they keep forgetting to submit. Then somehow turning a pile of raw, contradictory comments into something fair and useful. So it sits on the someday list, quarter after quarter, while everyone quietly agrees it would probably be a good idea.
Here’s the thing I learned after running these at a few companies: the project part is mostly self-inflicted. A first 360 review doesn’t need a rollout plan or a steering committee. It needs five people, a few good questions, and a willingness to start. This guide walks you through exactly that: the version I’d run if I were doing it for the first time tomorrow.
Key Takeaways
- A 360 review collects structured feedback on one person from their manager, peers, and direct reports. It works best as a developmental tool, not a performance rating tied to pay or promotion decisions.
- Five to seven well-chosen raters outperform a large group. The test is whether they have enough direct, recent experience to say something specific, not just whether they know the person.
- Three or four open-ended questions are enough. The four in this guide are ready to steal verbatim. A thirty-question form has lower completion rates and less useful output.
- Anonymity is a deliberate decision, not a default. In small teams it’s often a polite fiction, and the wrong setup is worse than no anonymity at all.
- The synthesis step is the part that doesn’t scale by hand: turning raw responses into a themed summary takes two to three hours per person, manageable for one or two people and unsustainable for eight or more every quarter.
A 360 review collects feedback on one person from the people around them: their manager, a few peers, and if they manage others, some direct reports. That’s the whole idea. Instead of one person’s opinion (usually the manager’s), you get a fuller picture from the people who actually work with them.
What it isn’t: a performance rating, a promotion decision, or a disciplinary tool. The moment a 360 becomes the input to someone’s raise, people stop being honest, and you’ve broken the only thing that made it valuable. Keep your first 360 developmental. It’s about helping someone see themselves more clearly, not deciding their fate.
If you remember one thing from this guide, remember that distinction. It’s the difference between a 360 that builds trust and one that quietly poisons it. For the fuller case for why this format is worth running at all, see why 360 feedback matters for growing teams.
The instinct is to invite everyone. Resist it.
For each person being reviewed, pick five to seven raters: their manager, three or four peers who work with them regularly, and (if they lead a team) two or three direct reports. The test for including someone is simple: do they have enough direct, recent experience with this person to say something specific? If they’d be guessing, leave them out. Five people with real observations beat fifteen people offering vague impressions every time. The number that keeps showing up in practice is six: enough perspectives to find a pattern, small enough that the process stays manageable.
One more thing on direct reports: when someone reviews their own manager, their feedback has to be anonymous or aggregated, or it won’t be honest. Nobody tells their boss the unvarnished truth with their name attached. We’ll come back to anonymity in a moment.
The most common mistake in a first 360 is asking too much. A thirty-question form feels thorough when you build it and feels like a punishment when someone has to fill it out for six different colleagues. Completion rates collapse, and half-finished feedback is worse than none.
Keep it to three or four open questions. Here are the ones I use, and you’re welcome to steal them word for word:
What is this person doing well that they should keep doing? Be specific. Give an example if you can.
What is one thing this person could do differently that would make the biggest positive difference?
How effectively does this person communicate and collaborate with you? What would make it better?
Is there anything else you think they should know?
That’s it. Four questions, all open-ended, all focused on behavior the rater has actually observed. You’ll get more useful signal from four good open questions than from a forty-item rating scale.
If you want a starting point with more variety, questions tuned for individual contributors, managers, and senior folks, I’ll cover that in a dedicated post on 360 feedback questions. For a first run, the four above are plenty.
This is the decision people get wrong most often, usually by not deciding at all.
For peer and direct-report feedback, anonymity usually produces more honesty, especially the first time, when trust in the process hasn’t been established yet. People are more willing to name a real problem when their name isn’t on it.
But anonymity has a cost. Anonymous feedback can be vaguer, occasionally crueler, and harder to follow up on. And in a small team, “anonymous” is often a polite fiction: if there are only two peers, the person being reviewed can usually guess who said what.
For a first 360 at a small company, I’d lean toward anonymous peer and direct-report feedback, with the manager’s feedback attributed. That gives you honesty where you need it most and accountability where it’s safe. Whatever you choose, tell everyone clearly before they start. The worst outcome is someone assuming their feedback was anonymous when it wasn’t.
The harder version of this question is whether people feel safe enough to say honest things at all. Building a genuine feedback culture is the longer-term work that makes the anonymity decision easier and the responses more useful when they come in.
Feedback makes people anxious, both giving it and receiving it. A good kickoff message defuses that. Send it five business days before the deadline, and say four things: what this is, what it’s for, that it’s developmental and not tied to pay or promotion, and when it’s due.
Here’s a version you can adapt:
“Hi everyone, we’re running a short 360 feedback round for [name]. The goal is simple: help them see what’s working and where they can grow, from the perspective of the people they work with. This is developmental; it’s not tied to compensation, ratings, or promotions. Peer and direct-report responses are anonymous. It’s four short questions and should take about ten minutes. Please complete it by [date]. Thank you; honest, specific feedback is genuinely useful here.”
One more thing on timing: five business days is enough, but set a firm deadline. “Whenever you have a moment” means half your responses arrive the day before you need them and half don’t arrive at all.
Notice the last line of the message does quiet work: it signals that specific honesty is what’s wanted, not safe platitudes.
When responses come in, do not paste the raw text into a document and hand it over. A pile of unprocessed comments (some glowing, some harsh, some contradictory) lands like a gut punch, and the person fixates on the one negative line instead of the pattern.
Your job is to find the patterns. Read everything, then write a short summary organized around themes: two or three clear strengths, two or three development areas, with representative examples under each. If three people independently mention the same thing, that’s signal. Say so. If one person said something sharp that nobody else echoed, weight it accordingly or leave it out.
This synthesis step is the difference between a 360 that helps and one that hurts.
Imagine a People Ops lead at a 50-person company running structured feedback for eight people at once. She collects responses across three rounds of email reminders, opens each batch in a shared document, and spends most of a Friday afternoon reading, theming, and writing summaries before she can have a single development conversation. For eight people, that’s roughly a full day of synthesis before the useful part begins. That’s not a process failure; it’s simply what this step costs when you’re doing it by hand at that scale. If you’re doing this for several people regularly, see how Lynxify handles the synthesis step. That’s the specific friction a focused tool is built to remove.
Set up a real conversation: thirty minutes, not an email with a document attached. Walk through the strengths first and let them land. People skip past their strengths to get to the criticism, so slow down here. Ask them to say something specific back, not just “thanks,” so the positive feedback actually registers. The development areas land better when the person already feels seen rather than braced.
Then move to the development areas, framed as opportunities, with the specific examples from the responses.
End with one question: “What’s one thing from this you want to work on?” One. Not five. A 360 that produces a single, owned, specific commitment has done its job. A 360 that produces a twelve-point improvement plan produces nothing.
Notice what this took: five people, four questions, a kickoff message, an afternoon of synthesis, and a thirty-minute conversation. No software, no implementation project, no budget approval. The hard part was never the logistics. It was deciding to start, and doing the human parts (synthesis and delivery) with care.
That said, the parts that don’t scale are real. Doing this for one person is an afternoon. Doing it for eight or ten, while chasing responses and synthesizing by hand every quarter, is a second job. That’s the point where a focused tool earns its place: not to replace the human judgment, but to remove the logistics so you can spend your time on the parts that actually matter.
If you’ve outgrown the spreadsheet version but a full performance platform feels like overkill, that’s exactly the gap Lynxify was built for. But run your first one however you like. The best 360 process is the one you actually start.
How do you run a 360 review step by step?
Pick five to seven raters who have direct, recent experience working with the person being reviewed. Write three to four open-ended questions rather than a long rating scale. Decide deliberately whether feedback will be anonymous and communicate that clearly to everyone before they start. Send a kickoff message five business days before the deadline, explaining that the process is developmental and not tied to compensation. Collect responses, synthesize them into a short themed summary, then deliver results in a real thirty-minute conversation. The whole 360 feedback process, from setup to delivery, typically spans one to two weeks for a single person.
How many questions should a 360 review have?
Three or four open-ended questions is the right number for most teams. More questions feel thorough when you’re writing them and feel like a burden to the people filling them out, especially when they’re completing feedback for multiple colleagues at once. Completion rates drop noticeably past ten questions, and response quality declines as fatigue sets in. The four questions in this guide cover what someone needs to know: what they’re doing well, what to change, how they’re landing with colleagues, and anything else worth naming. That’s enough to have a real development conversation.
Should 360 feedback be anonymous?
Usually yes for peer and direct-report feedback, especially in a first round before trust in the process is established. Anonymous responses tend to be more specific and honest when people aren’t sure how their feedback will be received. The practical exception is small teams: if someone has only two peers, “anonymous” is effectively transparent regardless of what you promise. For manager feedback on direct reports, attribution is usually fine. Whatever you decide, the key rule is to tell people clearly before they start. Discovering after the fact that responses weren’t as private as assumed does more damage than any piece of feedback would.
How long does a 360 review take?
Setting up the process takes about fifteen minutes: choosing raters, writing questions, and sending the kickoff message. Collecting responses usually takes about a week with one reminder at the midpoint. Synthesizing the results takes two to three hours per person reviewed. Delivering results takes about thirty minutes per person. Total organizer time for a single person: roughly three to four hours spread over one to two weeks. Running it for eight people at once, by hand, runs to two or three full days of synthesis before any development conversations begin.
Do you need software to run a 360 review?
No. Everything in this guide can be done with email and a shared document. For a first round covering one or two people, that’s usually the right choice: no new tools to learn, and you build a real understanding of the process before adding automation. The point where manual stops working is when you’re running reviews for six or more people simultaneously, or when you want to make it a consistent quarterly rhythm. At that point, the synthesis step alone becomes a significant ongoing time cost. If you’re at that stage, start your first structured 360 in Lynxify, no annual contract, no credit card required.
Dmytro Shtapauk
Practical tips and experience from top-notch experts
