Articles · Communication
How to Use Written Communication Well
A quick structure for clearer async communication.
Shared Language editorial team
Published · Updated · 2 min read

Why this matters
Written communication helps people process, remember, and act.
Good written updates include
Include the practical pieces.
- Topic
- Decision needed
- Deadline
- Owner
- Next step
Keep it useful
Short and clear is better than long and vague.
Put the action before the background
A useful message might begin, “Please choose option A or B by Wednesday so we can place the order.” Follow with the information needed for that choice, then link to longer background if necessary. If no response is needed, say so. Separating a request from general information helps the reader decide what to do next.
Make the message easy to scan
Use short paragraphs and descriptive headings when a message has several parts. Keep related questions together and identify the most important one. Avoid relying only on color, a screenshot, or an unexplained abbreviation. A link should say what it opens, and the reader should have permission to access the destination.
Choose when conversation is better
Written communication is not automatically the best format for every situation. If a thread develops several competing interpretations, offer a brief conversation and then record the decision. Ask the people involved what format is useful. The aim is a shared understanding that can be found later, not a larger volume of messages or a record of every thought.
Try this next
Send one update using: Decision / Owner / Deadline / Next step.