Elena managed a support team of nine people from her home in Portland, and every one of them worked somewhere else. On a call she was warm, clear, and quick. The problem was that almost none of her job happened on calls anymore. It happened in Slack, in email, and in comments on shared documents. And in writing, Elena was a different person.
Her messages were long. They started with context and built toward the point, the way a story does. By the time a reader reached what she actually needed, they'd stopped reading. Her team started replying "sorry, what's the ask?" often enough that it became a joke. Her director didn't joke. He started skimming, then he started missing things. One of the things he missed was a staffing request buried in paragraph four of a Thursday email.
When the request finally surfaced two weeks later, he asked why she hadn't flagged it. She had. It was right there. He just never got that far.
If you work remotely, this is the skill that decides whether you get heard or get skimmed. It isn't grammar or vocabulary. It's the ability to put a message in front of a busy person and have them understand it, act on it, and think well of you for sending it.
Your writing is your body language now
In an office, people also had your tone of voice, your face, and the fact that you walked over instead of sending an email. Remote, what's left is text. People read your confidence, your competence, your mood, and your respect for their time from what you write. They do it in the first two lines, whether you meant to say any of it or not.
The cost of getting it wrong is easy to miss, because a confusing message doesn't produce an error. It produces a slightly wrong answer, a delayed reply, a follow-up question, or a decision made on half the information. Nobody sees the drag. Everyone feels it.
Writer-first vs. reader-first
Elena's real problem was the order of her thinking. She wrote writer-first: she started where her thinking started and walked the reader through the same journey. That feels natural because it's how you came to understand the problem yourself.
Reader-first writing asks a different question: what does the person on the other end need to know, in what order, to do what I'm asking? Those two sequences are almost never the same. Your thinking started with background and ended with a conclusion. Your reader needs the conclusion first, so they can decide whether the background even matters to them.
Here's a test that catches most problems. Before you send anything longer than two sentences, ask yourself:
If this person reads only the first line, will they know what I need?
If the answer is no, the message isn't done.
A before-and-after example
Here's how Elena's staffing email actually opened:
"Hi Mark, hope your week is going well. I wanted to give you some context on how the queue has been trending since the product update went out. As you know, we've seen a shift in ticket mix toward billing questions, which take longer to resolve on average, and the team has been doing a great job keeping up but I'm starting to see some strain in the numbers..."
It's polite, accurate, and a wall. Mark decided it was a status update and moved on. The actual request, approval for a six-week contractor, showed up three paragraphs later.
Here's the same message, rebuilt reader-first:
"Mark, I'd like approval to bring on one support contractor for six weeks, starting the 15th. Cost is about $9,000. Reason: since the product update, billing tickets are up 40% and resolution time has climbed from 6 hours to 11. The team is absorbing it now but I expect we'll miss SLA by month-end without help. Happy to walk through the numbers if useful, but if this looks fine, a yes here is all I need."
Same content. The second version leads with the ask, gives the cost, explains why, names what happens if nothing changes, and tells Mark how little effort a reply takes. He answered it in four minutes.
The pattern: headline, context, next step
Underneath that rewrite is a structure you can use on almost everything you send.
- Headline. The ask or the answer, in one sentence, at the top. Not a greeting followed by background. The point.
- Context. The minimum your reader needs to trust the headline. Minimum is the key word. Include the numbers, the reason, and the consequence. Leave out the history of how you figured it out.
- Next step. What you want to happen now, stated so plainly the reader can reply with one word if they agree. Include a deadline when there is one.
Watch out for "let me know your thoughts." It hands the reader a chore. Replace it with a real question. "Can you approve this by Friday?" is a question. "Let me know your thoughts" is homework.
A few more examples of strong next steps:
- "If this looks right, reply 'go' and I'll send it to the client tomorrow."
- "Can you pick A or B by Wednesday noon? If I don't hear back, I'll go with A."
- "No action needed. Just wanted you to hear this from me first."
Too short is also a problem
Dev, an analyst in Chicago, had the opposite habit. His messages were short in the wrong way:
"Numbers look off. Can you check?"
Which numbers? Off how? By when? Dev thought he was being efficient. He was actually moving the work of understanding him onto everyone else. His fix asked the same question Elena's did, what does the reader need to act?:
"The Q3 revenue figures in the board deck don't match the finance export, off by about $40k in the September row. Can you check the source by end of day tomorrow? Board meeting is Thursday."
Three sentences, no back-and-forth required.
Match the length to the channel
Mixing up channels is a common way good messages get lost:
- Chat (Slack, Teams): A sentence or two. If it needs more than four lines, it's probably an email or a document. Long chat messages disappear in the scroll.
- Email: For anything that needs to be found later or involves more than one decision. Aim for under 200 words, with the ask in the first line and supporting detail in a clearly separate section below.
- Document: For anything people will refer back to, argue with, or build on. Here structure matters more than brevity. Use headings so a skimmer can find their part.
Getting the tone right on a screen
Text has no tone, so readers supply one. And the one they supply is usually worse than the one you meant. "Fine." reads as annoyed. "Can we talk?" reads as trouble. "Per my last message" reads as a threat.
Elena ran into this from the other side. Her long, careful messages read as anxious, and from a manager, anxious reads as disappointed. Her team started apologizing in replies to messages that weren't criticisms. She'd been stressing out nine people for months with sentence structure.
The fix isn't exclamation points everywhere. That reads as insincere fast. Instead, pay attention to the few places where tone actually lives:
- The opening line sets the temperature.
- The closing line confirms it.
- Any sentence that could read as criticism needs a word that tells the reader it isn't one.
"Can you fix this?" is neutral on paper and sharp on a screen. "Can you take a look at this when you get a chance? Not urgent." is the same request with the temperature turned down.
What if your company's culture runs long and chatty, and a reader-first message looks abrupt? Add one line of warmth, then keep the structure. "Hope the offsite went well. Quick one:" followed by the actual message. Warmth costs one sentence. Burying the point costs the whole message.
Common mistakes to watch for
- Opening with pleasantries and background. Warmth is fine. Making it the headline isn't.
- Writing a novel in chat. Move it to email or a doc and post a one-line pointer.
- Typing through a conflict. If you've gone three rounds and you're still not aligned, or you're starting to feel defensive, or someone's feelings are involved, stop writing and call. Text is efficient for information and terrible for repair.
- Confusing volume with presence. Someone who sends three clear, well-timed messages a day gets heard. Someone who sends thirty gets muted.
The takeaway
You don't need to become a better writer in some general sense. You need to move the point to where your reader will find it. Headline first, just enough context, a next step someone can answer in one word.
Try it this week. Take the next three messages you send that run longer than two lines, and rewrite each one so the first sentence holds the ask or the answer. Then find one thread that's gone past three rounds and end it with a quick call instead of a fourth message.
Elena rewrote her staffing email in five minutes once she saw the problem. Six months later, her director mentioned, unprompted, that she'd become one of the easiest people on his team to work with. Nothing about her work had changed. She'd just started putting the point where he could find it.
Want one place to plan your week and keep these habits going? Try Web & Things free.