Hard feedback is not harsh because it is specific. It becomes harsh when it turns a behavior into a character judgment, relies on vague labels, or gives the other person no workable path forward.
You can be direct about a missed expectation, a strained working pattern, or work that needs to change. The aim is not to make the feedback painless. The aim is to make it understandable and usable.
Start with an observable example
“You have been unreliable” may reflect a real frustration, but it leaves the recipient guessing which moments matter and what standard they missed. Replace the label with an example:
“The client update was due Monday morning and was sent Tuesday afternoon without a note about the delay.”
The example is concrete enough to discuss. It also keeps you from building the feedback around assumptions about effort or character.
Explain the impact without overstating it
After the example, describe what it affected:
“That meant the account team could not prepare for the client’s questions, and they had to adjust their schedule at the last minute.”
Impact language helps the person understand why the feedback matters. It is different from a dramatic conclusion such as “You made the whole team look bad.”
If you are not sure of the impact, say what you need to understand:
“I did not receive an update before the deadline. Can you walk me through what got in the way?”
Questions can be part of direct feedback. They are not a retreat from the issue.
Make a clear request
Feedback is easier to act on when it ends with a specific expectation:
“If you see that a deadline is at risk, please send me a note by the prior afternoon with the revised timing and any support you need.”
Avoid broad endings like “Please do better” or “Be more proactive.” A person may agree with those statements and still not know what different behavior looks like.
The full structure is example, impact, request:
“The client update was due Monday morning and was sent Tuesday afternoon without a note about the delay. That left the account team unable to prepare for questions. If a deadline is at risk, please alert me by the prior afternoon with a revised plan.”
Do not dilute the point with a compliment sandwich
Adding unrelated praise before and after every difficult message can make the feedback feel scripted or confusing. You can acknowledge good work when it is relevant, but do not use praise to hide the issue.
Instead of:
“You are wonderful to work with, and I really appreciate your energy. One small thing: the work is often late. But overall, great job!”
Try:
“I appreciate the care you put into the analysis. I need to address the delivery timing because the last two reports arrived after the agreed deadline. Let’s agree on a checkpoint that makes the timing more predictable.”
The tone is respectful because it is honest and proportionate.
Give the conversation room to continue
Even clear feedback should leave room for information you do not have. Ask a question that serves the next step:
“What would help you meet this expectation consistently?”
“Is there a dependency I should know about before we set the next deadline?”
Listening does not mean withdrawing the feedback. It means you are making a plan based on the full picture.
Written feedback needs extra care
Email can be useful for confirming expectations after a conversation. It is less useful for unloading several months of frustration. For a written note, keep the scope small and offer a conversation if the issue needs nuance:
“I want to follow up on today’s discussion. For the next reporting cycle, please send the first draft by Wednesday noon and flag any risks as soon as they appear. We can revisit the timeline in our check-in if needed.”
A final check
Read the draft and underline every judgment word: “careless,” “unprofessional,” “lazy,” “always,” “never.” Most feedback becomes clearer when those words are replaced by an example, an impact, and a request. Directness is not a raised voice. It is making the standard visible.