How to Give Constructive Feedback: The Complete Guide (With Examples)

Most feedback conversations fail before they start, because the person giving it has already picked one of two bad options: say nothing and hope it improves on its own, or wait until frustration builds up and it comes out sharper than intended. Neither one is how to give constructive feedback — both are ways of avoiding the actual skill. Constructive feedback is specific, timely, and aimed at a behavior instead of a person, and like any skill, it gets dramatically easier once you have a structure to hang it on. This guide covers the framework, real example scripts, how to handle a defensive reaction, and the questions people ask most.

The goal isn't to make the conversation more comfortable for you. It's to make the feedback more usable for them — clear enough that they know exactly what to do differently, and delivered in a way that doesn't make them feel like they need to defend themselves before they can even hear it.

Why vague feedback doesn't actually help anyone

"Good job, just try to be a bit more proactive" is a sentence that feels kind and does almost nothing. It gives the other person no information about what "proactive" would actually look like, so the next attempt is just as likely to miss the mark. Vague praise and vague criticism share the same flaw: they describe a feeling instead of a behavior, which means the person receiving them has to guess at the translation — and people tend to guess in the direction that requires the least change.

The fix isn't to be harsher. It's to be more specific. Specific feedback, even when it's about something that didn't go well, is easier to hear than vague feedback, because it gives the other person something concrete to work with instead of a general sense that they've disappointed you.

When to give it: soon, and in private

Feedback loses power the longer it waits. Raising something from three weeks ago forces the other person to reconstruct context they may not fully remember, and it signals that you'd been sitting on it rather than addressing it in the moment. Aim to give feedback within a day or two of the behavior, while the details are still fresh for both of you. Constructive feedback about a specific mistake or gap almost always belongs in private — a 1:1, not a team channel or a meeting with an audience, because even mild correction delivered publicly tends to register as a much bigger deal than it was.

The SBI framework: Situation, Behavior, Impact

The most reliable structure for constructive feedback is three parts, in order: the Situation (when and where this happened — "in yesterday's client call"), the Behavior (exactly what you observed — "you interrupted Maria twice while she was walking through the numbers"), and the Impact (what actually resulted — "it meant we never got to her risk assessment, and the client left with an incomplete picture"). Each piece does a different job: the situation grounds it in a specific moment instead of a pattern that feels like a character judgment, the behavior keeps it factual and observable, and the impact explains why it matters at all. Skip any one of the three and the feedback gets noticeably weaker — situation-behavior without impact reads as nitpicking; behavior-impact without situation reads as a sweeping accusation.

1. Describe the specific behavior, not the person's character

"You're not a team player" is a verdict about who someone is. "You didn't loop in the design team before changing the layout" is a description of what happened. The second version is dramatically easier to hear and act on, because it isn't asking someone to defend their identity — it's pointing at one decision they can make differently next time. Before the conversation, write down the actual observable behavior in one sentence, stripped of interpretation and adjectives. If the sentence still contains a word like "lazy," "careless," or "unprofessional," it's a judgment, not yet a behavior — keep rewriting until it's just the facts.

2. Name the impact so the reason is obvious

Behavior without impact leaves the other person wondering why you're even bringing it up — if it didn't actually cost anything, it can feel like criticism for its own sake. Naming the real impact, plainly, closes that gap: "it meant the client left without a risk assessment" is a reason, not a punishment. This also works in reverse for positive feedback — "you caught that pricing error before it went to the client, which would've meant a very awkward correction later" lands far better than "great catch," because it shows the person exactly why what they did mattered.

3. Ask a real question, and mean it

After stating the situation, behavior, and impact, stop and ask what happened from their side — "what was going on there?" or "how did that look from where you were sitting?" — and then actually listen to the answer instead of waiting for your turn to restate the point. Most behavior that looks like carelessness from the outside has a reason behind it: unclear priorities, a conflicting deadline, information they didn't have. Skipping this step turns feedback into a monologue and makes the other person feel judged rather than heard, even when everything you said up to that point was fair.

4. Handle defensiveness without backing down or escalating

Some defensiveness is normal, even when the feedback is delivered well — nobody enjoys hearing they missed something. The mistake is either caving entirely ("forget it, it's not a big deal") the moment you sense discomfort, or doubling down and piling on more examples to prove your point. Instead, separate the two things people often conflate: their competence and this one instance. "I still think you're good at this — and I also need this specific thing to go differently next time" holds both without contradiction. If they push back on a fact, be willing to be corrected; if they push back on the standard itself, hold it calmly and explain why it matters.

5. Close with one concrete next step, not a vague hope

"Just be more careful" gives someone nothing to actually do differently. "Let's do a quick review together before the next client call" is a step they can act on. Ending the conversation with a specific, small commitment — and a rough sense of when you'll check back in — is what actually changes behavior, rather than leaving the conversation as a one-time correction that fades from memory in a week.

A script you can adapt

• Set it up. "Got a couple minutes? I wanted to talk through something from [situation]."
• State the behavior, plainly. "I noticed [specific, observable behavior]."
• Name the impact. "The effect was [what actually resulted]."
• Ask, and actually listen. "What was going on there, from your side?"
• Hold both trust and the ask. "I still trust your work — and I need this specific thing to go differently."
• Close with a next step. "Let's try [concrete change] — I'll check back in [timeframe]."

Common mistakes when giving feedback

• Sitting on it too long. Feedback from three weeks ago has lost most of its usefulness and half its detail.
• Describing character instead of behavior. "You're disorganized" invites defense; "the deck didn't have the numbers we agreed on" invites a fix.
• Skipping the impact. Without it, feedback reads as a preference, not a reason.
• Delivering it in public. Even mild correction in front of others tends to land as much bigger than intended.
• Never asking their side. A monologue makes people defensive even when every fact in it is accurate.
• Ending with nothing concrete. "Try to do better" isn't a next step anyone can actually act on.

Frequently asked questions

What's the best framework for giving constructive feedback?

Situation, Behavior, Impact (SBI) is the most reliable structure: name when it happened, describe exactly what you observed, and explain what it actually resulted in. Each part does distinct work, and skipping any one of them noticeably weakens the feedback.

How do I give feedback to someone more senior than me?

Frame it around a specific outcome rather than their approach in general — "when the deck went out without the updated numbers, the client asked me to re-send it" — and ask a genuine question about their view. Seniority changes the tone, not the structure: specificity and a real question still do the work.

What if the person gets defensive or upset?

Don't retract the feedback or pile on more examples. Separate their competence from this one instance out loud — "I still think you're good at this, and this specific thing needs to change" — and give them a moment to respond before moving to a next step.

How is constructive feedback different from criticism?

Criticism often stops at what went wrong. Constructive feedback adds the specific behavior, the impact, and a concrete next step — it's aimed at changing something going forward, not just registering disapproval about something in the past.

Should positive feedback follow the same structure?

Yes — vague praise ("great job") is just as unhelpful as vague criticism. "You caught that pricing error before it reached the client, which saved us an awkward correction" tells someone exactly what to keep doing, and why it mattered.

How often should feedback happen?

Close to the moment it's relevant, rather than saved up for a scheduled review. Frequent, small, specific feedback is far easier to act on than one dense conversation every few months covering everything at once.

Not sure whether clarity, presence, listening or handling conflict is the skill quietly holding you back in these conversations? Take our free communication skills test. It scores six dimensions of real conversation and tells you, bluntly, where to build first.