How to Give Feedback That Changes Behavior: A Manager's Guide

Why does feedback so often fail to change anything?

Feedback fails when it is vague, late, aimed at the person instead of the task, or delivered in a way that makes the listener defend themselves instead of think. The research is a useful warning here. In a 1996 meta-analysis in Psychological Bulletin, Avraham Kluger and Angelo DeNisi pooled 607 effect sizes from 23,663 observations and found that feedback interventions improved performance on average (an effect size of 0.41), but that more than a third of them lowered performance.

Their explanation, which they called feedback intervention theory, is that feedback works less well the closer it pushes attention toward the self and away from the task.

That is the practical lesson for managers. Telling someone they are careless draws attention to who they are, and they will respond to that. Telling someone that the figures in Tuesday's report did not match the source data draws attention to the task, and they can fix it.

Aim your feedback at the work and the specific behavior behind it.

The cost of silence is also real. Gallup's 2015 analysis of manager behaviors found that employees whose managers hold regular meetings with them are almost three times as likely to be engaged, and that managers account for at least 70% of the variance in engagement scores. Giving no feedback is not neutral.

It leaves people guessing about how they are doing.

What is a simple structure for giving feedback?

The most widely used structure is Situation, Behavior, Impact, often shortened to SBI. The Center for Creative Leadership describes it in three steps and adds a fourth, Intent, to make the conversation two-way. The reason it works is that it forces you to stay with facts you observed and keeps judgments and guesses about motive out of the opening.

In the first step, name the situation: the specific setting and time, such as this morning's 11 am team meeting, and not a vague reference like last week. In the second, describe the behavior using only what you observed, which means you say what the person did, not that they were rude. In the third, explain the impact the behavior had, on you, the team or a customer.

In the fourth, ask about intent, with a question like: what were you hoping to accomplish? The Center for Creative Leadership notes that you should not assume you know why someone acted as they did. Ask, and listen to the answer.

A feedback script you can reuse

Use the script below as a starting point, then put it in your own words. People notice when feedback sounds like a formula, so treat the structure as scaffolding and not as text to recite. Prepare by writing down the situation, behavior and impact on paper before the conversation, and decide what you would like to be different afterward.

• Ask permission and set the frame: I have some feedback on the client call this morning. Is now a good time? (If not, agree a time the same day or next.)
• Situation: On the 11 am call with the client about the launch date.
• Behavior: You told them the date was confirmed, although engineering had not signed off yet.
• Impact: The client is now planning around that date, and I am worried we will need to correct it, which could cost us some trust.
• Ask for their view: What was your thinking when you gave the date? What would you like to do next?
• Listen, then agree on what changes: Next time, tell the client you will confirm after engineering signs off. Can you send them a short correction today?
• Follow up: Set a time to check in, for example in the Thursday one-on-one, and say what you will look for.
• Close on the relationship: State what you value about the person's work, only if it is true and relevant, so the conversation does not end on the problem alone.

Keep the whole conversation short. Most corrective feedback takes ten minutes or less. The longer you talk, the more likely you are to drift into general criticism, repeat yourself or raise unrelated issues.

If there are several problems, choose the one that matters most and deal with the rest later.

How do you give positive feedback that is useful?

Positive feedback is not just a courtesy. It tells people what to repeat. Vague praise such as great job does little, so use the same structure as for corrective feedback: this morning's presentation, you opened with the customer's problem before showing the solution, and the team stayed focused for the whole discussion.

Now the person knows what to do again.

Gallup's 2015 analysis reported that 67% of employees who strongly agreed that their manager focuses on their strengths or positive characteristics were engaged, compared with 31% of those who strongly agreed that their manager focuses on weaknesses. The article does not name a sample size or study year for this specific comparison, so treat it as directional. It does fit a sensible practice: spend as much care on noticing what works as on spotting problems.

For recognition that goes beyond feedback in the moment, such as public thanks and awards, see the guide on employee recognition. Feedback and recognition are related but different: feedback is information for improvement, and recognition is appreciation for contribution. Teams need both.

When and where should you give feedback?

Give it soon after the event, while both of you remember the details. Waiting for a review cycle means the person cannot connect the comment to the situation, and they may feel ambushed by something that has been bothering you for months. If you are upset, take a few hours to calm down but do not wait days.

Give positive feedback publicly when the person is comfortable with that, and give corrective feedback privately. Choose a neutral setting, and do not do it in the corridor or at the end of a meeting with others watching. For a difficult message, allow time afterward.

A conversation that ends right before the person has to attend another meeting leaves them with nowhere to process it.

Use your regular one-on-one meetings as the standing place for feedback, so that it becomes routine and not a summons. If feedback only happens when something is wrong, people dread the invitation. If it happens every week, a short comment about a presentation or a draft is just part of the job.

How do you deal with defensiveness and emotion?

Some defensiveness is normal. People often react to feedback with surprise, anger or silence, and none of these means the feedback was wrong or that you delivered it badly. Slow down, acknowledge the reaction and give the person a moment.

You can say: I can see this is hard to hear. I will pause for a moment, and then I would like to hear how you see it.

Ask questions before explaining or insisting. The Intent step in the Center for Creative Leadership's approach is useful here because it turns a verdict into a conversation. Sometimes you will learn something that changes your view: the person did not have the information, a process was unclear or you missed part of the picture.

Where that happens, say so plainly.

If the person disagrees with the facts, return to what you observed and be specific about the example. If they disagree with the impact, explain it again without exaggerating. If the person becomes upset to the point that the conversation cannot continue, stop, agree on a time to resume and make sure they know that the relationship and their job are not under threat if that is the case.

A climate where people can hear difficult messages without feeling attacked takes time to build, and the guide on psychological safety at work covers how.

How do you give feedback to remote and hybrid team members?

Remote feedback needs more deliberate planning because you lose the small cues of an office, such as noticing someone's face after a comment. Use video for anything corrective, not chat, since tone is easily misread in text. Schedule the conversation instead of springing it, and keep the structure the same so that people do not read the format as a signal.

Written feedback can work well for positive comments and for detailed comments on documents or code, as long as you keep it specific and follow up in conversation if there is something sensitive. Do not send a critical message late in the day and then log off.

Hybrid teams carry a particular risk: the people you see most often get the most feedback, and the people who are less visible get less. Check that you are giving each person a similar amount of attention. The guide on how to manage a hybrid team covers how to keep contact even across locations.

What mistakes should you avoid?

The first is the feedback sandwich, in which you wrap a criticism between two compliments. People often learn to discount the praise because they know what is coming, and the real message gets lost. Say the positive things at the time they are true and say the corrective thing clearly and kindly.

The second is generalizing. Words like always and never turn a specific event into a character judgment, and they invite the reply that the person did not always do it. Stick to the example you have, and mention patterns only when you can give two or three dated instances.

The third is feedback about someone's personality or presumed motives, such as you do not care about quality. Describe what you saw instead and ask about the reason. The fourth is saving it all up for the annual review, which makes the review a list of grievances.

The fifth is giving feedback and never following up. If a behavior changes, say so. If it does not, have a second conversation that is a little more direct about what needs to change and by when.

Finally, watch out for feedback on matters that need a different process. If the issue is serious misconduct, discrimination or a pattern that has not improved after clear feedback, involve HR and follow your organization's formal procedure. Your HR software may hold the records and workflows for this, and the performance management software category covers tools used for ongoing check-ins and review cycles.

How do you make feedback a habit on your team?

Make it ordinary. Put feedback on the agenda of every one-on-one, ask people what feedback they want from you and what you could do differently, and model receiving feedback gracefully. When someone gives you feedback, thank them, ask a clarifying question and tell them what you will do.

A manager who cannot take feedback will not get much from the team.

Teach the structure. Share the SBI steps with the team and encourage peer feedback using the same method, so that people can say to each other what they saw and what effect it had. A short written guide and a session where people practice with low-stakes examples is enough to start.

If you want to scale this across a department, the learning management systems category covers platforms for manager and team training.

Keep a small record. After each feedback conversation, make a note of the date, what you said and what you agreed. This helps you follow up, keeps your memory honest and gives you something to refer to in review time.

Look at the broader numbers on how employees experience communication with their managers in our employee engagement statistics page. The goal is a team where people know how they are doing, hear it from you early and trust that you will tell them the truth.

Frequently asked questions

What is the best way to give feedback to an employee?

Use a structure such as Situation, Behavior, Impact: name the specific moment, describe what you observed without judgments, explain the effect, and then ask for the person's view and agree on what happens next. Give it soon after the event, in private if it is corrective, and focus on the task and behavior, not the person.

How often should managers give feedback?

Regularly and in small amounts, not once a year. Gallup's 2015 analysis found that employees whose managers hold regular meetings with them are almost three times as likely to be engaged. A weekly one-on-one is a natural place to give short comments on recent work, which makes each individual piece of feedback less loaded.

Why do employees get defensive when given feedback?

Feedback that touches on identity or competence triggers self-protection. Kluger and DeNisi's 1996 meta-analysis found that more than a third of feedback interventions lowered performance, and that feedback works less well when attention shifts toward the self and away from the task. Describe observable behavior, ask about intent and give people time to respond.

Is the feedback sandwich a good technique?

Usually not. People learn to expect the criticism after the first compliment and then discount the praise, and the corrective message becomes blurry. Give positive feedback when it is earned and make it specific, and give corrective feedback separately, clearly and with a concrete next step.

Close by saying what you value in the person's work if it is true.

How do you give negative feedback without demotivating someone?

Keep it specific, about the work and not the person, and make it forward looking. Explain the impact, ask for their view, and agree on one concrete change and a follow-up date. Recognize what the person does well on other occasions so that they hear the problem as one issue, not a verdict on their value.

Should feedback be given in writing or in person?

Corrective feedback is best given live, in person or on video, so you can read the reaction and have a two-way conversation. Written feedback suits detailed comments on documents or code and positive notes people can keep. For anything sensitive, follow a written note with a conversation, and do not send critical messages and log off.

Sources and further reading

• The effects of feedback interventions on performance: a historical review, a meta-analysis, and a preliminary feedback intervention theory (Kluger and DeNisi, Psychological Bulletin, 1996), Hebrew University of Jerusalem research portal
• Closing the gap between intent vs. impact: the SBII feedback model (August 2025), Center for Creative Leadership
• Employees Want a Lot More from Their Managers (2015), Gallup