A manager forwards you a long, polite, well-punctuated email. You read all of it. You still have no idea what you’re supposed to do. That’s the real problem with written communication skills at work, and it’s almost never about grammar.
We spend a lot of time telling people to build vocabulary and fix their commas. Useful, but it misses the point. The emails that fail in most teams aren’t failing because a word was misspelled. They’re failing because the reader can’t tell what they’re being asked to do. Good workplace writing works because it’s unmissable.
Why is my writing unclear even when my grammar is fine?
Because unclear writing is usually unclear thinking. The email is vague because the ask is vague.
When a message rambles, the writer usually hasn’t decided exactly what they want, who owns it, or by when. So they hedge. They add context on top of context, hoping the reader will assemble the request themselves. The reader usually won’t. They’ll skim, feel a vague sense of “I should probably reply to this later,” and move on.
It’s a familiar scene in coaching conversations about communication. A manager insists their team ignores their emails. We read three of those emails together, and the manager can’t say in one sentence what they were asking for either. The writing was foggy because the intent was foggy. Fix the thinking, and the words get clear on their own. Before you write anything, answer one question: what do I want this person to do after they read this? If you can’t say it in a sentence, you’re not ready to write yet.
Lead with the ask
Put the request in the first line. Not after the pleasantries, not after the background, not on line nine. First.
Most people bury the ask because it feels abrupt to open with a demand. So they warm up: a paragraph of context, a bit of history, a gentle build toward the actual point. By the time the reader reaches the request, they’ve already decided how much attention this email deserves, and they decided it based on the first two lines, which contained nothing actionable.
Flip the order. Say what you need, then explain why. The reader who only reads two lines still knows what to do. The reader who wants the full context keeps going. You lose nothing by leading with the ask, and you rescue everyone who was going to skim anyway. Leading with the ask is a small change to your communication skills that costs nothing and pays off immediately.
One message, one job
Give each message a single job. When you stack three unrelated asks into one email, at least two of them get dropped.
Watch what happens. You need Ryan to send the budget, confirm a meeting, and review a doc. You put all three in one email because it feels efficient. Ryan reads it, mentally files the first ask, and forgets the other two by the time he’s done reading. Now you’re chasing him for the two things that got buried, and it looks like he dropped the ball, when really the email set him up to.
If you genuinely need several things, make them impossible to miss: a short numbered list, each item with its own owner and deadline. But be honest about whether they belong together at all. Two urgent, unrelated requests are often two emails. The principles of effective communication that hold up in practice almost always come back to focus: one message doing one job well beats one message doing four jobs badly.
How can managers improve written communication skills?
Write for the skim, not the close read. Assume your reader is on their phone, between meetings, giving you ten seconds. Design the message so that even that reader knows what to do.
That means the important parts have to survive skimming. Put the ask and the deadline where the eye lands first: the opening line, or in bold. Keep paragraphs short. Use a list when you have a list. White space does real work here: it’s what lets a busy reader find the one sentence that needs them. If your key request is sitting in the middle of a dense block of text, assume it will be missed, because it will.
This is also where the mechanics finally earn their place. Proofreading matters, reading widely to build a sharper vocabulary matters, and a habit of reviewing before you send matters. But they matter in service of the ask, not instead of it. A perfectly proofread email with a buried request is still a failed email.
A buried ask, rewritten
Here’s a real pattern, cleaned up. A manager wants a teammate, Ryan, to send updated figures before a client call on Thursday. Version one is what most of us actually send.
Before:
Subject: Touching base
Hi Ryan,
Hope you’re doing well and had a good weekend. I wanted to reach out because I’ve been thinking about the upcoming client call and where we’ve landed with a few things. As you know, the Q3 numbers shifted a bit after the last review, and there was some back and forth with finance about how to present the regional breakdown. I know you’ve been swamped, so no pressure, but it would be great to make sure we’re aligned before we talk to them. Let me know your thoughts when you get a chance.
Thanks so much!
Nowhere in that email does it say what Ryan should do, or when. He’ll read it, feel vaguely responsible for something, and reply “Sounds good, let’s sync.” Nothing gets sent. Thursday arrives and the numbers aren’t ready.
After:
Subject: Need updated Q3 figures by Wed noon (client call Thu)
Hi Ryan,
Can you send me the updated Q3 figures with the regional breakdown by Wednesday noon? We’re presenting them to the client Thursday morning and I want time to build the slides.
Context: finance revised the regional split after last week’s review, so the old version is out of date. If anything’s still open on your end, tell me today and we’ll sort it.
Thanks, Ryan.
Nothing about the tone or the relationship changed. What’s different is that Ryan now knows exactly what to send, in what format, and by when, from the subject line alone. The context is still there for anyone who wants it, but it’s demoted below the ask, which is where it belongs. That single reordering is the difference between an email that moves work forward and one that generates a follow-up chase two days later.
Cut the hedging and the preamble
Trim the throat-clearing. “I just wanted to quickly reach out because I was hoping you might possibly be able to” is nine words of nothing wrapped around one small request.
Hedging feels polite, but it usually does the opposite. It makes the reader work harder to find what you actually mean, and it makes an ordinary request sound like an apology. You can be warm and direct at the same time. “Can you send me X by Friday?” is not rude. It’s respectful of the reader’s time. The softeners (“just,” “quickly,” “maybe,” “if it’s not too much trouble”) pile up and blur the ask until it looks optional. If you want a reliable reply, don’t make your request sound like something the reader can skip.
The same goes for preamble. Background belongs after the ask, and only as much as the reader needs to act. Everything else is you thinking out loud on their time. When you struggle to strip it down, that’s often the signal your own thinking isn’t settled yet, the same fog we cover in overcoming barriers to effective communication.
Proofread for the action, not just the typos
Do a final read, but not the one you think. Instead of only hunting for typos, read the message once as the recipient and ask: could I tell exactly what to do, and by when, from this alone?
Typos are the easy layer. The harder, more valuable check is whether the action survives. Read your draft as if you’re the busy person receiving it. If you can’t find the ask in five seconds, neither can they. This is a better use of the “wait, then reread” habit than pure copyediting: you’re hunting for a missing instruction, not a stray comma.
You can build this faster than you’d expect by reading well-written messages on purpose. Pay attention to the emails and docs in your organization that always get a fast, clean response. They almost never have fancier vocabulary. They just make the ask obvious. Borrowing that structure will do more for your writing than any grammar drill, and it pairs well with verbal communication skills that follow the same logic: say what you need, then explain.
The through-line
Strong written communication skills come down to one discipline: decide what you want the reader to do, then write so they can’t miss it. Grammar, vocabulary, and proofreading all sit underneath that, useful in support of a clear ask, useless in place of one. When your writing is fuzzy, treat it as a signal that your thinking is fuzzy, and go clarify the ask before you touch the wording. Clearer asks also make better decisions downstream, because people are acting on what you actually meant, and they compound into a more functional team environment where messages get answered the first time.
If you want to see how your communication lands before you send the next high-stakes message, try Risely’s oral communication assessment. It’s a fast way to spot where your clarity holds up and where the ask tends to get lost, whether you’re writing it or saying it out loud.