How people actually read messages
Most workplace messages are skimmed. Readers glance at the sender and the subject, read the first few lines, and decide whether to deal with it now, later or never. If the main point is in the fourth paragraph, there is a fair chance it will be missed. This is not a flaw in readers; it is a reasonable response to a heavy inbox.
Structure is how you work with that habit rather than against it. The goal is that a reader who spends ten seconds still gets the essential message, and a reader who spends two minutes gets the details. There is no guarantee any message will be read or answered, but a clear structure makes it more likely.
Put the point first
The most dependable rule is to start with what matters most: the request, the decision or the news. Background comes after.
Many writers do the reverse. They narrate the history, build context, and arrive at the request at the end. That order feels natural to the writer, who lived through it, but it makes the reader wait.
Compare these two openings, both hypothetical.
Before: “Hi Jordan, I hope your week is going well. I was reviewing the vendor contracts last Tuesday and noticed that a few of them are up for renewal, and I know the budget discussions are happening soon, so I thought…”
After: “Hi Jordan, could you confirm by Friday whether we should renew the three vendor contracts that expire in December? Details are below.”
The second version tells Jordan what is needed, by when, and what the topic is. The background can follow for anyone who needs it.
A simple template
For many everyday messages, this order works:
- Greeting and the point: one or two sentences stating the request or news.
- Context: the minimum background needed to understand or decide.
- Details: facts, options or steps, as needed.
- Next step: who does what, and by when.
Not every message needs all four parts. A quick question may need only the first. A longer update may use all of them, with headings or bullets in the details section.
Make the ask unmistakable
If you need something, say so plainly and make it easy to answer.
- State the action: “Please approve,” “Can you review,” “I need a decision on.”
- Give a date or time frame when it matters, and say why if the reason is not obvious.
- Ask one thing per message where possible. Several unrelated requests in one message tend to get partial answers.
- If you have several questions, number them so that the reader can reply by number.
- If the message is purely informational, say so: “No action needed.”
A clear call to action is not only for marketing; it applies to ordinary emails, too.
Use short paragraphs and white space
Dense blocks of text are hard to scan. Aim for paragraphs of one to four sentences, with a blank line between them. Each paragraph should carry one idea, and its first sentence should say what it is about.
Use lists and formatting only where they help
Bullets and numbering are useful when the content is truly a set of items or steps. Three options to choose from, a list of attachments, or a sequence of instructions all fit. A single flowing explanation does not, and breaking it into bullets can strip out the connecting logic.
Bold text can highlight a deadline or a key action. If everything is bold, nothing stands out, so use it sparingly. Avoid mixing many colors, fonts or sizes in a message.
Mind the subject line and the preview
In email, the subject line is the first thing read. Make it specific: “Decision needed by Friday: vendor contract renewals” tells more than “Quick question.” Our guide to writing subject lines goes deeper. In chat, the first line often shows in a notification, so open with the point rather than “Hi” alone, which forces the reader to wait for the second message. Following good email etiquette about greetings and sign-offs helps the message feel considerate without adding length.
Keep it as short as the content allows
Brevity helps, but the right length depends on the content. A message that is too short can leave out context and prompt a round of follow-up questions. A good test: after reading, would the recipient be able to act without having to ask you anything? If yes, the message is complete. If more than that is included, consider cutting. The techniques in concise writing apply here.
For long or complex topics, consider a short message that points to a fuller document, or a brief call. Attachments should be mentioned in the text, not hidden.
Worked example: a project update
Subject: Project update: on track, one decision needed
“Hi team,
The website update is on track for the March 15 launch. I need one decision from you by Wednesday: whether to include the new pricing page in this release or the next.
Where we are
- Design is complete.
- Development is about two-thirds done.
- Testing begins next week.
Decision details Including the pricing page adds roughly three days of work and could move the launch date. Waiting avoids that but means pricing stays unchanged for another release.
Next steps Please reply with your preference by Wednesday. I will update the schedule on Thursday.
Thanks, Amira”
The reader gets status and request in the opening lines, can skim the bullets, and knows exactly what happens next.
Check before sending
Reread the first two lines as if they were all the reader would see. Do they carry the point? Is the request clear? Is anything essential hidden at the bottom? A one-minute check like this often makes the difference between a message that is answered and one that is lost.