As you become more senior, more of your influence happens in writing. Decisions are made in documents you are not in the room for, and your reputation travels through messages written by and about you.
Clear writing is therefore one of the highest-return skills available, and it is mostly technique rather than talent.
The one habit that fixes most writing
Put the point first.
Most people write the way they thought: background, context, analysis, and finally the conclusion. Readers want the opposite. Start with what you need or recommend, then supply the reasoning for those who want it.
- Before: “Following our review of the vendor options and several conversations with the team…”
- After: “We should renew with Vendor A for one year. Here’s the reasoning.”
Structures worth memorizing
The update: what changed, what it means, what happens next, what you need from the reader. Four short paragraphs at most.
The recommendation: the recommendation, the options considered, the trade-offs, the cost, the decision you need and by when.
The request: the ask in the first sentence, the deadline, the context, and what happens if it slips.
Bad news: what happened, the impact, what you have done already, what you need. Early, factual and without defensive padding.
Make it readable in ten seconds
- Short paragraphs, three or four lines at most.
- A subject line or title that states the point: “Decision needed: renewal by Friday” beats “Vendor update”.
- Bold the decision, deadline or number that matters.
- Bullets for lists, prose for arguments.
- One idea per paragraph.
Cut the words that weaken you
- Hedges that add nothing: “just”, “I think maybe”, “sort of”.
- Apologies for existing: “Sorry to bother you” at the start of a normal request.
- Jargon that hides meaning: “leverage synergies” says less than “share the team”.
- Passive voice where responsibility matters: “the report was delayed” versus “I delayed the report”.
Read your draft aloud. Anything you stumble over needs rewriting.
Writing with AI, without sounding like everyone else
AI is genuinely useful for structure, tightening and a first draft of routine messages. It also produces a recognizable, slightly airless style, and readers are starting to notice.
A reliable process:
- Write your own messy version first, so the thinking is yours.
- Ask the assistant to tighten it, or to point out where it is unclear.
- Rewrite the result in your own words, keeping the specifics.
- Check every fact, number and name.
Never paste confidential material into an unapproved tool, and be honest when colleagues ask. Our guide to AI skills employers want covers the wider habits.
Practice that compounds
- Rewrite one email a day to be half as long.
- Write a weekly summary of your work for your manager, even if nobody asked. It builds the muscle and quietly creates your promotion case, as described in our guide to asking for a promotion.
- Take a document you admire and work out why it is clear.
- Ask a colleague to mark the exact sentence where they lost interest, which is the feedback habit from our guide on giving and receiving feedback.
Frequently asked questions
Does writing matter in technical roles?
More than most people expect. Design documents, incident reports and pull request descriptions are how technical decisions get made and remembered, as our article on AI and software developers notes.
How long should a work email be?
Short enough to read on a phone without scrolling twice. If it needs more, write a document and send a three-line summary with the link.
English is my second language. How do I sound more confident?
Favor short sentences and plain verbs; they read as clear and direct in any language. Grammar tools help with mechanics, and reading your drafts aloud catches most of the rest.
