SBI and DESC help keep workplace feedback clear and constructive: describe the situation, name the behavior, explain its impact, then invite a response and agree on next steps. That final conversation matters—it turns a tense moment into a shared plan with room for both perspectives.

Multiple Choice

Which communication framework explicitly includes inviting dialogue and next steps?

When giving feedback, using a framework that roots the message in what happened, what was observed, and the resulting impact—while also inviting the other person to respond and ending with concrete next steps—creates a constructive and actionable dialogue. The option that fits this pattern describes Situation, Behavior, and Impact, and explicitly includes inviting dialogue and ending with next steps. This structure keeps feedback anchored in observable facts, explains why the behavior mattered, invites the other person to share their perspective, and then specifies what will happen next, which helps ensure clarity and accountability. The other approaches don’t align with this collaborative, forward-moving approach. One option focuses on acknowledgment and demands with no invitation to discuss or plan future actions. Another centers on telling, demanding, or threatening, which tends to shut down dialogue and trust. The last option offers praise without specifics and lacks actionable guidance or a path forward.

Feedback That Opens a Door: Using SBI and DESC at Work

Good feedback should do more than point out what went wrong. It should help people understand what happened, why it mattered, and what they can do next. That sounds simple, but workplace conversations can get tangled fast. A comment meant to be helpful may land as blame; a real concern may come out so vaguely that nobody knows what to change.

Frameworks such as SBI and DESC offer a steadier way through. They help keep a message tied to specific events, while leaving room for a genuine conversation. The aim isn’t to make every discussion sound scripted. It’s to make important conversations clearer, fairer, and more useful.

Start with what happened, not what you assume

SBI stands for Situation, Behavior, Impact. First, name the situation: when and where the event occurred. Then describe the behavior you observed. Finally, explain its impact.

For example: “During Monday’s client call, you answered before Maya had finished explaining the delivery delay. The client then asked her to repeat the details, and we lost time clarifying the plan.”

That statement gives the other person something concrete to respond to. Compare it with “You always interrupt people.” The word always turns one event into a sweeping judgment. It can trigger an argument about whether the label is fair, rather than a conversation about what happened.

SBI works best when the behavior is something another person could have seen or heard. “You rolled your eyes” is observable. “You don’t respect the team” is an interpretation. The distinction matters because feedback should describe a moment, not claim to know someone’s character or motives.

Impact also deserves care. It isn’t always a dramatic business result. It might be that a colleague had to repeat a point, a decision was delayed, or a quieter team member stopped contributing. Naming the effect helps explain why the behavior matters without turning the discussion into a personal attack.

Leave room for the other person’s view

A framework can bring structure, but the conversation still needs to be a conversation. After describing the situation, behavior, and impact, pause. Invite the other person to share what they saw or what was happening for them.

That invitation could sound like: “How did you see that moment?” or “Was something making it hard to wait until Maya had finished?” The question isn’t a trick, and it shouldn’t be delivered as one. If the speaker asks for a response, they need to be ready to listen.

There may be context they didn’t know. Perhaps the person thought the client had asked them to step in. Perhaps there was a technical delay or a misunderstanding about who was leading the call. Context doesn’t erase impact, but it can shape a fair response. Listening helps distinguish a one-off misread from a pattern that needs attention.

This is especially important when there’s a power gap. A manager’s invitation to talk may not feel open if the employee expects a penalty for disagreeing. Leaders can make the invitation more credible by staying calm, asking follow-up questions, and showing that they’ve heard the answer—even when they don’t agree with every part of it.

Then make the next step clear

A useful conversation needs a landing point. What will happen next? The next step might be a request, a shared agreement, a follow-up check-in, or a change in process.

For the meeting example, the speaker might say: “On our next client call, let’s let the person presenting finish before others add context. If you see a concern, jot it down and raise it when they’re done.” That’s more useful than “Communicate better,” because it describes an action people can recognize.

Next steps should be specific and proportionate. Not every awkward moment needs a formal plan or a calendar invite. Sometimes the two people agree on a simple adjustment and move on. In a more serious or repeated situation, a manager may need to document expectations, set a review date, or explain what support is available.

The key is to avoid ending with a demand that leaves no room for discussion. A clear boundary may be necessary, especially when safety, respect, or policy is involved. Still, clarity doesn’t require threats. People can hear both the expectation and the reason behind it.

Where DESC fits

DESC is another communication framework, often used for assertive conversations. Its letters commonly stand for Describe, Express, Specify, Consequences.

  • Describe the situation in neutral terms.

  • Express how it affects you or the work.

  • Specify what you’d like to happen.

  • Consequences explains what may follow if the request is met—or, in some versions, what may happen if the behavior continues.

The final part can sound harsher than intended, so it helps to frame it thoughtfully. A consequence need not be a threat. It could be a positive outcome: “If we share updates by noon, I can include them in the client report.” Or, where a boundary is needed, it may explain a realistic next action: “If the interruptions continue, I’ll ask the meeting facilitator to manage speaking turns.”

Different teams and trainers may define the letters with slight variations. The useful thread is the same: describe what’s happening, communicate its effect, state a clear request, and make the path forward understandable. Like SBI, DESC is a guide, not a speech to recite word for word.

Self-advocacy is a professional skill

Self-advocacy often gets mistaken for being loud or demanding. In reality, it can be quiet and direct. It might mean asking for clearer priorities, naming an interruption, requesting feedback in a private setting, or explaining what support would help you meet a deadline.

A structure like SBI or DESC can help people speak up without shrinking their concern or inflating it. “When the project deadline changed in the team chat, I didn’t see the update until the afternoon. I had to redo part of the report. Could deadline changes also come through email?” That message describes an event, its impact, and a workable request.

Professional identity grows through moments like these. People learn what they value, what boundaries they need, and how they want to contribute. A person who raises a concern thoughtfully isn’t being difficult by default. They may be protecting the quality of the work—or making it easier for the team to collaborate.

Of course, one framework won’t solve every workplace problem. Some issues call for a private conversation; others need a manager, HR partner, union representative, or formal reporting channel. If a concern involves harassment, discrimination, safety, or retaliation, a neat feedback script may not be enough. The right response may involve following workplace policy and seeking support.

Keep the framework human

SBI and DESC are most helpful when they support a real exchange rather than replace one. Use plain language. Stick to what you know. Be clear about the effect, but don’t claim that your interpretation is the only possible one. Then invite a response and agree on a next step.

It also helps to choose the right setting. Sensitive feedback usually deserves privacy, while broad process changes may belong in a team discussion. Timing matters, too: a person who has just left a tense meeting may need a moment before they can listen well.

The point isn’t to remove discomfort from every workplace conversation. Some conversations are uncomfortable because something important is at stake. A simple structure can make that discomfort more manageable: describe the event, explain its impact, hear the other person’s perspective, and agree on what happens next.

That’s how feedback becomes more than a verdict. It becomes a way to build clarity, protect working relationships, and move the work forward.