Early in a career, it's tempting to write the hardest emails five different ways before sending any of them. Draft one, too blunt. Draft two, too soft. Draft three, somewhere in between but somehow worse than both. Exclamation points go in to make bad news feel friendlier, then come out because they read as fake, then go back in. It never works. A client can always tell when someone is performing calm instead of just being direct.
What Actually Changes
Here's what tends to change with time: clients don't actually want cushioning. They want clarity, delivered by someone who isn't afraid of the conversation. Cushioning reads as hedging, and hedging reads as someone who isn't sure how bad the news really is, which is a much scarier thought for a client than the news itself.
Two Versions of the Same Update
When something's gone sideways on a project, an estimate that was wrong, a developer out sick during a critical sprint, a deliverable that isn't going to land the way it was promised, there's a version of the update that protects your own comfort in the moment, and a version that protects the relationship over the long run. They are almost never the same email, and the habit of reaching for the first one is a hard one to break.
The version that protects the relationship tends to do three specific things differently:
It leads with the fact, not the apology. Say what happened before you say how sorry you are. Clients need the information to start making decisions on their end, and an apology up front just delays the moment they get what they actually need from you.
It comes with a plan, not just a problem. Even a rough, half-formed plan beats a beautifully worded apology with no next step attached. A plan says "this is already being worked," which is the thing a client is actually anxious to know.
It gets sent by you, not routed through someone "more senior." The instinct to escalate hard conversations upward is understandable. But clients remember, specifically and for a long time, who told them the truth directly. Escalating the message, even with good intentions, quietly signals a lack of confidence in carrying it yourself, and it also signals that the team isn't as autonomous as it was promised to be.
It Never Fully Goes Away
The stomach-drop before sending one of these emails never fully goes away, even after six years as a PM and several more in account management. What can change is expecting it to disappear, and letting it decide how long you wait before you hit send. The dread is just part of the job. The delay is the part that's optional.
Kim Scott's framework for this is worth holding onto: care personally, challenge directly, and don't let the first collapse into an excuse to skip the second. Cushioning bad news isn't kindness. It's usually just discomfort, dressed up as consideration.
Source: Scott, K. (2017). Radical Candor: Be a Kick-Ass Boss Without Losing Your Humanity. St. Martin's Press.
