360 reviews for managers
The distance between how a manager thinks they lead and how their team actually experiences them is where most management problems live. A 360 is the cleanest way to measure that distance.
Direct reports rarely tell a manager the unfiltered truth to their face, and skip-levels only catch it once it has become a retention problem. Anonymous, multi-source feedback surfaces it while it's still fixable.
Why a 360 matters for managers
The feedback flows one direction otherwise
Managers give feedback constantly and receive almost none from the people they manage. A 360 is often the first structured signal a manager gets about their own leadership.
Delegation and trust show up here first
The gap between 'I empower my team' and 'they wish I'd let go' is one of the most common patterns in manager 360s — and one of the hardest to see from the inside.
It catches drift before it calcifies
Small habits (interrupting, deciding too fast, going quiet under pressure) compound into a reputation. Feedback catches them while they're still habits, not identity.
Questions worth asking
- 01When this person delegates, do you feel trusted with the outcome or managed through the details?
- 02How does this manager respond when you bring them a problem or push back on a decision?
- 03Where does this manager create clarity for the team, and where do things stay ambiguous?
- 04What does this manager do that you'd want every manager here to do?
- 05What's one thing this manager could stop doing that would make the team better?
Common pitfalls
Running it as evaluation, not development
If the team suspects the results feed a rating or a comp decision, candor drops and the whole exercise is worth less. Be explicit that it's for growth.
Too few reviewers to stay anonymous
With only two or three responses, a manager can guess who said what — which kills honesty. Aim for enough voices that no single quote is traceable.
FAQ
How many people should give feedback in a manager's 360?
Enough that responses stay genuinely anonymous — typically the manager's direct reports plus a few peers and their own manager, usually 6 to 12 people.
Should a manager's own boss see the raw feedback?
For a development-focused 360, no. The manager should own their report; sharing raw feedback upward turns it into evaluation and suppresses candor next time.
How often should managers run a 360?
Once or twice a year is plenty. Run it, build a short plan from it, work the plan, and re-measure — annual cadence lets change actually show up.
Run a 360 for managers
360Growth turns anonymous feedback into an AI-synthesized Growth Guide in days — not weeks of manual work.