You Typed It. But Did They Read It?

You spent 10 minutes writing that email.

They spent 10 seconds reading it. Maybe.

Written communication feels like the easy version of communication. You have time to think. Nobody's staring at you. You can edit before you hit send. And yet — somehow — things still get missed, misread, or completely ignored.

Here's what's actually going on.

The message you sent and the message they received are not the same document.

When you speak, people have your tone, your face, your energy to fill in the gaps. In writing, all of that disappears. What's left is just words on a screen — and people fill in the blanks with whatever they're already feeling that day.

That casual Friday Slack message you fired off? Marcus read it as passive-aggressive. The detailed project email you spent 20 minutes on? Jordan skimmed the first two lines and replied to something you didn't even ask. The meeting notes you dutifully compiled? Nobody read them. Nobody.

This isn't about writing skills. It's about awareness — knowing who's on the other end of your message, and what they actually need from you.

The Four Readers on Your Team

Your team doesn't read the same way. And if you're writing the same way to all of them, you're losing at least half of them on any given message.

Here's what I see over and over in my coaching work:

The Bottom-Line Reader wants the point in the first sentence. Not the third. Not after the context-setting paragraph you thought was helpful. The first sentence. They're not being rude — they're efficient. If you bury the ask, they've already moved on to the next thing on their list before they found it.

The Big Picture Reader wants energy and context before they get to the details. A cold, clinical message lands flat — even if it's technically complete. They're scanning for why this matters, and if they don't find it, the message feels like noise.

The Relationship Reader is reading your tone more than your words. A message that's blunt or matter-of-fact — even if completely accurate — can land like a rebuke. They notice what you didn't say. Skipping a check-in before diving into the task can feel, to them, like something's wrong.

The Detail Reader wants completeness and structure. Vague messages make them uncomfortable. If your email raises questions you didn't answer, expect a reply with six clarifying questions — because to them, that ambiguity is a problem to solve before they can move forward.

None of these are wrong. They're just different. And your job as a leader isn't to write the perfect universal message — it's to know who you're writing to.

The Channel Actually Matters

This is where a lot of leaders get tripped up. It's not just what you write — it's where you send it.

Email is for anything that needs context, documentation, or more than one person looped in. It's not for urgent requests, and it's definitely not for feedback that deserves an actual conversation.

Slack or Teams is for quick coordination and informal check-ins. It's great for team energy and fast answers. It's terrible for anything you'll need to find later, anything nuanced, or anything where tone could be misread.

Text is for time-sensitive and brief. It's personal by nature — use it that way. If you're sending someone a three-paragraph text, that's an email.

Reports and formal updates are for leadership visibility and data-driven decisions. The mistake most leaders make here is writing for themselves — organizing the information in the order you gathered it, rather than the order your reader needs it. Lead with the headline. Save the details for the people who want them.

Meeting minutes are not a transcript. Nobody needs to know who said what in what order. What they need: the decisions that were made, and who owns what next. If your meeting notes don't answer those two questions clearly, they're not doing their job.

So What Do You Actually Do With This?

Knowing your readers exist is one thing. Writing for them is another. 

For the Bottom-Line Reader: Lead with the ask or the decision, every time, without exception. Put the most important information in the subject line or the first sentence. If they have to scroll to find out what you need, you've already lost them. Think of it as writing your conclusion first and letting the context follow.

For the Big Picture Reader: Open with the why before the what. A single sentence of context, "here's why this matters"  changes how they receive everything that follows. Match your energy to the message. A flat, transactional tone on something important will read as disconnected, even if your words are technically right.

For the Relationship Reader: Don't skip the human part. A brief acknowledgment before you get to business isn't small talk — it's the thing that makes the rest of the message land. Watch your word choice, especially in writing, where there's no tone to soften it. "This needs to be fixed" and "here's what I'd like to see happen" say similar things very differently.

For the Detail Reader: Give them structure they can follow — headers, clear sections, numbered steps if there are multiple asks. Be specific. "By end of week" is not a deadline. "By Friday at 3pm" is. If there are open questions, acknowledge them rather than leaving them hanging. They will find every gap you left, so close them yourself.

Before You Hit Send: Three Questions Worth Asking

Regardless of who you're writing to, these three questions will catch most of the problems before they happen:

1. What do I need them to know, decide, or do? If you can't answer that in one sentence, your message probably isn't ready to send. Clarity in your head first, then on the page.

2. Does the tone match what I actually mean? Read it back, out loud if you have to, and ask whether a reasonable person could misread it. If there's a way to take it wrong, someone will.

3. Am I writing this for me, or for them? There's a version of your message that makes you feel thorough and complete. And there's a version that actually gets read, understood, and acted on. Those are not always the same message.

That last question is the one worth sitting with.

The Real Question

Written communication isn't just a skill, it's a leadership habit. Every message you send is either building clarity and trust on your team, or quietly eroding it.

The good news? You don't have to overhaul everything at once. Just start with one message today. Before you send it, ask yourself who's reading it and what they actually need from you.

That shift alone will change more than you think.