Lead with the decision
Put the request, conclusion, or changed condition in the first useful sentence. Context can follow once the reader knows why it matters.
Name the actor
Prefer a visible subject and active verb. “The team will ship Friday” carries more information than “A Friday release is anticipated.”
Use concrete nouns
Replace vague references such as “this,” “things,” or “the situation” with the actual project, document, risk, or decision.
Cut throat-clearing
Remove openings that apologize for writing, repeat the subject line, or narrate that you are about to explain something.
Keep one job per paragraph
A paragraph should explain one claim, instruction, or group of evidence. Start a new paragraph when the reader's task changes.
Prefer measured detail
Dates, owners, quantities, and constraints create trust. “Soon” and “a lot” make the reader estimate what the writer already knows.
Write useful headings
A heading should help someone scanning the page predict the content below it. Topic labels are better than decorative phrases.
Match tone to consequence
Use warmth for collaboration and directness for decisions. Do not hide a deadline, risk, or refusal behind decorative language.
Read for missing steps
Before sending, ask what the recipient must know or do next. Add the link, file, owner, deadline, or approval path they would otherwise request.
Edit at the point of use
Make the final pass inside the email, document, or message where the words will live. That preserves surrounding context and reduces copy-paste mistakes.