A first-time manager's guide to running 360 feedback
Read more How to Run 360
Not every team is ready for a 360 review, and not every moment is the right one to run one. There are at least five specific situations where a structured 360 will do more damage than good, and in each of them the better move is something smaller, quieter, and aimed at a different problem. This piece is about those situations, and about the alternatives that actually fit them.
I’ll get this out of the way up front: I sell software in this category, so the most distributable thing I can do is tell you when not to use it. Most “should you do a 360” content is written by people whose answer is always yes. Mine isn’t. If you read this and decide to skip a round you were planning, I’ll consider this post a win. If you read it and feel surer about the round you’re already planning, I’ll consider it a win too. The point is to make the call deliberately, not by calendar.
Key Takeaways
- The first question is “what are we trying to learn?” not “should we run a 360?”. Most of the disqualifiers below are situations where a 360 isn’t the right instrument for the actual question.
- During a crisis, layoffs, or a leadership change, a structured 360 produces noise, not signal. Skip-level conversations are the better move until the dust has settled.
- On brand-new teams (under 60-90 days of overlap), responses are impressions rather than observations. A lightweight pulse now and a real round in a quarter beats a real round now.
- If a 360 is being used as a backdoor for a hard conversation the manager doesn’t want to have themselves, recipients see through it and trust collapses. Have the conversation.
- If you ran one last year and nothing changed, the dread is the diagnostic. Skip a year, or change the format radically, before running the same round again.
“When to use 360 feedback” isn’t actually the right first question. The right first question is “what are we trying to learn, and is a 360 the right instrument for that?”. Most of the times a 360 fails, it fails not because the 360 is a bad tool, but because someone reached for it when the underlying question was something else. A team is anxious. A manager is avoiding a conversation. A leader wants validation. A calendar says it’s that time of year.
A 360 review is a development tool, narrowly aimed at giving one person a fuller picture of how their behavior is landing. It’s not a performance management tool, not a conflict resolution tool, not a culture-fixer, and not a yearly ritual. Most of the disqualifiers below are situations where one of those other problems is the real one, and the 360 is being asked to do work it isn’t designed to do.
If the team is in the middle of an acute event, layoffs, a public mistake, a leadership change, a high-profile resignation, this is not the moment. Responses gathered during a crisis are saturated by the crisis. The reviewee gets feedback that reads like a stress test of last week, not an honest read on how they generally work. Recipients on edge focus on the one anxious-sounding comment instead of the pattern.
Imagine a 35-person company that just laid off five people. Three weeks later someone schedules the planned 360 round for the leadership team. What gets surfaced is the laid-off-people anxiety in everyone, not the leaders’ actual behavior. The data is noise.
Instead: do skip-level conversations and one or two targeted 1:1s for the next 30 to 60 days. Revisit the structured round in 90 days, when the responses can be about the work again and not about the event.
Brand-new team, recent reorg, raters with under 60 to 90 days of working overlap with the reviewee. The responses you get back are impressions, not observations. Generic positives (“they seem motivated”) and vague negatives (“not sure yet”) collapse into a deliverable that produces nothing actionable.
The same logic applies inside the first-time manager’s guide to running 360 feedback, where the 60-day timing rule is the most useful single piece of advice for new managers wondering if they can run one yet. Below that threshold the data is just too thin.
Instead: run a lightweight pulse on the working relationship now (one question, written, optional), and schedule the real round in a quarter when raters have lived through something with the reviewee. The waiting period is the most valuable part.
The leader being reviewed has a track record of finding out “who said that”, of going cold on raters whose comments stung, of weaponizing anonymity (“we’ll figure out who wrote this”). The team knows it. They will not be honest, the response set will be cautious to the point of useless, and the few honest raters expose themselves to retaliation.
This is a culture problem masquerading as a feedback question, and a 360 won’t solve it. Building a feedback culture covers the longer-term work that makes upward feedback safe in the first place, and the short version is: leaders go first by modeling that hard feedback gets thanked, not punished.
Instead: skip the upward direction in this round. Run lateral peer feedback only on the team, separately. Or, if you’re senior enough to have the conversation directly, have it. The structured round can come back when the conditions have changed.
Someone on the team is underperforming, or behaving in a way that’s costing the team, and the manager doesn’t want to say it themselves. They hope the 360 will “surface it”, that hearing it from peers will land harder than hearing it from them. This is one of the most common 360 misuses I see, and it has a specific failure mode: the recipient sees through it instantly.
What lands is not the feedback. What lands is the manager’s avoidance. The next time a structured feedback round comes around, trust is below the starting line.
Instead: have the conversation. A direct, specific, prepared sit-down with the person, owned by the manager. Use the 360 later, with this person or others, when the question is genuinely development, not the manager’s discomfort.
The most subtle disqualifier. Last year’s round happened. People filled out the form. A meeting was held. Nothing visibly changed in how the team works or how anyone gets reviewed. The team has filed “360 round” under “compliance ritual” and is bracing rather than growing.
Running the same round again, in the same format, with the same follow-through gap, will produce the same outcome with worse participation. The dread is the diagnostic; the format is the cause.
Instead: skip a year. Or change the format radically: peer-only, two questions, written debrief instead of a meeting, smaller scope. The discipline is breaking the ritual loop, not extending it.
A 360 works when the conditions are mostly the inverse of the disqualifiers above. The team is stable and has shared working history. The recipient has shown they can hear hard things without retaliating. The manager is committed to following through on whatever surfaces. The round is separated from compensation, so honest responses don’t cost anyone their bonus. There’s a small set of well-chosen questions, not forty.
If most of those are true, a 360 is the right call and the practical setup is genuinely small. How to run your first 360 review walks the steps and why 360 feedback matters covers the affirmative case if you want the companion read. The two pieces together make the full argument: when conditions are right, run one; when they aren’t, do something else.
A 360 is a tool, and tools have conditions. The discipline isn’t running one whenever the calendar says it’s that time, it’s choosing not to run one when the conditions aren’t there yet. Saying “not this team” or “not this quarter” is the most senior move available to whoever owns the process, and the team will trust the next round more because of it.
The worst version of a feedback program is the one that runs on autopilot regardless of what’s happening underneath. The best is the one that knows when to wait.
If you’ve worked through the disqualifiers and you’re in a situation that genuinely fits, start your first 360 in Lynxify, no annual contract, no credit card required. Or run it manually with a shared document and a few questions; either way, the choice to run one is more important than the tool you run it with.
When not to use 360 feedback?
Skip a 360 when the team is in the middle of a crisis or major transition, when raters have less than 60 to 90 days of overlap with the reviewee, when the leader being reviewed has a track record of punishing honest feedback, when the round is being used as a backdoor for a conversation the manager should be having directly, or when last year’s round produced no behavior change and the format hasn’t been rethought.
Is 360 feedback a bad idea for small teams?
Not inherently, but small teams have specific constraints. Anonymity is largely a polite fiction when there are only two or three peers per person, and the multi-source value of a 360 shrinks when the sources are also small. For teams of 1 to 3 people, a structured 1:1 with the right questions often delivers what the 360 would, with less overhead.
What can you do instead of a 360 review?
Match the alternative to the actual question. For a team in crisis, skip-level conversations and targeted 1:1s. For a new team, a lightweight pulse plus a delayed real round. For an unsafe leadership situation, lateral peer feedback only or a direct conversation. For a manager avoiding a hard conversation, the direct conversation itself. For ritual fatigue, a skipped year or a radically different format.
When is the right time to run a 360 review?
The right time is when the team has shared working history (at least a quarter together), the recipient can absorb hard feedback without retaliation, the manager is committed to following through, the round is separate from compensation, and there’s a tight set of well-chosen questions. If most of those conditions are true, run one. If most aren’t, do something else first.
Dmytro Shtapauk
Practical tips and experience from top-notch experts
