The Principles of Clear Prose

Learning outcomes

You post a status update to your team channel: “It should be noted that the implementation of the new caching layer has resulted in a significant reduction in the latency that is experienced by users.” Your reader gets to the end, pauses, and reads it again. Somewhere in that sentence is good news, a faster product, but they had to dig for it. A teammate would have written “The new cache cut user latency in half,” and nobody would have read it twice. Both sentences are correct. Only one of them lands on the first read, and that difference is not luck. It is a small set of principles you can learn and apply on purpose.

After studying this page, you can:

• State the single goal that governs every other rule of clear prose: the reader understands on the first read.
• Rewrite a heavy, noun-stuffed sentence by making the characters the subjects and their actions the verbs, undoing nominalization.
• Order a sentence and a paragraph so each one starts with familiar information and ends with the new, so the whole chains smoothly.
• Cut three kinds of deadwood (redundant pairs, empty meta-discourse, and expletive openings) without losing meaning.
• Recognize the curse of knowledge in your own draft and bridge the gap your reader cannot.
• Choose the active or passive voice deliberately, and run a fast write-then-revise loop on any workplace document.

Before we dive in

Every piece of writing advice you have ever heard is downstream of one fact: reading takes effort, and your reader has a finite supply of it. A sentence is clear when it spends that effort only on the idea, and unclear when it makes the reader spend effort decoding the sentence itself before they can even reach the idea. The status update above is not wrong. It is expensive. Every extra word, every buried verb, every backwards order charges the reader a small tax, and by the end they have paid enough to want to re-read.

So the goal of clear prose is narrow and testable: the reader should understand your meaning on the first pass, without going back. Not “the writing sounds smart.” Not “every rule is obeyed.” Just this: did it land the first time? Everything in this page is a way to answer yes more often. The principles come mainly from two writers who studied clarity closely, Joseph Williams in Style and Steven Pinker in The Sense of Style, and they agree on the core: clear prose matches the shape of the sentence to the shape of the story it tells.

Here is the move that makes the rest make sense. A sentence tells a little story, and a story has characters who do things. When the grammar lines up with the story, when the characters are the grammatical subjects and their actions are the verbs, the reader follows effortlessly, because the sentence is built the way they already think. When the grammar fights the story, when the action is hidden inside a noun and the real character is missing or shoved aside, the reader has to reconstruct who did what. That reconstruction is the effort you feel as “unclear.” Almost every principle below is a different way to stop making the reader do it.

A warning before we start. None of these are rules in the sense that breaking them is an error. They are defaults. A good writer breaks each one on purpose when the situation calls for it, and the last skill you will learn here is knowing when. We will treat the passive voice, the long sentence, and the abstract noun not as villains but as tools you reach for deliberately, not by accident.

The one test that judges everything

Before the seven principles, fix the standard they all serve. The principles are not seven independent rules to memorize; they are seven symptoms of one underlying problem, and one test detects all of them. Read your sentence and ask: did my reader understand this on the first pass, or did something make them slow down, back up, or re-read? Every principle below is a named cause of that slowdown, and every fix removes one cause.

Read the diagram as a loop you run on every sentence you revise. The top question is the only thing that ultimately matters; the seven branches are just the common reasons the answer comes back “no.” You will rarely have to check all seven by name, because with practice you hear the slowdown and jump straight to its cause. The sections that follow take each branch in turn, show it failing on a real workplace sentence, and hand you the fix.

Breaking it down

1. Match grammar to the story: characters and actions

Start with the principle that does the most work, because the other six lean on it. Williams’s central claim is simple: readers feel a sentence is clear when its main characters are the subjects and their important actions are the verbs. A sentence is a story; the subject slot is for who is acting, and the verb slot is for what they do. Honor that, and the reader decodes nothing.

The most common way to violate it is nominalization: turning a verb into a noun. “Decide” becomes “decision,” “implement” becomes “implementation,” “reduce” becomes “reduction.” Each of these is a perfectly good word, but when you build a sentence out of them, you freeze the actions into things and then need a weak helper verb (“make,” “perform,” “result in,” “lead to”) to limp between them. The real action vanishes from the verb slot, and the real character often vanishes too.

Watch it happen. “The team made a decision to delay the launch” buries the action “decide” inside the noun “decision” and props it up with the empty verb “made.” Free the verb and the character steps forward: “The team decided to delay the launch.” Three words shorter, and the team is now visibly doing something. The fix is always the same: find the noun that hides an action, turn it back into a verb, and make whoever is acting the subject. (Nominalization is a derivation pattern, a noun built from a verb by suffixes like -tion and -ment; the machinery is covered in word families and derivation.)

Notice that the first two rows shed the most weight, because nominalization is the heaviest tax of all. Each revision asks one question of the original, “who did what?”, and then answers it with a subject and a verb. Hold that question in your head and you have the single most useful revision habit in professional writing.

2. Cohesion: old before new

A sentence can have its characters and actions in the right slots and still read badly in a paragraph, because clarity is not only about single sentences; it is about how they connect. Williams’s second principle governs that connection: begin each sentence with information the reader already has, and end it with the new information you are adding. Old before new. Familiar first, then the payload.

The reason is mechanical. The start of a sentence is where the reader looks for the thread, the link back to what they just read. If you open with something brand new, the thread breaks and they feel a small lurch. If you open with the familiar, the new sentence clicks onto the previous one, and a paragraph of sentences chains into a smooth line of thought. This is also why the end of the sentence matters: English naturally stresses the final words, so the new information you put there lands with emphasis.

Here is a paragraph that ignores the principle, then one that follows it. Both contain identical facts.

The AFTER version is not shorter, and no word is fancier. It simply orders each sentence so its first words echo the previous sentence’s last words, a chain of old-to-new hand-offs. Read both aloud and the second one flows while the first one stutters; that flow is cohesion, and it is mostly a matter of order, not vocabulary. The rhythm this creates is a subject of its own in sentence rhythm in writing.

3. Concision: cut the deadwood

The third principle is the cheapest to apply and the easiest to feel: cut every word that does not earn its place. Concision is not about writing short for its own sake; it is about removing words the reader has to process for no gain. Deadwood comes in three recognizable forms, and once you can name them you will see them everywhere in your own drafts.

The first is the redundant pair, where two words say what one word already covers. “Each and every” is just “every.” “Full and complete” is “complete.” “First and foremost” is “first.” The second word feels like emphasis but adds only length. The second is empty meta-discourse, phrases that talk about the writing instead of saying the thing: “it should be noted that,” “it is important to mention that,” “as a matter of fact.” These are a runway with no plane on it; the reader sits through them waiting for the real sentence. The third is the expletive opening, the hollow “there is,” “there are,” and “it is … that” that push the real subject deep into the sentence. “There is a function that validates the token” is “A function validates the token,” with the real subject restored to the front.

The discipline is to read each sentence and ask of every phrase: if I delete this, do I lose meaning? If not, it is deadwood. This is closely related to the wordiness and meta-discourse faults catalogued in correct but awkward; there the lens is sounding native, here it is reading clearly, but the cuts are the same. The courage to delete is the whole skill, because deadwood always feels like it is doing something until you remove it and find the sentence stronger.

4. The curse of knowledge

The fourth principle is the hardest to apply because it is the hardest to see in yourself. Pinker argues that the single biggest cause of unclear writing is not bad grammar or laziness; it is the curse of knowledge. You know your subject. You know what the acronym stands for, why the workaround exists, what the reader needs to have read first. And precisely because you know it, you forget that your reader does not, so you leave out the bridge they needed and write past them.

The curse is why an expert’s explanation so often feels both correct and useless to a beginner: every word is accurate, but the connective tissue, the context that would let an outsider follow, lives only in the writer’s head. It shows up as unexplained jargon (“just bump the TTL”), as missing steps (“then deploy it” without saying how), and as references to things only you can see (“like we discussed” in a doc read by hundreds). None of these are errors. They are gaps, and the writer cannot feel them because their own knowledge silently fills each one.

The practical defense is to assume less shared context than feels natural. When you write a term of art, ask whether a competent reader from the next team over would know it; if not, gloss it in a clause. When you write “just” or “simply,” treat it as a warning sign that you may be skipping a step that is only easy because you have done it before. The curse never fully lifts, which is why even strong writers rely on a reader to catch what they cannot.

5. Concrete over abstract

The fifth principle gives the reader something to picture. Abstract words name categories and concepts; concrete words name things you could point to, count, or watch happen. “We improved operational efficiency” floats; “We cut the deploy from forty minutes to four” lands, because the reader can see it. Pinker’s image for good prose is a clear window onto the world: the writer points at something real and the reader looks through the glass at it. Abstraction frosts the glass.

Concreteness does not mean banning all abstract words; some ideas are genuinely abstract and need abstract names. It means preferring the specific when you have the choice, and anchoring an abstraction to an example the moment you introduce one. “Performance regressed” is abstract; follow it with “the search endpoint went from 200 milliseconds to 2 seconds” and the abstraction now has a picture attached. The pattern is name-then-show: state the general point, then give the concrete case that lets the reader feel it. This is the same concrete-before-abstract instinct that governs good explanation everywhere, and it pairs naturally with the active, character-driven sentence from principle one, because a real character doing a real action is already concrete.

6. The active voice as default, the passive on purpose

The sixth principle is the most often mangled into a superstition, so state it carefully. The active voice (“the contractor introduced the bug”) names the actor as the subject and is the right default, because it matches the character-and-action shape from principle one. The passive voice (“the bug was introduced”) demotes or hides the actor and is therefore the exception. But the passive is not an error, and the common advice to “never use the passive” is wrong. The passive is a precise tool with two legitimate jobs.

The first job is keeping the topic in the subject slot for cohesion. If a paragraph is about the bug, “the bug was introduced by a contractor” rightly keeps “the bug” up front, serving the old-before-new principle even though it is passive. The second job is hiding an actor who is irrelevant or unknown: “the server was rebooted at 3 a.m.” is better than naming whichever on-call engineer happened to do it, because the actor does not matter. The fault is not the passive itself; it is the passive used by accident, which hides an actor you should have named and drains the action out of the sentence.

7. One idea per paragraph, point near the top

The final principle scales the others up from the sentence to the paragraph. A paragraph should carry one main idea, and the sentence that states it should sit near the top, not be saved for the end like a punchline. Readers skim; they read the first sentence of a paragraph closely and the rest lightly, so a point buried in the last line is a point many readers never reach. Leading with the point is not dumbing down; it is respecting how people actually read at work.

This is why the bloated status update from the start of the page failed twice over. It buried its one idea, the cache made things faster, at the end of a long sentence, behind a wall of nominalizations and an expletive opening. The clear version states the point first (“the new cache cut user latency in half”) and lets any detail follow. The same shape works for a paragraph: topic sentence first, support after. When you find yourself building to a conclusion, try moving the conclusion to the front and watch the paragraph get easier to read. The art of putting the point first in professional messages is developed further in professional email.

Mental Model: write fast, then revise hard

Here is the reframe that ties the seven principles together and corrects the most common misconception about them. The wrong model is that clear writing means writing clearly the first time, applying all seven principles as the words come out. Under that model, every sentence is a small exam you must pass while drafting, and the result is the worst of both worlds: writing slows to a crawl and still comes out stiff, because you are editing and composing at once and doing neither well.

The better model splits the work in two. Drafting and revising are different jobs that use different parts of the mind, and trying to do them simultaneously cripples both. So write the first draft fast and badly. Let it be wordy, let the verbs hide in nouns, let the point sit at the end; the goal of the draft is only to get the raw thought onto the page where you can see it. Then revise, and revise as a reader, not a writer: now you apply the principles, free the verbs, reorder old-to-new, cut the deadwood, hunt the curse of knowledge, move the point to the top. The principles are revision tools, not composition tools.

This is also why the principles do not make writing robotic. You are not following a checklist as you compose, which would flatten your voice; you are writing freely and then sharpening. The freedom lives in the first pass, the clarity in the second. A writer who has internalized the seven principles still drafts messily; they just revise faster, because they hear the slowdowns and know the fixes by name.

A worked revision, end to end

To see the whole page work at once, take one bloated paragraph and revise it the way the mental model prescribes: read it as a stranger, find each slowdown, name its cause, apply its fix. The original is a status update of the kind that floods every team channel.

The revision keeps every fact and loses forty percent of the words, and it lands on the first read. Walk back through it and you will see all seven principles at work in a few lines: buried verbs freed, the point moved to the front, the accidental passives made active, the expletive and the meta-discourse cut, the vague “significant” made concrete. This is what the reviser’s loop produces in practice, and it is a skill that compounds: the more bloated paragraphs you revise on purpose, the fewer you draft by accident.

Common mistakes

The first mistake is the heavy-noun style itself, mistaking it for sophistication. Many writers believe that stacking abstract nouns (“the optimization of the utilization of resources”) sounds more professional than plain verbs, so they reach for it deliberately. It reads as the opposite: slow, evasive, and hard to follow. The most respected technical writers use the plainest verbs, because they trust the idea to carry itself. When a sentence feels impressively dense, suspect a nominalization and free the verb.

The second mistake is overcorrecting on the passive voice into a phobia. Having heard “avoid the passive,” some writers contort every sentence into the active even where the passive was right, naming an irrelevant actor (“an engineer rebooted the server”) when “the server was rebooted” was cleaner, or breaking cohesion to avoid a passive that was keeping the topic up front. The rule is not “never passive”; it is “active by default, passive on purpose.” Know why you chose each one.

The third mistake is burying the point at the end out of a sense of building toward it. In an essay a delayed reveal can work; in a work email, a doc, or a status update, it fails, because the reader skims the top and may never reach the bottom. If your most important sentence is the last one in the paragraph, it is probably in the wrong place. Move it up and let the support follow.

The fourth mistake is the curse of knowledge defended as concision. A writer cuts context to be brief and tells themselves they are being clear, when really they have removed the bridge the reader needed. Concision means cutting words that add nothing, not cutting the context a reader requires. The two feel similar from inside your own head, because your knowledge fills the gap either way; the only reliable test is a reader who does not share your context.

The fifth mistake is hedging everything. Anxious writers wrap every claim in “it seems that,” “perhaps,” “to some extent,” and “in my opinion,” until the reader cannot tell what the writer actually believes. A little hedging marks genuine uncertainty and is honest; blanket hedging is just noise that drains the writing of force. State what you know plainly, hedge only what you are actually unsure of, and the few hedges that remain will carry real meaning.

Mastery Questions