Delivering Hard Messages
Say no, give feedback, and break bad news — clearly is kindly.
- ✓Lead a hard message with the headline, not a cushion of caveats
- ✓Decline a request cleanly while keeping the relationship intact
- ✓Give feedback that is specific and actionable, not vague or personal
When the message is unwelcome — a no, a critique, bad news — the instinct is to bury it in softening, apology, and delay. That feels kinder but it's crueler: the reader hunts for the point, misreads how serious it is, and leaves more anxious. Clear is kind. Deliver the hard part early and plainly, own it, and pair it with a path forward.
Clear is kind — front-load the hard part
Cushioning the bad news in three paragraphs of preamble doesn't soften the blow; it makes the reader search for it and doubt how bad it really is. State the hard thing plainly and early — 'We're not moving forward with the project' — then explain. Warmth lives in the explanation and the next step, not in hiding the headline. Being vague to spare someone's feelings usually spares your discomfort, not theirs.
Say no to the request, yes to the person
A clean 'no' is a gift — it lets people plan. Decline the specific ask directly, give a brief honest reason (not a pile of excuses), and where you can, offer an alternative or a door left open. 'I can't take this on this quarter — I'm at capacity on the launch. I could revisit in Q3, or Sam may have room now.' No guilt, no false maybe that wastes everyone's time.
Feedback: behavior, impact, ask
Vague or personal feedback ('be more proactive', 'your attitude') can't be acted on and breeds defensiveness. Name the specific behavior you observed, its concrete impact, and the change you want: 'The last two PRs shipped without tests (behavior), and both caused a production bug (impact). Going forward, run the test suite before requesting review (ask).' Describe what happened, not what kind of person they are.
Brené Brown's research-backed maxim — 'clear is kind, unclear is unkind' — captures why hedged bad news backfires: ambiguity transfers your discomfort onto the reader. The Situation-Behavior-Impact (SBI) model from the Center for Creative Leadership keeps feedback specific and non-personal, which makes it easier to hear and to act on.
Before & after
Hey! So I've been thinking a lot about your proposal and I really appreciate all the effort you put in, it's clearly well thought through, and I'd love to support it in some way, it's just that timing-wise things are a bit tricky right now and I'm not totally sure where it fits, so maybe we can find some time to chat about it at some point?
I'm going to pass on the proposal for now — it's strong, but it doesn't fit this quarter's priorities. If budget opens up after Q3 planning, I'd want to revisit it. Thanks for the thorough work on it.
I feel like you've kind of been dropping the ball lately and not really bringing your A-game — I need you to step it up and be more reliable going forward.
The last two releases went out without the test suite run, and both caused a customer-facing bug (behavior + impact). Going forward, I need tests run and green before you request review (ask). Can you build that into your checklist?
Practice
Write a response, then get coached. Revise and re-score as many times as you like — iteration is the point.