You leave a meeting thinking, “That could have gone better.” Your colleague leaves without knowing anything is wrong. By Friday, frustration has become “You need to communicate better.” The gap between those two moments is where useful feedback often disappears. Before speaking, turn your reaction into information another person can examine.
Start with a moment, not a label
Choose one recent, relevant event. Describe what you directly saw or heard, and distinguish it from your interpretation. “The handover did not include the client’s revised deadline” is observable. “You do not care about detail” assumes a motive and turns one incident into an identity.
The Situation–Behavior–Impact approach associated with the Center for Creative Leadership offers a useful scaffold: identify the context, describe the behavior and explain its effect. It is a scaffold, not evidence that your interpretation is complete. Follow it with a question that makes correction possible.
“You need to take more ownership.”
“Yesterday’s tracker had no owner for the testing task. Could you confirm who is responsible before the next handover?”
Explain the impact proportionately
Connect the event to work, not to a dramatic prediction. You might say, “I scheduled the review using the old deadline, so we had to rearrange two people’s work.” If you do not know the impact, say so. Avoid claiming that “everyone is frustrated” unless you are authorized to represent those people and have reliable information.
Ask yourself whether the expectation was clear beforehand. Feedback about an unstated rule may reveal a management gap rather than an individual failure. If the person lacked access, training or authority, discuss that condition alongside the behavior. Accountability becomes more credible when it includes the system around the person.
Make room for the reply
Ask, “What was happening from your side?” Then listen without composing a rebuttal. A defensive response may reflect embarrassment, disagreement, previous unfairness or a real error in your account. You cannot diagnose which from tone alone. Summarize what you heard and check it before returning to the request.
If the discussion becomes heated, slow down: “I want us to understand this rather than rush it. Shall we take a break and return this afternoon?” A pause needs an agreed return point. Otherwise it can feel like withdrawal or an unresolved threat. Do not insist on continuing simply because you prepared a careful opening.
Agree something observable
Replace “improve communication” with a specific behavior and a workable occasion. For example: “For the next handover, include the current deadline and the decision owner in the shared note.” Ask what support is needed and whether the proposed step fits the person’s role. A request should not quietly transfer responsibility they cannot exercise.
Agree when you will check back. The review can be brief: did the change happen, did it help, and should anything be adjusted? Write down consequential agreements in a shared place. A record should clarify expectations, not create a secret scorecard. Follow your organization’s policies for formal performance documentation.
Receive feedback without agreeing too quickly
When you are on the receiving end, you can listen without accepting every conclusion. Ask for an example, explain relevant constraints and distinguish the valid part from the disputed part. “I agree the update was late. I do not agree that I ignored the request; it arrived while I was covering the incident.”
Thanking someone for raising an issue does not require an immediate promise. If you need time, say when you will respond. If feedback concerns a protected characteristic, discriminatory standards or retaliation, keep an appropriate factual record and consider a formal support route rather than treating it as ordinary coaching.
Use praise with the same precision
“Great job” can be kind but hard to repeat. “Your summary separated the decision from the open questions, which helped us finish the review” makes a contribution visible. Check preferences before giving public recognition. Some colleagues welcome attention; others prefer a quiet note or credit in the work record.
Do not turn appreciation into a sandwich around a difficult message. People can learn to distrust the praise. Offer recognition when it is earned and address concerns directly, with context and respect.
Write one observation, one impact and one question. Then check: am I describing a behavior this person can reasonably change?
Know when coaching is not enough
Repeated serious errors, harassment, threats and safety breaches may require an established organizational process. Do not promise confidentiality you cannot maintain, investigate beyond your role or delay necessary reporting while searching for perfect wording. A fair process, appropriate support and clear responsibilities matter more than a polished script.
Further reading
Explore the Center for Creative Leadership on feedback; Douglas Stone and Sheila Heen’s Thanks for the Feedback; and Kim Scott’s Radical Candor. These offer different lenses, not universal instructions. Adapt any framework to the evidence and the people involved.