How to Give Feedback to Someone More Senior Than You

The Thing Nobody Teaches You

There's a skill gap hiding in plain sight in most organizations, and almost nobody addresses it directly. Every manager eventually learns how to give feedback downward. You get trained on it, coached on it, reminded of it in every performance cycle. "Be direct. Be specific. Be timely."

But what about upward? What about when the person who needs to hear something is your boss, your skip-level, or a senior stakeholder you depend on? What do you do then?

Most people do one of two things. They say nothing, swallowing the feedback indefinitely and building resentment around it. Or they say something, but they wrap it in so many hedges and softeners that the message never actually lands. "I just wanted to share a thought, and I could be totally wrong, but maybe sometimes it might be worth considering..."

Neither approach helps anyone.

Upward feedback is genuinely hard. The power dynamic is real. The risk feels asymmetric. But if you're a manager or operator reading this, you need to be able to do it. Not because it's the polite thing, but because organizations where people can't speak honestly to power are slower, less accurate, and more fragile. And the leaders above you deserve real information too, even when it's uncomfortable to deliver.

Here's how to actually do it.

Understand Why You're Avoiding It

Before we get to technique, let's be honest about the real obstacle, because it's not a skill problem at the start. It's a fear problem.

When you imagine giving your boss critical feedback, something activates. Maybe it's the worry that they'll perceive you as insubordinate. Maybe it's the fear that they'll retaliate, even subtly, at review time. Maybe it's the suspicion that they already know and don't want to hear it, so you'd be the one making it awkward. Or maybe you've worked somewhere before where someone tried upward feedback and got quietly sidelined for it.

All of those are real risks. I'm not going to tell you they aren't.

But here's what I've seen consistently across three decades of managing, being managed, and watching organizations from the inside: the leaders who got the best from their teams were the ones who created enough psychological safety that people would tell them the truth. Not because those leaders were saints, but because they understood that an organization operating on incomplete information is flying partially blind. And the leaders who punished upward feedback? Their teams learned fast. They stopped telling the truth. And eventually, the leader stopped being effective, often without ever understanding why.

Point being, the cost of not saying it is almost always higher than the cost of saying it badly.

The Two Things That Have to Be True First

You can't skip the prerequisites and go straight to the script.

The first thing that has to be true is that you have the relationship. I don't mean you have to be best friends with your manager. I mean there needs to be enough baseline trust that when you say something critical, they don't interpret it as an attack. If you've never built any rapport, any track record of positive intent, any history of being someone who is genuinely invested in the team's success, then showing up with critical feedback is going to land strange. Build that first.

The second thing that has to be true is that you're sure it matters. Not every observation needs to become a feedback conversation. If your boss has an annoying habit that doesn't actually affect anyone, keep it to yourself. Save your upward feedback budget for things that actually matter: patterns that are hurting the team, decisions made on incomplete information, behaviors that are creating churn or friction at scale.

If both of those are true, you're ready.

Say It Directly, But Say It With Context

Here is the structural mistake most people make when they do work up the courage to give upward feedback. They build up to the point so slowly, so carefully, that the point gets lost in the setup. By the time they actually say the thing, the other person has been nodding politely for three minutes and is thinking about something else.

Be direct. State the observation early. Then give the context that supports it.

Here's a real shape that works: "I want to share something that I think is worth your attention. I've noticed that when you give feedback to the team in group settings, a few people seem to shut down afterward. I've talked to two of them and I think they're hearing it as criticism of their competence rather than direction on the work. I don't think that's your intent at all. But I think it might be affecting how much they're willing to share openly with you."

Notice what that does. It states the pattern. It gives specific supporting evidence ("two of them"). It names the impact. And it separates the behavior from the intent, which is the thing that keeps feedback from becoming an accusation.

The goal isn't to land a punch. The goal is to hand them something useful they couldn't see themselves.

Timing and Setting Are Not Decoration

This is practical, but people underestimate it.

Never give feedback in a group. Never. If you have something real to say to a senior person, find a private moment. This is both more respectful and more effective. Public feedback to a senior leader tends to read as a challenge, and now you've made them defend themselves in front of an audience. You've created a situation where accepting the feedback gracefully requires them to look diminished. Most people won't do that, and you can't really blame them.

Find a one-on-one. If you don't have a regular one-on-one with this person, create the context. "Do you have fifteen minutes this week? I want to share something that's been on my mind." That framing, low-key, no drama, signals that you're not picking a fight.

Timing matters too. Right before a big presentation, right after a stressful deadline, right in the middle of a crisis: none of those are good moments. Give the feedback when there's space to actually receive it.

What to Do When It Doesn't Land

Sometimes you say it right and it still doesn't land. The person gets defensive, or they nod and clearly don't buy it, or they thank you and then nothing changes.

First, be patient. People need time to sit with things. I've had conversations where someone came back to me two weeks later and said, "That thing you said has been in my head," and it turned out to matter after all. The immediate reaction isn't always the lasting one.

Second, you don't have to repeat it. You said it. That's the thing you could control. What they do with it is theirs to figure out. You're not their coach unless they want you to be. Say it once, clearly and directly, and then let it go.

Third, pay attention to the pattern. If you give someone honest feedback and they respond by freezing you out, making your work harder, or creating friction for you in the organization, that is real information about them. And it means you're working for someone who doesn't actually want honest information. That's worth knowing, because it changes what you do next.

The Upside Nobody Talks About

Here's the part that gets left out of every conversation about upward feedback: when you do it well, it builds your credibility faster than almost anything else.

Most people won't do it. The ones who can, who can deliver honest information to senior leaders clearly and without ego, they become the people those leaders actually trust. Because you've proven you'll tell them something they don't want to hear. That is rare. And leaders who are worth working for know it.

I've seen relatively junior managers get into rooms they had no business being in because a senior leader trusted that they'd get the truth. Not flattery. Not political positioning. The truth.

That's what upward feedback, done right, can build for you. Not just a cleaner conversation this time. Real trust over time.

The feedback you're avoiding having? Have it.