To give feedback without sounding harsh, describe a specific event, name the impact you actually observed, ask for the other person’s account, and agree on a realistic next step. Speak respectfully and choose a setting where they can respond. Direct wording can still land badly; a clear structure is not a guarantee of agreement.
Try: “In Tuesday’s draft, three totals differed from the source sheet. I spent 25 minutes reconciling them before we could send it. How did you check the figures this time?”
That gives you a concrete issue to discuss. “You’re careless” gives you a judgment to argue about.
A useful structure, with room to listen
The Center for Creative Leadership’s Situation–Behavior–Impact framework starts with the situation, observable behavior and impact. CCL also recommends inquiry about intention rather than assuming why someone acted.
For an everyday conversation, use this practical extension:
- Situation and observation: When did it happen, and what did you see or hear?
- Impact: What happened as a result? Separate a known effect from a concern about what might happen.
- Inquiry: What was going on from their side? What were they trying to achieve?
- Agreement: What action, support and follow-up make sense now?
The fourth step is an action-planning addition, not what the “I” in SBI stands for. Avoid using any framework as a monologue that ends before the other person speaks.
Example: a missed deadline
Manager: “We agreed on a Tuesday draft. It arrived Friday, leaving an hour for review. What happened from your side?”
Employee: “I waited for the revised numbers. I thought a draft with gaps would waste your time.”
Manager: “I should have been clearer that an incomplete draft was useful. Next time, could you send the available sections Tuesday and mark what’s missing?”
Employee: “Yes, if I know who to ask about the missing input.”
Manager: “I’ll name that owner in the brief. Let’s check how the next handoff goes on Friday.”
This fictional example does not excuse the missed handoff. It identifies a misunderstanding and creates a more workable agreement. Before treating a missed expectation as a performance problem, check that it was communicated and supported; University of Iowa HR guidance recommends that check.
Example: a sharp message
In the Support thread, you wrote “This is obvious” before explaining the fix. The next three messages were about that wording rather than the customer issue. What were you trying to get across?After listening, you might agree: “Next time, lead with the missing information and the next action. If the request is unclear, ask for the detail you need.”
Avoid claiming everyone felt disrespected unless you actually know that. You can say “I read it as dismissive” or describe the visible effect on the thread. The other person’s intent and the impact may differ; neither should be guessed into certainty.
Example: interrupting in a meeting
“In the 11 a.m. meeting, you started answering while Priya was still explaining the issue. We moved on without hearing the customer constraint. What did you notice? For the next discussion, can we let the person finish before adding a question?”
If there is a time-critical correction, acknowledge that exception. The goal is useful turn-taking, not a rule that nobody can ever interrupt. If you are the meeting facilitator, you also have a role in making space.
As a new manager, separate a request from a standard
A peer might say: “Can we agree a handoff time that gives both teams room to review?” A manager can state a legitimate requirement: “For this release, source checks need to be complete before we send the numbers.”
Authority does not remove the need to listen. Ask about workload, access and competing priorities, then provide the support or decision your role requires. If you have never explained the standard, set it clearly rather than presenting it as a repeated violation.
Feedback can reinforce good work too
Use the same specificity when something went well:
“In yesterday’s client call, you summarized the two options before asking for a decision. That let us confirm the scope while everyone was present. Please keep that summary step in the next handoff.”
This identifies what to continue. “Great job” can be sincere, but by itself it does not tell the person which action helped.
If it lands badly
Pause and check: “Which part do you see differently?” or “What did you hear me saying?” You may have missing facts, unclear wording or a poorly chosen moment. A defensive reaction does not prove your feedback was correct.
CCL’s feedback guidance emphasizes preparation, specific actions and active listening; it also notes that you cannot control whether the recipient likes or agrees with the feedback. For the next turn, see responding to defensive reactions.
Before and after the conversation
Before: write your example, the observed impact and one genuine question. Choose a private setting for sensitive feedback. Remove assumptions about character or motives.
After: recap the action, the support you will provide and the check-in date. At the check-in, notice improvement specifically or discuss the remaining obstacle. Do not stop at getting the words out.
TalkCraft’s Give Hard Feedback Clearly module lets you compare written replies in scenarios such as The Deflector, with a coaching note explaining each choice. If you are on the receiving side, start with how to respond to criticism.
