Business Insights

Feedback without conflict: the SBI model or the “sandwich” method

Feedback is one of the most important management tools. With its help, a manager supports employees in developing, correcting mistakes, improving processes, and understanding the company’s expectations. In practice, however, feedback often becomes a source of tension: the employee perceives comments as criticism, the manager is afraid of hurting the person, and important issues remain unspoken.

As a result, misunderstandings accumulate within the team. Mistakes are repeated, the quality of work decreases, and the manager starts becoming irritated not because of one situation, but because “this keeps happening all the time.” To prevent feedback from turning into conflict, it is important to use a clear structure for the conversation.

One of the most practical approaches is the SBI model: Situation-Behavior-Impact. Another popular format is the “sandwich” method, where a corrective comment is placed between two positive comments. Both tools can be useful, but they work differently. Let’s look at when to use SBI, when the “sandwich” method is appropriate, what mistakes managers make, and how to give feedback in a way that helps the business rather than damaging relationships within the team.

Feedback is especially effective when it is based not only on emotions, but also on clear indicators: deadlines, work quality, financial results, team workload, and impact on clients. We help businesses analyze management decisions through numbers, processes, and risks. As part of financial consulting, the company’s specialists help assess which processes require attention, where losses occur, and which decisions can increase business stability.

Why feedback often causes conflict

Conflict does not arise from the fact of feedback itself. It appears when a person hears not a specific comment about work, but an accusation directed at them personally.

For example, the phrase “you are inattentive” sounds like an assessment of personality. The employee may start defending themselves, arguing, or feeling offended. But if the manager says: “In Monday’s report, the data for two clients was not included, and because of this, accounting could not reconcile the amounts on time,” the conversation becomes specific.

The main mistake in giving feedback is mixing together the person, their behavior, and the consequences. When a manager speaks in general terms, the employee does not understand what exactly needs to change. And when the comment sounds too emotional, the meaning gets lost behind a defensive reaction.

Feedback should answer three questions:

what happened;
what specific action or behavior needs to be discussed;
what consequences it led to;
what needs to be done next.

This is why structured models such as SBI help make the conversation calmer and more useful.

What the SBI model is

SBI stands for:

Situation
Behavior
The impact or consequences

It is a feedback model that helps a manager speak not about general impressions, but about specific observable behavior and its effect.

The formula looks like this:

When the situation happened → what exactly the person did → how it affected the work, team, client, or result.

For example:

During the client meeting on Tuesday, when the project deadlines were being discussed, you interrupted your colleague several times and did not let her finish her explanation. Because of this, the client did not hear an important part of the reasoning, and tension appeared within the team.

This wording does not attack the employee’s personality. It describes a specific episode, specific behavior, and a specific impact. This reduces the likelihood of conflict and increases the chance that the person will hear the essence of the message.

Situation: describing the specific situation

The first element of SBI is the situation. The manager should indicate when and where the matter being discussed took place.

Unsuccessful wording:

You often communicate poorly with the team.

Better:

During Monday’s planning meeting, when the team was discussing the project launch...

Specificity helps the employee understand which episode is being discussed. If the situation is not clearly identified, the person may argue: “When did this happen? I don’t remember that. I don’t always do that.”

Good feedback starts with a fact, not an evaluation.

You can use wording such as:

“During the client meeting on Wednesday...”
“In last week’s report...”
“When you passed the task to another employee...”
“During the budget discussion...”
“In the correspondence with the contractor...”

The more precisely the situation is described, the easier it is to get to the point without unnecessary emotions.

Behavior: talking about behavior, not personality

The second element is behavior. Here it is important to describe only what could be seen or heard.

Unsuccessful wording:

You treat tasks irresponsibly.

Better:

You sent the report two days later than the agreed deadline and did not inform the team about the delay.

In the first case, the manager evaluates the person’s personality. In the second, the manager talks about a specific action. The difference is fundamental: an employee can change an action, but will defend themselves if they feel accused as a person.

Behavior should be described as neutrally as possible:

not “you are lazy,” but “the task was not completed by the agreed deadline”;
not “you communicate rudely,” but “in the correspondence, you wrote a phrase that could have sounded harsh”;
not “you are disorganized,” but “the meeting started without the prepared data”;
not “you ignore clients,” but “the client received a response only after two days.”

This approach is especially important in HR processes, team management, and internal communication. If a company does not have clear rules for feedback, work evaluation, and formalizing decisions, the risk of misunderstandings and labor disputes increases.

In such cases, it is useful to build not only communication, but also a system of HR documents. More details about support for HR processes are available on the FlagMAN-D page dedicated to HR documentation management.

Impact: explaining the consequences

The third element of SBI is impact. The manager explains what the employee’s behavior led to.

For example:

Because of the delay in the report, accounting did not have time to check the data, and we had to postpone sending the documents to the client.

Or:

When the task was handed over without a detailed description, the designer spent additional time clarifying details, and the launch deadline shifted.

Impact helps the employee see that the feedback is not a personal reproach. It is about the result: time, clients, money, work quality, team workload, or risks.

It is important not to exaggerate the consequences. If the mistake led to a small delay, there is no need to say that “the whole company is suffering because of this.” Overly strong wording triggers defensiveness and reduces trust.

A good Impact statement shows the real connection between the action and the result.

Example of feedback using SBI

Suppose an employee regularly fails to send documents to accounting on time.

Unsuccessful wording:

You always drag everything out; because of you, we have problems with reporting.

Wording using SBI:

On Friday, when the invoices and acts for the week had to be sent, the documents were sent after 6:00 PM, although the agreement was to send them by 12:00 PM. Because of this, accounting did not have time to check all operations during working hours, and part of the reconciliation had to be postponed until Monday. Let’s agree on how we will send documents going forward so that deadlines are not missed.

In the second version, there is a specific situation, observable behavior, consequences, and a proposal to move toward a solution. Such a conversation is harder to turn into a conflict because it is based on facts.

For business, this is especially important in processes related to reporting, finances, and documents. If employees systematically delay data, not only communication suffers, but also the quality of accounting. In such situations, it is important to build clear internal rules and control document flow. You can read more about the role of order in accounting in the article: Restoring accounting records in Moldova: what to do if accounting was not maintained.

When the SBI model is especially useful

SBI works well in situations where specific behavior needs to be discussed and changed in the future.

The model is suitable for:

work-related mistakes;
missed deadlines;
communication problems;
incorrect communication with clients;
conflicts within the team;
management feedback;
performance evaluation;
discussion of work quality;
correction of behavior by managers and employees.

SBI is useful not only for negative feedback. It can also be used for positive feedback.

For example:

During the client meeting on Thursday, you quickly prepared the calculation and explained it in simple terms. Thanks to this, the client understood the difference between the options more quickly and agreed to move to the next stage.

This kind of feedback reinforces correct behavior. The employee understands exactly what worked well and can repeat it in the future.

What the “sandwich” method is

The “sandwich” method is a feedback format in which a critical comment is placed between two positive messages.

The structure looks like this:

First, the manager says something positive.
Then the manager gives corrective feedback.
At the end, the conversation is closed again with a supportive phrase.

For example:

You prepared the visual part of the presentation well. At the same time, there are inaccuracies in the budget calculations that need to be corrected before sending it to the client. Overall, the structure of the presentation is strong, so after the figures are corrected, it can be used.

The idea of the method is to reduce tension and avoid demotivating the employee. However, it should be used carefully.

The weakness of the “sandwich” method

The problem with the “sandwich” is that employees quickly begin to recognize the pattern. If a person understands that criticism will always follow the first praise, they stop perceiving the positive part as sincere.

In addition, the important remark may get lost. The employee hears the beginning and the ending, but may not understand how serious the middle part is.

For example:

You are doing very well, but there is a small issue with deadlines. Overall, we are satisfied with your work.

After such a phrase, the employee may think the problem is insignificant, even though missed deadlines may be critical for the manager.

That is why the “sandwich” method is better used not for serious violations, but for gentle corrections when it is important to maintain a supportive tone while drawing attention to a specific improvement!

SBI or “sandwich”: which one to choose

SBI is better suited when you need to:

discuss a specific mistake;
change an employee’s behavior;
explain the consequences;
record the facts;
reduce the emotional intensity of the conversation;
prepare for a difficult discussion;
avoid subjective evaluations.

The “sandwich” method may be appropriate when:

the feedback is not critical;
the employee reacts very emotionally to comments;
the work needs a gentle adjustment;
it is important to maintain motivation;
there is real positive behavior worth noting.

The main rule is: if the problem is serious, do not hide it between compliments. It is better to speak directly, but respectfully and based on facts.

How to give feedback without conflict

For feedback to be received calmly, it is important not only to choose the right model, but also to follow general rules for the conversation.

1. Speak at the right time

Feedback should be close to the situation. If a mistake is discussed a month later, the employee may no longer remember the context. In addition, delayed feedback often becomes more emotional: the manager accumulates irritation for a long time and then says everything at once.

It is better to discuss the situation while it is still relevant, but not at the moment of strong emotions.

2. Do not start the conversation in public

Critical feedback is better given privately, not in front of the whole team. Public comments are often perceived as humiliation and trigger a defensive reaction.

Praise can be given publicly if the employee is comfortable with it. But corrective comments are better discussed one-on-one.

3. Separate facts from interpretations

Fact: “The report was sent at 6:30 PM instead of 12:00 PM.”

Interpretation: “You don’t care about deadlines.”

Feedback should be based on facts. Interpretations may be wrong, while facts help keep the conversation constructive.

4. Give the employee an opportunity to respond

Feedback is not a monologue. After describing the situation and consequences, it is important to ask the employee how they see the situation.

For example:

How do you see this situation? What prevented you from sending the data earlier? What needs to change so that the deadline is met next time?

Sometimes the cause of the mistake is not the employee, but the process: an unclear task, overload, lack of access, conflicting priorities, or insufficient resources.

If problems at work are related to overload or unclear roles, it is useful to analyze not only the behavior of one specific person, but also the management system. You can read more about how managers can make decisions with incomplete information in the FlagMAN-D article: How to make decisions under uncertainty: 5 approaches for managers.

5. End the conversation with a specific next step

Feedback without a next step often remains just a conversation. At the end, it is important to agree on what will change.

For example:

“Let’s agree that documents will be sent every Thursday by 4:00 PM.”
“Next time, before sending anything to the client, we will check the figures using a checklist.”
“If the deadline shifts, you inform the team at least one day in advance.”
“In two weeks, we will return to this issue and see how the new process is working.”

A specific next step turns feedback into a management tool.

How a manager can prepare for difficult feedback

If the conversation may be tense, it is better to prepare in advance.

Before the meeting, it is worth answering several questions:

what specific situation will be discussed;
what behavior needs to change;
what consequences it led to;
what facts confirm the issue;
what result is needed after the conversation;
what support can be offered to the employee;
what agreements need to be recorded.

If the issue concerns discipline, deadlines, job duties, or repeated violations, it is important to consider not only communication, but also documents: the employment contract, job duties, internal regulations, orders, and time tracking rules. This reduces the risk of disputes and helps the company act consistently.

For business, it is important that HR documents reflect real processes. If rules exist only “verbally,” it is harder for the manager to justify expectations and record agreements.

How not to turn feedback into demotivation

An employee perceives feedback more easily when they understand that the goal of the conversation is to improve the work, not to punish them.

For this, it is important to:

speak calmly;
avoid sarcasm;
avoid comparing the employee with others;
avoid bringing up old mistakes unnecessarily;
avoid generalizations such as “always” and “never”;
acknowledge the person’s strengths;
discuss specific behavior;
show that the situation can be changed.

The phrase “you always miss deadlines” almost always causes resistance. The phrase “over the past two weeks, two reports were sent later than the agreed deadline” sounds more specific and fair.

Good feedback should not destroy trust. It should help the person understand exactly what should be changed and why it matters to the team.

Feedback as part of a management system

If feedback appears in the company only when the problem has already become serious, it is perceived painfully. It is much more effective when feedback is built into regular processes:

weekly one-on-one meetings;
discussion of project results;
retrospectives;
regular goal reviews;
onboarding of new employees;
meetings at the end of the probation period;
annual or quarterly performance reviews.

In such a system, employees get used to feedback as a normal part of work, not as a sign of conflict.

It is also easier for the manager: there is no need to accumulate dissatisfaction and wait for the “right moment.” It becomes possible to regularly discuss what is working well, what needs improvement, and what actions can help the team move faster.

If the company is growing, these processes should be formalized in regulations, policies, and HR documents. This helps managers act consistently and employees understand expectations.

Typical mistakes managers make when giving feedback

The most common mistakes are not related to a lack of desire to help, but to the wrong form of conversation.

Managers often:

speak too generally;
begin with an accusation;
give feedback in public;
accumulate irritation for too long;
discuss personality rather than behavior;
fail to explain consequences;
do not suggest a next step;
use the “sandwich” method where a direct conversation is needed;
do not allow the employee to express their view;
do not record agreements.

Because of this, feedback turns into an argument. The manager thinks they “said everything correctly,” while the employee leaves feeling treated unfairly.

SBI helps reduce these risks because it requires the conversation to follow a structure: situation, behavior, impact.

In brief: how to give feedback using SBI

Situation:
Describe a specific moment, meeting, task, correspondence, or report.

Behavior:
Name the specific action that could be seen or heard.

Impact:
Explain how it affected the client, team, deadlines, money, quality, or risks.

Next step:
Agree on what will change going forward.

Example:

During the client meeting on Wednesday, when we were discussing the project budget, you did not prepare the calculation for additional expenses. Because of this, we could not immediately answer the client’s question and had to postpone approval until the next day. Let’s agree that before such meetings, we check all figures in advance using a checklist.

Conclusion

Feedback without conflict is not a matter of being soft or strict. It is a matter of structure. When a manager speaks in general phrases, evaluates personality, or accumulates irritation, the conversation can easily turn into an argument. When the manager describes a specific situation, behavior, and consequences, feedback becomes clear and practical.

The SBI model helps speak directly but respectfully. It is especially useful for difficult conversations, repeated mistakes, and situations where behavior needs to change. The “sandwich” method can be useful for gentle correction, but it should not be used where the problem is serious and requires clarity.

For business, quality feedback is part of the management system. It helps reduce conflicts, increase responsibility, improve processes, and maintain trust within the team.

If your company needs to build clear HR processes, prepare HR documents, regulations, and internal rules, FlagMAN-D specialists can help create a system where expectations, responsibilities, and agreements are properly recorded and support business stability.

FlagMAN-D

2026-07-16 10:00