../

Clear writing

How to write prose that a busy reader understands on the first pass: the core principle, the canonical rules (Orwell, Strunk, Zinsser, Pinker) and where they go wrong, structure, sentences, word choice, punctuation, readability formulas and an editing process. Applying it to memos, emails and pitches is in persuasive writing; docs, design docs and commit messages are in technical writing. Reader-first thinking is the same idea as in UX/UI design.

The core principle

Clear writing is clear thinking made visible, aimed at a specific reader. Almost every rule below is a corollary of three ideas.

IdeaMeaningTest
Know what you thinkyou cannot write clearly about something you have not decidedcan you state the point in one sentence, out loud, without notes?
One main pointevery document, section and paragraph has one jobcould a reader summarize it in a line, and would it match yours?
Reader firstthe reader has less context, less time and less interest than youwhat does this reader already know, and what do they need to do next?

Zinsser puts the first one bluntly in On Writing Well (chapter "Simplicity"): "Clear thinking becomes clear writing: one can't exist without the other." Paul Graham makes the same point from the other side in "Putting Ideas into Words" (2022): writing about something usually shows you that you did not know it as well as you thought.

Practical consequences:

  • Write the point first, then the document. If you cannot write the one-sentence version, you are still thinking, not writing. That is fine, but label the draft as thinking.
  • Name the reader. "The CFO who will approve this" produces a different document from "people interested in our infrastructure". Write for one real person; others will cope.
  • Decide what the reader should do or believe afterward. Informing, deciding and persuading need different shapes (see persuasive writing).
  • The reader cannot interrupt. In conversation a confused listener asks. On the page, every gap you leave is filled by a guess or a closed tab.

The canonical rules

Orwell's six rules

George Orwell, "Politics and the English Language" (Horizon, 1946). Before the rules he lists the questions a "scrupulous writer" asks of every sentence: "What am I trying to say? What words will express it? What image or idiom will make it clearer? Is this image fresh enough to have an effect?" Then:

I think the following rules will cover most cases:

i. Never use a metaphor, simile or other figure of speech which you are used to seeing in print.

ii. Never use a long word where a short one will do.

iii. If it is possible to cut a word out, always cut it out.

iv. Never use the passive where you can use the active.

v. Never use a foreign phrase, a scientific word or a jargon word if you can think of an everyday English equivalent.

vi. Break any of these rules sooner than say anything outright barbarous.

(Text as published by the Orwell Foundation; some printings add serial commas in rules i and v.)

RuleWhat it targetsModern caveat
i. stale figuresclichés that substitute for thought ("move the needle", "low-hanging fruit")a fresh, precise metaphor is still one of the best explanation tools
ii. long wordsinflation: utilize, facilitate, commencethe precise technical word beats a vague short one (idempotent is fine for engineers)
iii. cut wordspadding, throat-clearing, redundancycutting can remove the connectives that make logic followable
iv. active voicehidden agents, evasions ("errors were made")the passive is often right (see sentences)
v. jargonin-group words used on outsidersjargon is efficient inside the group; the error is using it on the wrong reader
vi. break the rulesrules are tools, not lawthe most ignored and most important rule

Orwell's own essay contains passives and long words; he says himself that "one could keep all of them and still write bad English". The rules are a checklist against habits, not a definition of good prose.

Strunk and White

William Strunk Jr privately printed The Elements of Style for his Cornell students in 1918; E. B. White revised and expanded it for Macmillan in 1959. The useful core is in Strunk's original "Elementary Principles of Composition" (rule numbers from the 1918 text):

#Rule (1918 wording)Keep it?
8Make the paragraph the unit of composition: one paragraph to each topicyes
9As a rule, begin each paragraph with a topic sentence; end it in conformity with the beginningyes, for expository prose
10Use the active voiceas a default, not a ban
11Put statements in positive formyes: "late" beats "not on time"
12Use definite, specific, concrete languageyes, the most valuable rule in the book
13Omit needless wordsyes, but it only helps if you can tell which words are needless
15Express co-ordinate ideas in similar formyes (parallelism)
16Keep related words togetheryes
18Place the emphatic words of a sentence at the endyes (end focus)

Strunk's rule 13 in full: "Vigorous writing is concise. A sentence should contain no unnecessary words, a paragraph no unnecessary sentences, for the same reason that a drawing should have no unnecessary lines and a machine no unnecessary parts. This requires not that the writer make all his sentences short, or that he avoid all detail and treat his subjects only in outline, but that he make every word tell." The second sentence is the part everyone forgets: concision is about every word earning its place, not about brevity.

The critique. Linguist Geoffrey Pullum's "50 Years of Stupid Grammar Advice" (Chronicle of Higher Education, April 2009) argues that the book's "advice ranges from limp platitudes to inconsistent nonsense". His main points:

  • Much of the style advice is harmless but empty: "Omit needless words" is "useless" because "The students who know which words are needless don't need the instruction."
  • The grammar is wrong. Of the four examples offered to show the passive, Pullum shows three contain no passive at all ("There were a great number of dead leaves lying on the ground").
  • The anti-passive bias ignores information flow: a passive sounds bad when its subject is newer than the agent, and natural otherwise ("The bill was paid by an anonymous benefactor").
  • Rules against starting with however, against which in restrictive clauses and for singular none are contradicted by the usage of respected writers.

Verdict: use Strunk's composition rules as prompts; ignore its grammar pronouncements; never enforce "no passives" mechanically.

Zinsser: clutter and simplicity

William Zinsser, On Writing Well (first edition 1976). The chapter "Simplicity" opens: "Clutter is the disease of American writing." His fix: "the secret of good writing is to strip every sentence to its cleanest components. Every word that serves no function, every long word that could be a short word, every adverb that carries the same meaning that is already in the verb, every passive construction that leaves the reader unsure of who is doing what—these are the thousand and one adulterants that weaken the strength of a sentence." (Wording from the 1980 edition.)

Clutter typeExampleClean
inflated phrase"at this point in time""now"
redundant adverb"totally unique", "smiled happily""unique", "smiled"
qualifier"in a funny sort of way", "rather", "quite"delete
euphemism"negative patient care outcome""the patient died"
buzzword"leverage our learnings going forward""use what we learned"

Zinsser also insists that "Writing is hard work. A clear sentence is no accident." Most clear sentences are rewrites.

Pinker: The Sense of Style

Steven Pinker, The Sense of Style (2014), is the best modern guide because it explains why prose is hard to read, using cognitive science rather than decree.

Classic style. Borrowed from Thomas and Turner's Clear and Simple as the Truth (1994). Pinker: "The guiding metaphor of classic style is seeing the world. The writer can see something that the reader has not yet noticed, and he orients the reader's gaze so that she can see it for herself." Writing is a window onto the world; writer and reader are equals in a conversation; the writer shows rather than argues about how hard the topic is.

Classic style doesClassic style avoids
points at concrete things, examples, numberstalking about the writing itself ("in this section we will…")
states claims with appropriate confidencereflexive hedging to avoid being wrong
treats the reader as intelligent and uninformedcondescension or in-group shorthand
uses the concrete noun and the active verbabstractions stacked on abstractions
presents the conclusion, not the writer's strugglethe literature-review tour before the point

The curse of knowledge. Pinker calls it "the single best explanation I know of why good people write bad prose": once you know something, you cannot easily imagine not knowing it. The term comes from economists Camerer, Loewenstein and Weber (1989). In Elizabeth Newton's 1990 Stanford study, people tapped the rhythm of well-known songs and predicted listeners would name about half; listeners named 2.5%. Symptoms in writing: undefined abbreviations, skipped steps, "obviously", examples that only make sense if you already understand.

FixHow
show a draft to a real outsidersomeone from the target audience, not a teammate
read your own draft after a gapdays, not minutes; you forget enough to see the gaps
define on first useevery abbreviation and every term the reader might not share
add the examplean abstraction plus one concrete instance beats three abstractions
replace labels with descriptions"the Q3 thing" → "the pricing change we shipped in September"

Zombie nouns. Helen Sword's term ("Zombie Nouns", New York Times Opinionator, 23 July 2012) for nominalisations: verbs and adjectives turned into abstract nouns (investigate → investigation, decide → decision, able → ability). They drain the agent and the action from a sentence. Pinker describes the move as taking "a perfectly spry verb" and embalming it into a noun.

ZombieAlive
"The implementation of the migration resulted in a reduction of latency.""Migrating cut latency."
"We had a discussion about the prioritization of the roadmap.""We discussed which roadmap items come first."
"Failure to provide confirmation will result in cancellation.""If you don't confirm, we'll cancel your booking."
"There was an agreement among the team on the adoption of TypeScript.""The team agreed to adopt TypeScript."

Metadiscourse is writing about the writing: "In this section I will discuss…", "As noted above…", "It is worth mentioning that…". A little signposting helps in long documents; most of it is throat-clearing. Pinker's alternatives: open with the question the section answers, or just state the point.

Hedging. Compulsive qualifiers (somewhat, arguably, to some extent, it could be said that) protect the writer, not the reader. Hedge once, precisely, where there is real uncertainty, and say how uncertain: "probably (we have three weeks of data)" beats "it may potentially be the case".

Plain language

The Plain Writing Act of 2010 (Public Law 111-274, signed 13 October 2010) requires US federal agencies to use "plain writing" in public documents, defined as "writing that is clear, concise, well-organized, and follows other best practices appropriate to the subject or field and intended audience." The Federal Plain Language Guidelines (PLAIN, March 2011, revision 1 May 2011) turn that into practice; the material formerly on plainlanguage.gov now lives in digital.gov's plain language guides.

Guideline themePractice
write for your audienceidentify readers and their top tasks; answer their questions in their order
organizemost important first; useful headings (often questions); short sections
wordsshort, everyday words; the same term for the same thing; define unavoidable jargon
sentencesactive voice; "you" for the reader; "must" for obligations; short sentences
layoutlists for steps and options; tables for comparisons; white space
testcheck comprehension with real readers, not with formulas alone

Plain language is not dumbing down. Experts read plain prose faster too, and nobody has ever complained that a specification was too easy to understand.

Structure

Structure matters more than sentences. A reader who knows where the argument is going forgives clumsy sentences; perfect sentences in the wrong order still fail.

PatternRuleUse for
BLUF (bottom line up front)put the conclusion, request or decision in the first line or twoemails, status updates, memos, anything someone might stop reading
Inverted pyramidmost important information first, then supporting detail in descending importancenews-style updates, incident notices, announcements
Pyramid Principleanswer first, then grouped supporting arguments (Minto)recommendations; see persuasive writing
Topic sentencethe first sentence of a paragraph states what the paragraph showsexpository paragraphs
One idea per paragrapha new idea starts a new paragrapheverything
Chronologicalevents in orderincident timelines, histories, tutorials
Problem → solutiondescribe the pain before the fixproposals, design docs

BLUF comes from US military correspondence; the inverted pyramid from newspaper practice. Both exist because readers stop early.

Topic sentences and skimming

If a reader reads only the first sentence of each paragraph, they should get the argument. This "skim test" is the single most useful structural check.

BeforeAfterWhy
"Over the last quarter the team has been looking at several aspects of the onboarding flow, including drop-off, time to activate and support volume.""Onboarding loses 40% of sign-ups at the email-verification step."the topic sentence states the finding, not the activity
"There are a number of considerations regarding the database choice.""Postgres fits our workload better than MongoDB for three reasons."announces the claim and the shape of what follows
"Security is important.""Every endpoint that changes data must check the session's role."specific, testable, actually says something

Parallelism

Items in a list, a comparison or a series take the same grammatical form (Strunk's rule 15).

BeforeAfter
"The plan covers hiring, how we will budget, and a timeline for launch.""The plan covers hiring, budget and launch timing."
"Steps: 1. Install the CLI 2. Configuration of the token 3. You should now run the tests""1. Install the CLI. 2. Configure the token. 3. Run the tests."
"She is fast, accurate and has experience.""She is fast, accurate and experienced."

Lists vs prose

Use a list whenUse prose when
items are parallel and independent (options, requirements, steps)ideas depend on each other (because, therefore, unless)
order matters (numbered steps)you are making an argument
the reader will scan or check items offnuance and trade-offs matter
there are 3–9 itemsthere are 2 items (a sentence is shorter)

Bullets hide missing logic: three bullets can sit side by side without anyone stating how they relate. Bezos's 2004 email banning slides at Amazon's senior meetings made this point: "If someone builds a list of bullet points in word, that would be just as bad as powerpoint." Use lists for data, prose for reasoning.

Sentences

Active and passive voice

Active: subject does the action ("The deploy script deleted the table"). Passive: subject receives it ("The table was deleted", optionally "by the deploy script"). A passive needs a form of be (or get) plus a past participle; "There were leaves on the ground" and "The server is down" are not passives.

Prefer active whenPassive is right when
the agent matters and is knownthe agent is unknown or irrelevant: "The server was restarted at 02:00."
the passive would hide responsibility: "mistakes were made"the thing acted on is the topic you are continuing: "The parser has a bug. It was introduced in v2.3."
instructions: "Run the migration"you want the new or heavy element at the end: "The prize was won by a team of three first-year students from Leeds."
the sentence gets shorterthe convention requires it (methods sections, some legal text)

Strong verbs, fewer nouns

The action of a sentence belongs in its verb. Hunt for weak verbs (make, do, have, give, provide, perform, conduct, is) attached to action nouns.

BeforeAfterWhy
"We performed an analysis of the logs.""We analyzed the logs."nominalisation → verb
"The report provides a description of the outage.""The report describes the outage."same
"There is a need for us to reduce costs.""We need to cut costs."expletive "there is" plus zombie noun
"It is recommended that users update.""Update to 4.2."hidden agent; instruction as command
"The team made the decision to postpone.""The team postponed."the decision is implied
"Our goal is the facilitation of faster onboarding.""We want new users productive in a day."abstraction → concrete target

Given-new and end focus

Readers process a sentence by linking its start to what they already know, then adding the new part (the "given-new" principle from Haviland and Clark's psycholinguistics research in the 1970s). English also puts emphasis at the end of a clause (Strunk's rule 18). Together: start with the familiar, end with the new or important.

BeforeAfterWhy
"Moving to Postgres in March was what let us drop the document store, because JSONB support is included in Postgres.""We moved to Postgres in March. Its JSONB support let us drop the document store."each sentence starts with something already mentioned
"A 40% cost reduction is expected from the new caching layer.""The new caching layer should cut costs by 40%."the number is the news; put it last
"We should ship on Friday, in my view, given the risks.""Given the risks, we should ship on Friday."the recommendation lands last; qualifiers move to the front

Chains of given → new across sentences produce cohesion: each sentence picks up where the last one ended. Topic-hopping (every sentence starting with a new subject) feels choppy even when each sentence is fine.

Sentence length

There is no correct length; there is a correct variation. Uniform short sentences read like a telegram; uniform long ones exhaust working memory.

GuidelineDetail
average 15–20 wordsa common plain-language target; not a hard cap
vary deliberatelya short sentence after long ones lands a point
one main clause per ideasplit when a sentence has two "and"-joined main points
keep subject and verb closelong insertions between them force the reader to hold the subject in memory
front-load conditions only when short"If the build fails, rerun it." fine; a four-line "if" clause first is not
avoid noun stacks"user account password reset email template" → "the template for password-reset emails"

Positive, concrete, specific

BeforeAfter
"not unlikely""likely"
"did not remember""forgot"
"The results were not insignificant.""Conversion rose from 2.1% to 2.9%."
"a period of unfavourable weather""a week of rain"
"improve performance""cut p95 latency from 800 ms to 200 ms"
"soon""by Friday 3 October"

Word choice

The table below is a working list. "Instead of" items are not banned; they are defaults to question.

TypeInstead ofWriteNote
wordyin order toto"in order to" occasionally helps avoid ambiguity
wordydue to the fact that / owing to the fact thatbecause
wordyin spite of the fact thatalthough
wordyat this point in time / at the present timenow
wordyin the event thatif
wordywith regard to / in relation toabout, on
wordyfor the purpose ofto, for
wordyhas the ability to / is able tocan
wordya large number of / a majority ofmany / most
wordyprior to / subsequent tobefore / after
wordyin close proximity tonear
wordyon a daily basisdaily
wordythe question as to whetherwhetherStrunk's own example
wordyit is important to note that(delete)if it is important, the reader will notice
wordyin terms of(rewrite)usually hides a vague relation
inflatedutilize / utilizationuse
inflatedfacilitatehelp, enable, run
inflatedcommence / terminatestart / end
inflatedendeavortry
inflatedsufficient / numerousenough / many
inflatedapproximatelyaboutkeep "approximately" in technical specs if house style wants it
nominalisationmake a decisiondecide
nominalisationconduct an investigationinvestigate
nominalisationprovide assistancehelp
nominalisationgive consideration toconsider
nominalisationachieve a reduction inreduce
redundant paireach and everyeach, every
redundant pairfirst and foremostfirst
redundant pairnull and voidvoid
redundancyend result / final outcomeresult / outcome
redundancypast history / future planshistory / plans
redundancybasic fundamentalsfundamentals
redundancycompletely finished / very uniquefinished / unique
redundancyclose proximity / advance planningnear / planning
hedgeI think / I believe / it seems that(delete) or give the confidence levelthe byline already says it is your view
hedgequite, rather, somewhat, fairly, relatively(delete) or quantify"relatively fast" → "twice as fast as v1"
hedgemay potentially / might possiblymay / mightdouble hedge
weaselsome people say / it is widely believedname who, cite where
weaselup to 50% fastertypically 30% faster (median of N runs)"up to" hides the typical case
weaselsignificantly (not statistical)the number"significant" implies a test in technical writing
weaselindustry-leading, best-in-class, world-classthe evidencereaders discount unsupported superlatives
weaselvirtually, essentially, basically(delete) or be precise
jargonleverage (verb)use
jargonsynergywhat exactly combines, and the gain
jargonbandwidth (for time)time, capacity
jargoncircle back / touch base"I'll reply by Tuesday"give a time
jargonmove the needleraise X by Y
jargongoing forwardfrom now on, or delete
jargonimpactfuleffective, or state the effect
jargonlearningslessons, findings
jargonrobust / scalable / seamlessthe actual property: "handles 10× traffic"adjectives without numbers

Punctuation essentials

MarkRuleExample
comma, non-restrictive clausecommas around information that could be removed without changing which thing you mean"My brother, who lives in Leeds, is a doctor." (one brother)
no comma, restrictive clauseno commas when the clause identifies which one"My brother who lives in Leeds is a doctor." (implies other brothers)
that vs whichUS style reserves which for non-restrictive clauses; British usage allows restrictive which"the bug that broke login" / "the bug, which broke login, …"
comma after long introductory elementhelps parsing"After the migration finished, we reran the tests."
comma splicedon't join two independent clauses with only a comma"The build failed, we rolled back." → full stop or semicolon
semicolonjoins closely related independent clauses; separates list items that contain commas"The build failed; we rolled back." / "Leeds, UK; Lyon, France; Porto, Portugal"
colonintroduces what the first clause promises: a list, an explanation, an example"One thing blocks launch: the payment provider."
em dash (—)a strong break for an aside or an amplification; use sparingly"The fix — one line — took three days to find."
en dash (–)ranges and connections; British style often uses a spaced en dash where US uses an em dash"pages 10–20", "London–Paris route"
hyphencompound modifiers before a noun"a well-known issue", "an open-source tool", but "the tool is open source"
apostrophepossession and contraction, never plurals"the team's plan", "it's" (= it is), "its" (possessive), "APIs"
Oxford (serial) commacomma before the final and/or in a list of three or more"Rust, Go, and Python"

The Oxford comma is a style choice, not a rule. Chicago, the Google developer style guide and the Microsoft style guide use it; AP and many British newspapers generally don't. Pick one per document and use it consistently; add one anyway wherever omitting it creates ambiguity ("I thanked my parents, Ayn Rand and God"). The comma is not always trivial: in O'Connor v. Oakhurst Dairy (US Court of Appeals, First Circuit, 2017) a missing serial comma in a Maine overtime exemption decided the case in the drivers' favor.

Readability formulas

Formulas estimate difficulty from surface features: sentence length and word length (syllables). With WW = words, SS = sentences and YY = syllables:

Flesch Reading Ease (Rudolf Flesch, 1948; higher is easier, roughly 0–100):

FRE=206.835−1.015 WS−84.6 YW\text{FRE} = 206.835 - 1.015\,\frac{W}{S} - 84.6\,\frac{Y}{W}

Flesch–Kincaid Grade Level (Kincaid and colleagues for the US Navy, 1975; approximate US school grade):

FKGL=0.39 WS+11.8 YW−15.59\text{FKGL} = 0.39\,\frac{W}{S} + 11.8\,\frac{Y}{W} - 15.59
FRE scoreUS gradeDescription
90–1005thvery easy
80–906theasy; conversational
70–807thfairly easy
60–708th–9thplain English
50–6010th–12thfairly difficult
30–50collegedifficult
10–30college graduatevery difficult
0–10professionalextremely difficult

Worked example. A 100-word paragraph with 5 sentences and 150 syllables: W/S=20W/S = 20, Y/W=1.5Y/W = 1.5, so FRE=206.835−20.3−126.9≈59.6\text{FRE} = 206.835 - 20.3 - 126.9 \approx 59.6 and FKGL=7.8+17.7−15.59≈9.9\text{FKGL} = 7.8 + 17.7 - 15.59 \approx 9.9. Rewritten as 8 sentences with 135 syllables (W/S=12.5W/S = 12.5, Y/W=1.35Y/W = 1.35): FRE ≈79.9\approx 79.9, FKGL ≈5.2\approx 5.2.

Other formulas (Gunning fog, SMOG, Coleman–Liau, Automated Readability Index) use similar inputs and give similar rankings.

Limits. Formulas were built on school texts and Navy manuals and measure proxies, not comprehension.

Formula blind spotConsequence
meaning and logica shuffled paragraph scores the same as the original
word familiarity"Kubernetes" counts as 4 syllables of difficulty; "ontic" counts as easy
reader knowledgea specialist reads dense jargon faster than a layperson reads "easy" text
structure and layoutheadings, lists and examples don't count
gamingchopping sentences raises the score and can reduce cohesion

Use a formula as a smoke alarm (a grade of 16 on a customer email means something is wrong), never as a target. The real test is a reader: ask someone from the audience what the text says and what they would do next.

Editing process

Drafting and editing are different jobs. Draft fast without judging; edit slowly in passes, from large to small, because fixing words in a paragraph you will delete is wasted work.

  1. Structure

    • Is the main point in the first paragraph (or the first line of an email)?
    • Does the order match the reader's questions?
    • Skim test: read only headings and first sentences. Does the argument survive?
    • Cut or move whole sections that don't serve the point.
  2. Paragraphs

    • One idea each, stated in the topic sentence.
    • Each paragraph follows from the last; add the missing link where it doesn't.
    • Split paragraphs longer than about 6–8 lines on screen.
  3. Sentences

    • Agent as subject, action as verb; convert zombie nouns.
    • Given before new; the important element last.
    • Vary length; split sentences with two main clauses joined by "and".
  4. Words

    • Run the word-choice table: wordy phrases, hedges, weasels, jargon.
    • Replace vague adjectives with numbers or examples.
    • Same term for the same thing throughout.
  5. Proofread

    • Names, numbers, dates, links, attachments.
    • Read aloud or with text-to-speech; stumbles mark bad sentences.
    • Last: spelling and punctuation (a spell-checker, then your eyes).
TechniqueWhy it works
Read aloudthe ear catches rhythm problems, missing words and sentences you run out of breath in; Paul Graham recommends it in "Writing, Briefly" (2005)
Cut 10%Stephen King, in On Writing (2000), describes adopting a rejection slip's formula: second draft = first draft minus 10%
Waita day's gap reduces the curse of knowledge; you read what is there, not what you meant
Change the mediumprint it, change the font, read on your phone; familiarity hides errors
Reverse outlinewrite one line per paragraph of the finished draft; gaps and repeats become obvious
Outsider readthe only direct measure of clarity; ask "what is this asking you to do?"
Search for ticsgrep your own crutch words (just, very, really, actually, basically, in order to)

Common mistakes

MistakeSymptomFix
writing before thinkingthe conclusion appears in the last paragraphmove it to the top; rewrite from there
burying the ledebackground first, point on page 2BLUF
curse of knowledgeundefined terms, skipped stepsoutsider read; define on first use
throat-clearing"I wanted to reach out to touch base about…"start with the second sentence
zombie nouns"-tion", "-ment", "-ance" everywhere; weak verbsput the action back into the verb
hedging everything"perhaps", "arguably", "somewhat" in every paragraphhedge once, precisely
wall of text15-line paragraphs, no headingsone idea per paragraph; descriptive headings
bullet souplists of fragments with no logic between themprose for reasoning
inconsistent terms"user", "customer", "account holder" for the same thingpick one; add a glossary
vague quantities"significant growth", "soon", "many users"numbers, dates, names
elegant variationsynonyms for the same concept to avoid repetitionrepeat the term; readers assume a new word means a new thing
over-applying rulesno passives ever, no sentence over 20 wordsrules serve the reader, not the other way round
one-pass editingtypos fixed in a structurally broken draftedit in passes, largest first

Templates

Editing checklist

STRUCTURE
[ ] Main point stated in the first paragraph / first line
[ ] I can say the point in one sentence
[ ] Reader named; I know what they should do next
[ ] Headings + first sentences alone carry the argument
[ ] Every section serves the main point (else cut)
 
PARAGRAPHS
[ ] One idea per paragraph, stated first
[ ] Each paragraph follows from the previous one
[ ] No paragraph longer than ~8 lines on screen
 
SENTENCES
[ ] Agent is the subject, action is the verb
[ ] Zombie nouns turned back into verbs
[ ] Given before new; important words at the end
[ ] Passives only where they help
[ ] Sentence length varies; average around 15-20 words
 
WORDS
[ ] Wordy phrases, hedges, weasel words removed
[ ] Jargon defined or replaced for this reader
[ ] Vague adjectives replaced by numbers or examples
[ ] One term per concept, used consistently
 
PROOF
[ ] Read aloud once
[ ] Names, numbers, dates, links checked
[ ] Cut ~10% from the first draft

One-point paragraph

[Topic sentence: the claim, specific and testable.]
[Evidence: a number, an example, or a source.]
[Explanation: why the evidence supports the claim.]
[Consequence: what it means for the reader / what next.]
 
Example:
Onboarding loses 40% of sign-ups at email verification.
In September, 6,200 of 15,500 new accounts never clicked
the link. Most were on mobile, where the link opens a
different browser and loses the session. Letting users
verify with a six-digit code should recover about half.

BLUF status update

Subject: [Project] status: [on track / at risk / blocked]
         - [one-line headline]
 
BLUF: [One or two sentences: state, and what you need.]
 
Progress since [date]:
- [Outcome, not activity]
- [Outcome]
 
Risks / blockers:
- [Risk] - [impact] - [what we're doing / what we need]
 
Next: [what happens by when]
Ask: [specific request, owner, deadline] (or "none")

Explain-it-to-a-newcomer paragraph

[Term] is [plain one-line definition].
It matters because [consequence the reader cares about].
For example, [concrete instance with real names/numbers].
It is not [common confusion]; that is [the other thing].

References