How to ask your team for upward feedback as their manager

At the end of a team meeting, a manager says the thing they've read they're supposed to say: "And hey — I'd love feedback on how I'm doing as a manager. Anything I could do better, my door's always open." Around the table, people nod. Someone says "honestly, it's going really well." The manager feels good about having asked. The team feels the temperature of the room and says nothing real, because the person asking for the critique is the same person who writes their reviews, approves their time off, and decides who gets the interesting project next quarter.

This is the hardest direction to collect feedback in, and most managers underestimate exactly how hard. Asking your boss for feedback is awkward but safe — the power runs toward the person you're asking. Asking your team for feedback on you inverts that: you're asking the people with the least power and the most to lose to critique the person who holds power over their working life. "My door's always open" does nothing about that. The door was never the problem. The asymmetry is.

Why face-to-face doesn't work here — even in a 1:1

The instinct is to fix the meeting-room silence by asking one-on-one instead. It helps a little and solves nothing fundamental, because the power gap follows you into the private room. Your report can do the math just as fast across a desk as across a conference table: if I tell my manager the standups are a waste of time and they take it badly, that lands on me, specifically, at review season.

This isn't timidity, and it isn't a sign you've failed to be approachable. It's a rational read of a real incentive structure — the same economics that keep people from giving you honest feedback in general, amplified by the fact that here you're not a peer or a vendor, you're the boss. The warmer and more well-liked you are, the more the team will protect the relationship by withholding the very thing that would help you. Niceness doesn't dissolve the asymmetry. It just makes everyone more reluctant to spend it.

Megan Reitz, who researches employee voice and speaking truth to power at Oxford's Saïd Business School, makes the uncomfortable point directly: leaders systematically overestimate how "speak-up-able" they are. The more senior you get, the more your presence quiets a room — and the more confident you tend to be that it doesn't. The manager who says "but my team tells me everything" is usually the one hearing the least.

What actually works: anonymous, structured, aggregated

If face-to-face is structurally compromised, the answer is to take your face out of it. The model that works for upward feedback is the one large, feedback-literate organizations converged on: anonymous, structured, aggregated, and explicitly developmental.

Google's people analytics team built exactly this — a semi-annual manager feedback survey that reports complete anonymized, aggregated results to the manager, with two crucial properties. First, it's confidential — the manager sees themes and averages, not who said what. Second, and most important, it is purely developmental: the results are deliberately kept out of the manager's own performance and compensation review, precisely so the team can be honest without the answers boomeranging back through some chain of consequences. The moment upward feedback feeds into anyone's evaluation — the manager's or, by implication, the team's — it stops being honest.

You don't need Google's infrastructure to copy the principle. You need three things: the answers come in without names attached, the same questions get asked of everyone so you can see patterns rather than one loud voice, and everyone understands the feedback is for your development, not for the record.

There's an honest catch at small scale, and it's worth naming out loud to your team rather than pretending otherwise. With three or four direct reports, "anonymous" only goes so far — a specific phrasing or a referenced moment can give someone away. Don't oversell a confidentiality you can't fully guarantee; that backfires the instant someone feels exposed. Instead, lean on behavioral questions that are safe to answer truthfully (hard to weaponize, hard to trace), aggregate everything you can, and be candid that the point is themes, not detective work. A team that believes you genuinely won't go looking for who-said-what will tell you more than a team handed a watertight-sounding promise they don't trust.

What to ask

Vague questions get vague upward feedback, the same way they do in any feedback request that's too broad to answer honestly. "Am I a good manager?" invites a reassuring yes. Ask instead about specific, observable manager behaviors — the things your reports actually experience week to week:

When you assign work, do they leave clear on what's expected, or do they have to guess?
When they bring you a problem, do they get help — or do they get the problem handed back with interest?
Do you give them enough context on why, or just what?
When they disagree with you, what happens next time they're tempted to?
Is there something you do that makes it harder for them to do their best work?

These are behavioral, not characterological — they ask what you do, not who you are, which is what makes them answerable. (The same principle drives the 360 questions that surface useful answers; upward feedback is one slice of a 360.)

Make it a rhythm, not a one-off

A single upward-feedback round, sprung once, reads as a stunt — or worse, as a hunt for who's disloyal. The team can't tell whether it's safe until they've seen the cycle run at least once without anyone getting burned. Recurring, predictable rounds do two things a one-off can't: they let trust compound (each safe round makes the next one more honest), and they let you actually track whether the thing you changed last quarter landed. A quarterly cadence tends to be the sweet spot — frequent enough that issues surface while they're small, spaced enough that you've had time to act on the last round before asking again. Upward feedback is a practice, not an event.

The part that decides everything: what you do after

Collecting the feedback is the easy half. What you do with it determines whether you ever get it again. Three moves:

Close the loop, out loud. Tell the team what you heard — the hard parts included — and what you're going to change. "A few of you said I jump in to solve things before you've had a chance to. I'm going to wait, and ask first." Naming the criticism yourself proves it was safe to give.
Change one visible thing. Not everything — one thing, observable, soon. The team needs to see that feedback turns into action, or they'll correctly conclude the survey was theater.
Never, ever trace and retaliate. Not overtly, not subtly, not even in your own head in a way that leaks into how you treat someone. The fastest way to kill upward feedback permanently is to make one person regret having given it.

Do this once, visibly, and the next round will be more honest than the first. Skip it, and you've taught your team that asking was a formality — and trained them, expensively, to never trust the next ask either.

Where Mirorly fits

The cleanest way to run upward feedback is the same structure Mirorly is built around — except here the respondents are your direct reports. You answer a set of behavioral leadership questions about yourself first, then send the same questions to your team, who respond anonymously, and you read your self-view side by side with theirs. The gaps are the whole point: the places where you rated yourself one way and the people you manage see it differently are exactly the blind spots you can't surface alone.

Our core leadership behaviors template is built for this: run it on yourself, send one link to your team, and get aggregated, anonymous answers structured to show you the gap rather than bury it in an average. Not a verdict, not an HR cycle, not a once-a-year survey someone makes you do — just a clear, repeatable read on how the people you manage actually experience being managed by you.

The one-line summary

Your team is the best-placed and least-able to tell you how you manage — so take your face out of the ask: anonymous, structured, developmental-only, recurring, and followed by one visible change and zero retaliation. How you take the first round decides whether there's ever a second.