Most leadership messages fail before anyone reads them.

Not because the leader doesn't have something worth saying. But because by the time the message reaches employees, it has been workshopped, approved, and edited into something that sounds like a press release. Vague. Formal. Disconnected from the people it's supposed to reach.

Employees can smell it. And they delete it.

Here's how to write one that actually lands.

Start with the one thing

Every leadership message should have a single point. Not three priorities. Not a quarter in review. One thing the reader needs to understand or do by the time they finish reading.

If you can't name that one thing before you start writing, you're not ready to write. Go back to the outline. The message isn't ready yet.

This sounds obvious. It almost never happens in practice. Most leadership messages try to accomplish too much at once and end up accomplishing nothing. Employees finish reading and have no idea what they were supposed to take away.

Lead with the point. Build around it. Stop when you're done.

Write to a person, not a workforce

"To all employees" is not an audience. It's an avoidance strategy.

The best leadership messages are written with a specific person in mind. Not a demographic, not a job level, not "the frontline workforce." A person. Someone the leader actually knows, or can picture clearly. What does that person need to hear right now? What are they worried about? What would make them feel like this message was written for them and not just at them?

When you write to one real person, the message becomes specific. And specific is the only thing that works. Vague language is the enemy of trust. Employees don't need inspiration. They need relevance.

Sound like a human being

Leadership messages often fail the most basic test: they don't sound like a person wrote them.

Read the draft out loud. Does it sound like something the leader would actually say in a room full of people? Or does it sound like it was written by a committee and reviewed by legal?

Both of those things may be true. But the final message can't sound like it.

This is where internal communications work earns its keep. A strong communications partner doesn't just clean up grammar. They protect the leader's voice through every round of review. They know which edits make the message safer and which ones make it worse. And they push back on the ones that make it worse.

Acknowledge the hard thing

Employees are not naive. If there's something difficult in the message, something uncertain, something that affects their lives, they already know it's there. Glossing over it doesn't protect them. It just signals that leadership isn't being straight with them.

The fix is simple. Name it. One sentence. Then move forward.

"This has been a hard quarter and I know many of you have felt it." That's enough. You don't have to dwell. But you do have to acknowledge. A message that skips over the hard thing in favor of optimism loses the reader at the skip.

Serious news requires a flat tone. The warmth can come back later. But the acknowledgment has to come first.

Keep it short enough to respect their time

Employees are busy. They are reading your message between tasks, on a phone, in a break room. They are not sitting at a desk with a cup of coffee and nowhere to be.

Every sentence has to earn its place. If a paragraph exists to make the leader feel better about what they're saying rather than to serve the reader, cut it. If the message can be said in 200 words, don't write 500.

Brevity is not a style choice. It's a form of respect. And employees notice when they're not getting it.

The test

Before you send anything, ask one question: if I were the person receiving this, would I know what to do with it?

If the answer is no, it's not done yet. Go back to the one thing. Find it. Lead with it. And cut everything that isn't serving it.

That's the whole job. It's harder than it sounds. But it's learnable. And when you get it right, employees notice that too.

If your leadership team is ready to communicate in a way that actually connects, here's how I work. Or if you're ready to get started, let's talk.