Kindness does not mean avoiding hard truth.
Honesty does not mean being harsh.
Good feedback is:
- clear
- specific
- respectful
- focused on behavior and work
- given close to the event
Why this matters
Two failure modes dominate feedback in companies, and they tend to travel together. Some leaders default to vague kindness — “great job, just keep it up” — and the person they are trying to help learns nothing. Other leaders default to blunt honesty without care — “this is unacceptable” — and the person they are trying to help shuts down and defends.
The discipline is both at once: clear about what and why, kind about who. The clearer the behavior, the less you have to defend the kindness. The kinder the tone, the harder it is to dismiss the content.
What it looks like in practice
A team member missed a deadline on a reporting deliverable last week. The manager prepares to give feedback the next day — not three months from now at a review — using the pattern from Scripts: When giving feedback:
“Here is what happened. Here is the impact. Here is what needs to change next time. How can I help?”
In practice:
- What happened. The Friday report did not land until Tuesday; the operations review on Monday had to be run from incomplete data.
- The impact. Three people held questions for the team that the team could not answer until the data caught up.
- What needs to change. If the data is not going to be ready, send a one-line yellow status by Thursday at noon so the reviewers can re-plan.
- How can I help. Is there something in the process that is making this harder than it needs to be?
Notice the structure: it is direct about the behavior and the impact, it is forward-looking about the fix, and the closing question is genuine. It is not soft. It is also not harsh.
What it looks like when violated
The most common failure: feedback that comments on the person rather than the work. “You’re not detail-oriented” is a character assessment; the person cannot act on it without arguing about who they are. “The Friday report missed three data validations that the prior version caught” is an observation; the person can act on it by Tuesday.
A second common failure: feedback delayed. The pattern of remembering ten things at a quarterly review — some of which happened in week two — produces defensive listening at the review and zero correction in week three. Feedback works in proportion to how close it sits to the event.
A third failure: feedback that is technically accurate but intentionally cruel. Saying it “straight” is not a license to make the receiver smaller. See Guardrail 3.
How to apply it this week
- Identify one piece of feedback you have been holding for more than a week. Decide whether it is still worth giving. If yes, give it this week using the four-line pattern above.
- When you give feedback this week, name a behavior and an impact, not a character trait. If you cannot point at a specific moment, the feedback is not ready.
- Notice your tone in the closing. The genuine “how can I help” matters more than the words before it.