How to give feedback to your manager

Most advice on upward feedback stops at "be tactful", which is not a sentence anyone can say out loud. The failure usually isn't nerve. It's that people open their mouth without a first line, hear themselves sounding like a complaint halfway through, and retreat into something so vague their manager agrees with it and forgets it by lunch. So this guide is mostly scripts. Steal the wording, change the nouns.

Three checks before you say anything

1. Is it about the work? Useful feedback points at something your manager did and something it cost. Feedback about their personality gets filed under "attitude problem, yours".
2. Is it one thing? A list reads as a case for the prosecution. Pick the single item that, if it changed, would most improve your week.
3. Do you want a change, or an apology? Only one of those is feedback. If you cannot name the change you want in one sentence, you are not ready to give it yet.

A fourth check, not optional: can this manager hear it? Most can, some can't, and no script fixes the ones who can't. There is a section at the end for that case.

The sequence: what happens in the first five minutes

1. Book the room, not the corridor. Use your existing one to one if you have one. If you don't, ask for fifteen minutes. Never ambush someone as a group meeting breaks up.
2. First thirty seconds: ask permission. It sounds like a formality. It isn't. It moves your manager from being talked at to agreeing to listen, and it gives them a second to stop thinking about the last meeting.
3. Next sixty seconds: one situation, one behaviour, one effect. Where and when it happened, what they did, what it cost. No preamble, no history, no other people's opinions.
4. Then stop talking. This is the hard part. Leave the silence alone for five full seconds. People fill their own gap with something more honest than anything you'd have prompted.
5. Last two minutes: make the ask, agree what happens next. A named change and a next occurrence, not a warm feeling.

The scripts

Opening the door

• "Can I give you some feedback on how the handover went last week? It's about my end of it, not a complaint about the team."
• "There's something slowing me down that I think you can fix faster than I can. Ten minutes, whenever suits."
• And when they ask for feedback on the spot and you have some: "Yes, actually. Give me until tomorrow so I say it properly rather than badly now."

The feedback itself

Situation, behaviour, effect. It is the same structure as the SBI feedback model, and it works upward for the same reason it works downward: a described event is hard to argue with, a judgement is easy to argue with.

• "In Tuesday's client call, you answered the pricing question before I could. I'd prepared for it, and afterwards the client kept routing questions to you rather than me. I'd like to be the one who takes those."
• "The brief changed on Thursday and reached me on Friday in the group chat. I'd already rebuilt half the deck against the old version. If changes come to me directly, even one line, I stop doing that rework."
• "We've moved our one to one three times this month. I know the quarter is brutal. The effect is that I'm making calls I'd rather check with you first, and I'd rather not guess."

The ask

• "What would help: send me the change directly before it hits the channel."
• "Could we shorten the one to one to twenty minutes instead of moving it?"
• "Next time that question comes up on a call, can you hand it to me?"

The close

One sentence, and it does more than it looks: "Thanks for taking that. Can I raise things the same way next time?" You have just asked for a standing channel, and almost nobody says no in the moment.

Upward feedback lands when it is about the work and what it cost. "I lost two days" is a fact your manager can act on. "You're disorganised" is a verdict they can only defend against.

Wrong version, better version

When it goes wrong

Four failure modes cover most of it. Each has a move.

1. They get defensive

Watch for the reflex: explanation, context, the pressure they were under. Do not repeat your point louder. Hand them the floor and mean it.

Say: "I'm not saying you got it wrong. I'm telling you what it cost on my side. What did it look like from where you were sitting?" Then actually listen, which is harder than it sounds and is the whole of active listening. If they ask who else feels this way, they are hunting for a source rather than a fix: "I'm speaking for me. If you want a wider read, a team retro will tell you more than I can."

2. They agree warmly and nothing changes

The most common outcome by a distance. Agreement is cheap because it ends the discomfort. The fix is to leave the room with a next occurrence attached, not a sentiment.

Say: "Good. So next time the brief moves, it comes to me first. And if it doesn't, can I nudge you?" Then, when it happens again, use the nudge you were granted, flatly and without drama: "Following up on briefs. It went to the channel again on Monday." No sigh, no history lesson.

3. They turn it into feedback about you

Sometimes fair, sometimes a swerve, and you often can't tell in the moment. Either way, don't defend and don't abandon your point.

Say: "That's fair and I want to come back to it properly. Can we finish this one first?" Take a note in front of them. Then genuinely return to it, because if you don't, you've taught them the swerve works.

4. It goes cold

No reaction, no follow-up, three days of ordinary silence. Silence is not a verdict, usually it is just a full calendar. Send one short line that keeps the agreement concrete without escalating it.

Write: "Thanks again for Tuesday. Just so I've got it right: briefs come to me first from now on. Shout if I've misread that." Short, written, no cc, no accusation. It is very hard to be annoyed by.

When not to give it

• When the risk is real. Some managers punish upward feedback, and pretending otherwise is not brave, it's naive. Route it through a skip-level, a 360 process or HR, keep your own written record, and be honest with yourself about whether the job is the problem.
• When you're angry. Wait a day. Don't wait a month, because by then you'll have collected evidence, and evidence-based feedback is an ambush.
• When it isn't theirs to fix. Budget, headcount and policy sit above them. Raising it is fine, framing it as their behaviour is not.
• When you can't name the ask. Write the one-sentence request first. If it won't come, the feedback isn't ready.

If you're the manager: make it possible to receive

Nobody gives their boss feedback because a policy invited them to. They do it because the last person who tried wasn't punished for it. Three things move that:

• Ask a narrower question. "Any feedback for me?" reliably returns "no, all good". Try: "What's one thing I did this month that made your job harder?"
• Handle the first one well, because the first response sets whether there is ever a second. React to the content, not to the fact that you were criticised.
• Thank the specific point, not their bravery. "Thanks for being so honest" quietly confirms that honesty was risky. This is what psychological safety is actually made of: small evidence, repeated.

The bit reading won't fix

None of these sentences are difficult to understand. They are difficult to say in the room, to the person who writes your review, with your pulse up and thirty seconds to open. That gap is not an information gap, which is why guides like this one change less behaviour than they should.

What moves it is rehearsal: saying the opening line out loud, getting it wrong in front of someone who isn't your boss, hearing how the hedging sounds from outside your own head, and going again. That is the entire argument for experiential learning and for practising constructive feedback under mild pressure rather than reading about it. The first time you say these words should not be the time it matters.

Tour De Force runs this as live, experiential training for teams worldwide — online and in person. Talk to us, or play Gamified learning appsThe Weekly Challenge to see the method in ten minutes.