360 feedback questions by role: ICs, managers, and senior leaders
Read more Questions & Templates
If you’re a first-time manager wondering whether you can run a 360 feedback round on your own small team, the short answer is yes, and the version that fits you is much smaller and less scary than the internet makes it sound. You don’t need HR, you don’t need a 50-person rollout plan, and you don’t need to wait until you feel ready. The article you’re reading exists because almost every guide on 360 feedback for first time managers is written for a People Ops lead at a 500-person company, and that’s not your situation.
Two things to disambiguate up front. There are actually two different first 360s a new manager runs: one on yourself (asking your report and a few peers for feedback on how you’re doing as a new manager), and one on your direct report (running a development-focused 360 to help them grow). Both are normal. Both are worth doing. The decisions and the worries overlap, and this piece covers both. If you want the audience-neutral six-step mechanical version, the cornerstone how to run your first 360 review lays it out plainly, and you can read this piece alongside it for the new-manager-specific stuff.
Key Takeaways
- You can run a 360 as a first-time manager. Wait until you’re past about 60 days in role, then either direction (on yourself or on your report) is fair game.
- The right scale for a team of 1-3 people is 3-4 raters total, not the 5-7 the SERP keeps recommending.
- Asking your direct report for feedback on you doesn’t damage your authority. The opposite, with one exception: asking and then ignoring or punishing the answer.
- “Harsh” feedback from a report is almost never as catastrophic as the anxiety predicts. The worst case is silence, not criticism.
- Contradictory feedback isn’t a problem, it’s a pattern. Find what most raters agree on first, then weigh outliers honestly.
Probably yes. The one timing caveat: give yourself about 60 days in role before you run one. Before that point, you and your team don’t have enough shared history yet for the responses to be useful. After 60 days, the data is real enough to act on, and the act of asking for feedback this early signals to your team that this is going to be the kind of working relationship where hard things get said in the open.
Which direction first depends on what’s worrying you more. If you feel uncertain about how you’re landing as a new manager, run it on yourself first. The act of asking, “How am I doing as your manager so far?” and then listening well is one of the most useful moves available at this stage. If your report is the one stuck or struggling, run a developmental 360 for them with a small set of raters. Both are valid first 360s; you don’t have to pick the “more advanced” one. Start with the version that fits the actual problem in front of you.
Most 360 advice assumes 5-7 raters per person. That advice is correct for a 50-person company and wrong for yours. For a brand-new manager with one or two direct reports, the practical rater count is 3-4 total: your direct report (or the person being reviewed), one or two peers who actually work with the subject closely, and the subject’s manager (which is you or your own manager, depending on the direction).
A note on anonymity at this scale: when your team is small, “anonymous” is partly a polite fiction. If you have two peers reviewing you, you’ll usually be able to guess who said what. Don’t pretend otherwise, and don’t promise an anonymity you can’t deliver. The fuller version of this trade-off is in anonymous feedback at small companies, but the short version for your situation: peer and direct-report responses can stay un-attributed in the synthesis, and most reviewers know that, and most still respond honestly when they trust you’ll handle it like an adult. That trust is what you’re building by asking.
This is the anxiety that keeps first-time managers from running a 360 on themselves at all: what if my report says something that breaks me? The honest version of that fear is rarely the version that happens. The harsh feedback you’re imagining (something brutal about your character or competence) almost never arrives in those terms. What usually arrives is specific, observable, and fixable: a habit you didn’t know was landing badly, a meeting style that’s tripping people up, a decision pattern that someone wishes you’d explain.
Three reframes that help when you read the responses:
How to receive it: read once when you get it, sit with it for a day before responding, and then come back to your team with thanks plus one specific thing you’re going to try. That last move (specific, small, visible) is what turns the feedback into trust.
The other direction. The mechanical setup is the same as any 360 (pick raters, write questions, set a deadline, synthesize, deliver), and the cornerstone covers it step by step. What changes for you as a first-time manager is the question selection. The question set you’d ask about an IC is different from the question set you’d ask about a manager, and using the wrong one produces vague, low-signal answers regardless of how good the rest of your process is.
The cleanest starting point is the pillar on 360 feedback questions for the design principle (every question targets observable behavior in a specific situation, not personality traits) and 360 feedback questions by role for the role-specific sets. If your report is an IC, use the IC set. If your report is now managing someone themselves, use the manager set. Pick 5-7 questions, not 15, and write the kickoff message in your own voice rather than a template, because the template is what makes it feel like a corporate ritual instead of a conversation.
This is the second anxiety that stops new managers from running a 360. The fear is reasonable on the surface: you’re new, your authority feels fragile, why invite criticism that could undermine it.
The answer is the opposite of the fear. Asking your team for feedback on yourself, visibly, is the single most authority-building move available to a first-time manager. It does three things at once: it signals that you take your own growth as seriously as theirs, it sets the norm that hard things get said in the open here, and it removes the most common new-manager trap (the team learning early that feedback flows down but never up). The version of this argument applied to teams more broadly is in building a feedback culture, and the same dynamic operates at the scale of one manager with two reports.
The one exception, the version that does damage authority: asking for feedback and then ignoring or punishing it. If your report tells you that you’re micromanaging and your next week is more micromanaging, you’ve made things worse than not asking at all. Don’t ask if you’re not willing to change something. That’s the only real risk in the room.
Should I tell my own manager I’m running this? Yes, a brief heads-up, framed as development. “I’m running a small 360 round to get feedback on how I’m doing in the new role” is enough. You don’t need permission; you’re communicating it as something you’ve decided to do. Most managers will respond well to a new manager who’s investing in this kind of self-development.
What if the feedback is contradictory? It usually will be, at least partly, and that’s not a problem. Two raters seeing different facets of the same behavior produce different (and both valid) responses. Read everything first, find the pattern most raters agree on, and treat outliers as outliers. Don’t try to reconcile every contradiction; some of them are real disagreements about what good looks like, and those are worth surfacing rather than averaging out.
What if it goes badly? The realistic version of “badly” is “uncomfortable” not “catastrophic.” A first 360 that lands awkwardly is usually fixable in a single follow-up conversation; how to deliver 360 feedback results without breaking trust covers the meeting and the repair version of it. If you’re imagining career-ending consequences, those are the anxiety talking, not the realistic risk.
The reframe for the tired version of you, scrolling this at 9pm before bed.
Worth worrying about:
Not worth worrying about:
Running your first 360 as a new manager is one of the most useful moves available at the start of your career as a manager, and almost no one does it because the anxiety is louder than the upside. You’re in a different spot now, having actually read about it. Pick the direction that fits the problem in front of you, scale the round to your team (3-4 raters, 5-7 questions, two weeks), follow the cornerstone for the mechanics, and write the kickoff message like a person rather than a corporate template.
When you’re ready to run one without spreadsheets, start your first 360 in Lynxify, no annual contract, no credit card required. Or do it in a shared document and email; the version you actually run beats the version you keep planning.
Should a new manager do a 360 review on their own team?
Yes, usually, once you’re past about 60 days in role. Before that point, you and your team don’t have enough shared history for the responses to be useful. After that point, either direction (a 360 on yourself or a development-focused 360 on a report) is reasonable. Start with whichever fits the actual problem in front of you, not the one that sounds more advanced.
How long should you wait as a new manager before running a 360?
About 60 days from when you started as their manager. Sooner than that and the feedback is mostly an impression rather than a pattern, which produces vague responses that aren’t worth much to act on. After two months of working together, raters have seen enough specific behavior to give specific answers. The 60-day mark isn’t magic, it’s just when the signal gets reliably useful.
What 360 feedback questions should you ask as a first-time manager?
Five to seven open-ended questions calibrated to the role of the person being reviewed. If your report is an IC, the questions are about craft, learning, and collaboration. If you’re the one being reviewed as a new manager, they’re about how your decisions and coaching are landing. The pillar on 360 feedback questions covers the construction rule, and the role-specific sets in the questions by role spoke give you copy-ready starting points.
Is it okay to ask your direct report for feedback on you?
Yes, and it’s one of the most useful things a first-time manager can do. The fear is that it undermines authority; the reality is that asking and then visibly acting on something you hear is what builds it. The one rule: don’t ask unless you’re willing to change something. Asking for feedback and ignoring it does more damage than not asking at all.
Dmytro Shtapauk
Practical tips and experience from top-notch experts
