Feedback does not have to be vague to sound respectful. You can be direct about what needs to change without attacking someone’s character, guessing their motives, or trying to control how they respond. The difference often lies in what you focus on: a specific action that can be discussed, rather than a broad judgement about the person.
A practical structure is to describe the situation, name the behavior you observed, explain its impact, and make a clear request. For example, instead of saying, “You’re careless,” you might identify a missing detail in a particular handover, explain what it made harder, and ask for that detail to be included next time. The conversation may still feel uncomfortable, but it gives both people something concrete to understand and address.

What makes feedback sound aggressive?
People often hear feedback as an attack when it sounds like a verdict on who they are: “You’re unreliable,” “You don’t care,” or “You’re impossible to work with.” These statements go beyond an observable event. They label a person, and the other person may end up defending their character instead of discussing what happened.
Feedback can also feel hostile when it assumes intent. “You left me out because you wanted to make me look bad” is not simply a description of an action; it is a claim about someone’s motive. Even if you have a strong reason to be concerned, presenting an interpretation as fact can close down the conversation before you have established what occurred. When the other person sees the issue differently, handle the disagreement without making it personal.
Other choices can make the issue harder to understand: using “always” or “never,” adding sarcasm, raising several old grievances at once, or criticising someone in front of other people. Vague instructions such as “be more professional” can also frustrate the listener because they do not specify what to do differently. To understand their account, use questions that invite a concrete answer rather than questions that hide an accusation.
Directness, by itself, is not aggression. A respectful message can be concise and firm: “The report needs the source figures included before it goes to the client.” It becomes more difficult to hear when it adds contempt, blame, or a sweeping judgement: “You never do a proper job.” The aim is not to remove the point from the feedback. It is to make the point fair, specific, and actionable.
Use situation, behavior, impact, and request
The Center for Creative Leadership describes the Situation–Behavior–Impact model, usually shortened to SBI, as a way to keep feedback focused on what happened. It asks you to identify a particular situation, describe an observable behavior, and explain its impact. You can then add a specific request or practical next step.
A useful version for everyday conversations is:
- Situation: When and where did this happen? Choose one identifiable occasion.
- Behavior: What did you see or hear? Describe the action without labelling the person.
- Impact: What effect did it have? State your experience or the practical consequence, and distinguish it from what you are assuming.
- Request: What would you like to happen next time? Make it specific enough to act on.
For example: “In yesterday’s handover, the final figures weren’t included. I couldn’t confirm the total before the client call. Could you add them to the shared file before the next handover?” This names a situation, an observable omission, its effect, and a concrete request.
The example is a model for structuring a conversation, not a guaranteed script. The wording should fit what actually happened and what you need. If the figures were available elsewhere, or the handover process was unclear, that context matters. Specificity should improve accuracy, not make an accusation sound more polished.
The Center for Creative Leadership also describes an extension, sometimes called SBII, that adds an inquiry about intent. After explaining your observation and its impact, you might ask, “What was happening from your perspective?” or “Was there something I may have missed?” This gives the other person room to explain without requiring you to withdraw your point.
Prepare one example and one clear request
Before starting, write down the one event you want to discuss. If you cannot point to a particular example, pause and consider whether you have enough information to give fair feedback. “You’re difficult in meetings” is a broad conclusion. “In Tuesday’s planning meeting, I was interrupted twice while explaining the timeline” is something the two of you can examine.
Then decide what change you are asking for. “Communicate better” does not tell someone which communication to change. A more useful request might be: “If the delivery date changes, could you message me before the end of the day?” A request can be direct without being an order, though in some roles or situations a clear instruction may be necessary.
Keep the conversation to one main issue where possible. If you bring up several unrelated incidents, the listener may struggle to understand what matters most, and you may end up debating the details of each one. If the issues are connected, explain the connection rather than presenting a list of complaints.
It can help to consider the setting and timing. A private conversation may be more appropriate for sensitive feedback than a public correction. If the issue is not urgent, choose a moment when you can speak without rushing. Workplace research on exactly when feedback is most effective is limited, so there is no universal timing rule. The practical goal is to have enough space for a clear exchange, not to wait indefinitely for a perfect moment.
You do not need to deliver a long preamble or hide the point inside compliments. A straightforward opening can be enough: “I’d like to discuss one part of the handover from yesterday and agree on how to handle it next time.” That makes the purpose visible without framing the other person as the problem.
Choose wording that describes actions, not character
Pay attention to whether your words can be checked against a particular event. “You ignored my message” may be an interpretation; “I sent the schedule on Monday and didn’t hear back before the deadline on Wednesday” is more specific. The second version does not prove why there was no reply, but it gives you a clearer starting point.
“I” statements can help show what you experienced, but they do not automatically make criticism fair or gentle. “I feel you’re incompetent” is still a character judgement. A more useful statement separates the event from your interpretation: “When the figures were missing from the handover, I couldn’t check the total before the call.”
Be careful with the impact part, too. Your experience is real, but your explanation of another person’s effect on a team may be an inference. You could say, “I was concerned that the client would get an incomplete total,” rather than “You made the whole team look unprepared,” unless you know that is what happened. If you are uncertain, say so: “I may have missed something—what was happening from your perspective?”
Here are a few useful language swaps:
- Instead of: “You’re careless.” Try: “The final figures were missing from yesterday’s handover, so I couldn’t confirm the total.”
- Instead of: “You need to communicate better.” Try: “If the delivery date changes, could you send me an update by the end of that day?”
- Instead of: “You never listen.” Try: “When I was explaining the concern in today’s meeting, you began responding before I had finished. Could you let me finish before we discuss it?”
- Instead of: “You did that on purpose.” Try: “When the plan changed and I wasn’t told, I was left working from the old version. Can you tell me what happened?”
Use the version that reflects the facts. A carefully worded sentence is not a substitute for checking that your description is accurate.
Stay clear if the other person reacts defensively
Even fair feedback can be uncomfortable. A calm tone cannot guarantee that someone will agree, feel appreciative, or respond without emotion. Your goal is to state the issue clearly and listen to the response—not to make the other person react exactly as you would like.
If they disagree with your description, ask what they saw differently. You might say, “I understand you remember it another way. Can we look at what was shared before the call?” If you discover that a detail was wrong, correct it. If the central issue remains, return to it without repeating the character judgement you were trying to avoid.
If they explain their intent, you can acknowledge it while still describing the effect: “I understand you were trying to finish quickly. The missing figures still meant I couldn’t check the total in time. How can we prevent that at the next handover?” Intent and impact can both matter. Asking about intent does not require you to dismiss the impact.
If the conversation starts turning into a list of counter-accusations, bring it back to the specific issue and the next step. If either of you is too upset to continue productively, it may be better to pause and agree to return to the discussion. Pausing does not mean the issue has disappeared; follow through if the feedback still needs to be addressed.
Listening is not the same as agreeing with everything you hear. Give the other person time to respond, ask clarifying questions, and consider whether new information changes your understanding. At the same time, you do not have to abandon a reasonable request simply because it is unwelcome.
Don’t over-soften serious feedback
Trying to sound kind can sometimes make feedback so indirect that the other person cannot tell what needs to change. A long, elaborate introduction or a “praise sandwich” can obscure the main point, especially when the issue is important. You can acknowledge someone’s effort if it is relevant, but praise should not be used to disguise or dilute a concern.
For serious or repeated issues, state what happened, what needs to change, and any relevant next step plainly. Avoid making consequences sound more certain or severe than they are. If you have responsibility for setting expectations, be specific about those expectations. If you do not, describe your concern and ask to agree on a workable approach.
Feedback quality matters more than simply giving more feedback. The CIPD’s evidence review identifies qualities such as specificity, relevance, constructiveness, credibility, and lack of bias as important, and notes that feedback can be counterproductive. A meta-analysis by Kluger and DeNisi also found that feedback interventions did not consistently improve performance; some reduced it. That review covered varied tasks and settings, rather than everyday personal conversations specifically. Neither source means that feedback should be avoided. They are reasons not to assume that any feedback, delivered in any way, will help.
These limits are important: a useful structure cannot guarantee a good response or make unfair criticism fair. The evidence cited is mainly workplace-focused, and the right approach may differ in close relationships, across cultural contexts, or where people have unequal power. If a situation involves intimidation, discrimination, or a safety concern, tactful wording alone may not be an adequate response.
A short checklist before you speak
Take a moment to check the message you plan to deliver:
- Can I name one specific situation rather than relying on “always” or “never”?
- Am I describing what I observed, rather than labelling the person or assuming a motive?
- Have I explained the impact as my experience or a practical consequence, not as an unquestionable verdict?
- Is my request clear enough for the other person to know what to do differently?
- Am I prepared to hear context that might change part of my understanding?
If the answer is yes, you can be plain. For example: “In yesterday’s handover, the final figures weren’t included. I couldn’t confirm the total before the client call. Could you add them to the shared file before the next handover? Was there something that made that difficult this time?” This wording does not guarantee agreement. It does make the concern easier to understand, discuss, and act on.