How to Give Feedback as a New Manager

Why new managers avoid giving feedback

The most common reason new managers avoid giving feedback has nothing to do with not knowing what to say. It has everything to do with authority they don't yet feel they've earned. You were a peer three months ago. Now you're supposed to tell someone their work isn't good enough — and somewhere in the back of your mind, you're worried they'll think less of you for it, push back, or simply disengage. So you wait. You tell yourself it wasn't that serious. You decide to see if it happens again before saying anything.

That hesitation is normal. It is also a pattern that will quietly undermine everything you're trying to build as a manager. The fear isn't irrational either. Most new managers have been on the receiving end of feedback that felt like a personal attack — delivered without context, in front of others, or at a moment of high emotion. They don't want to be that person. So they become the person who says nothing.

The cost of staying silent compounds faster than most managers expect. When feedback is withheld, the behaviour continues — and continues to be noticed by everyone else on the team. The person delivering poor work doesn't improve because nobody has told them there's a problem. The people watching start to question whether standards are being applied fairly. Resentment builds quietly. By the time the problem becomes impossible to ignore, it's no longer a small conversation — it's a performance issue that should have been addressed weeks ago. Silence doesn't protect the relationship. It just delays and amplifies the damage.

The feedback conversation most managers get wrong

The most common failure mode isn't avoiding feedback entirely — it's giving feedback that's too vague to act on. "You need to be more proactive." "Your communication could be better." "I just feel like you're not fully engaged." These statements feel like feedback but function like criticism. They name a feeling without describing a behaviour, and they leave the other person with no idea what to actually change.

The second failure mode is timing. Feedback delivered in the heat of the moment — right after a meeting that went badly, or when you're already frustrated about something else — carries the emotional charge of the situation rather than the clarity of the observation. It lands as an attack, not a development conversation. What the person on the receiving end needs is specificity, not sentiment. They need to know exactly what happened, why it mattered, and what different looks like. Feedback that develops tells someone something they can act on before the next opportunity arrives. Feedback that deflates tells them what you think of them without giving them a way forward. The difference is almost always in the structure — not the intention.

A framework for giving feedback that is actually heard

The framework used inside Manager Unleashed for this exact situation is the SBI Method — Situation, Behaviour, Impact. Three steps. No performance review language. No cushioning that dilutes the message.

Step 1 — Situation. Name the specific moment. Not "lately" or "in general" — the exact context. "In yesterday's client call" or "when you sent the report on Thursday morning." This removes ambiguity and signals that you're speaking from observation, not opinion.

Step 2 — Behaviour. Describe what you observed, not what you interpreted. "You interrupted the client twice before they finished their point" is a behaviour. "You were dismissive" is an interpretation. Behaviour is factual and specific. It can't be argued with in the same way an interpretation can.

Step 3 — Impact. Explain the consequence — on the team, the client, the outcome, or the dynamic. "It shifted the energy in the room and the client became noticeably less forthcoming for the rest of the call." Impact is why the feedback matters. Without it, the conversation feels like a complaint. With it, it becomes a development conversation.

Used together, the three steps give the other person everything they need: what happened, what was seen, and why it mattered. That's the foundation of a conversation that moves something forward.

The timing and setting that make feedback land

Prompt beats perfect. Feedback given within 24 to 48 hours of an incident lands with context still intact — for both of you. Wait a week and the specifics fade, the moment loses its relevance, and the conversation starts to feel like a file being opened rather than a development discussion. Give feedback privately, always. Public feedback — even when delivered calmly — creates an audience, and nobody receives feedback well when they feel observed. A private setting removes the performance pressure and gives the other person room to respond honestly. Open the conversation with a frame, not a statement. "I want to give you some feedback on something from yesterday's meeting — is now a good time?" That single question signals respect, reduces defensiveness, and puts the person in a receiving state before you've said anything substantive. It costs you ten seconds and changes the entire tone of what follows.

What to do when feedback is not received well

The most common mistake when feedback is met with defensiveness is to back down — to soften, qualify, or partially retract what was said in order to end the discomfort. This is the worst possible response. It teaches the other person that pushing back makes the feedback go away. When you get defensiveness or silence, don't escalate and don't retreat. Acknowledge the reaction briefly — "I can see this is landing hard" — and hold your position. You don't need agreement. You need the message to be heard. Close the conversation cleanly: "I'm not asking you to respond right now. I just want you to sit with it." Then follow up within a few days — not to revisit the argument, but to check in on how they're doing. That follow-up is what separates a difficult conversation from a damaging one.

The one thing that changes everything about feedback

The mindset shift that makes feedback easier to give — and consistently better received — is this: feedback is not a judgement of the person. It is information they don't yet have about how their behaviour is landing. When you hold that frame, the conversation changes. You're not delivering a verdict. You're offering something useful. The SBI Method works not because it's a script but because it keeps you anchored to observation rather than opinion. Pick one conversation you've been putting off. Apply the three steps. The discomfort doesn't disappear — but it becomes manageable, and the outcome becomes predictable.