Plain language isn't dumbing down — it's harder than jargon
Jargon is what you reach for when you haven't finished understanding something. Writing plainly is the proof that you have. A look at why clear writing is the difficult version.
There's a quiet assumption that plain language is the easy, lesser version of "real" writing — that experts speak in jargon because the ideas are genuinely too sophisticated for everyday words, and that simplifying them means losing something essential.
It's almost exactly backwards. In most cases, jargon is the easy option and plain language is the hard one. Jargon is what you reach for when you haven't finished understanding something well enough to say it simply. Clear writing is the receipt that proves you did.
Jargon is often a hiding place
Watch what jargon actually does in a sentence. A lot of the time, it lets the writer gesture at an idea without committing to it. Consider:
"We need to leverage our core competencies to drive synergistic value across the organization."
Strip it down and ask what it's actually claiming, and you find… almost nothing. "Do more of what we're good at, in ways that help different teams at once." Even that is generous. The original sentence is comfortable precisely because it never has to be specific enough to be wrong.
This happens in serious fields too, not just corporate decks. In medicine, finance, law, and academia, a wall of terminology can signal real precision — or it can paper over a writer who hasn't reduced the idea to its load-bearing core. The reader usually can't tell which from the outside, and that ambiguity is the problem.
A good stress test: if you can't say it plainly, there's a decent chance you don't yet understand it plainly. The jargon was holding the spot where the understanding should be.
Plainness forces you to actually decide
To write the sentence above plainly, you have to make decisions the jargon let you dodge. Which competencies? Good at, according to whom? Helps different teams to do what, specifically? Plain language is hard because it closes the exits. Every vague word is a choice you now have to make.
This is why translating something into plain language is one of the best ways to learn it. The Feynman technique — explain it as if to a smart twelve-year-old — works not because twelve-year-olds are the target audience, but because the act of removing jargon exposes every gap in your own understanding. You discover the parts you were only pretending to know the moment you try to say them in ordinary words. The same test makes summaries useful: our plain-English summary of Atomic Habits has to preserve the mechanism behind the advice, not merely swap long words for short ones.
So when a book explains a hard idea in plain language and it still feels rigorous, that's not a downgrade. That's someone having done the difficult work of understanding it completely enough to hand it to you clean.
Plain ≠ simplistic
Let's be precise, because there's a real failure mode here. Plain language is not the same as oversimplification, and it's not baby talk. The goal isn't to remove nuance; it's to remove friction that isn't carrying nuance.
The distinction:
- Jargon that carries meaning stays. "Inflation," "antibody," "compound interest" — these are precise terms that would take a paragraph to unpack, and unpacking them every time would be its own kind of unclear. Plain writing keeps the load-bearing vocabulary and explains it once.
- Jargon that carries status goes. "Utilize" instead of "use." "Facilitate" instead of "help." "Idiosyncratic volatility" when "the risk specific to one company" is what you meant. These words don't add precision; they add distance.
Good plain writing is the result of telling those two apart, word by word — which is slow, judgment-heavy work. The easy thing is to keep all the terminology and let the reader sort it out. The hard thing is to do the sorting for them.
A before and after
Before: "Asset allocation across non-correlated instruments mitigates idiosyncratic downside exposure."
After: "Spreading your money across things that don't all rise and fall together means one bad bet can't sink you."
The second version is longer, and it took more effort to write. It also can't hide. If it's wrong, you can tell. That accountability is the point — and it's exactly what jargon is so often used to avoid.
Clear writing is generous in a specific way: it moves the work from the reader back to the writer, where it belongs.
A plain-language edit you can run tomorrow
Take one important paragraph, name its single job, then rebuild it around a concrete claim. Hunting for shorter synonyms only produces tidier jargon.
Suppose a team writes this:
"We will operationalize a cross-functional prioritization framework to optimize high-impact initiatives."
Ask what the reader should know or do. The honest answer might be: "On Monday, the product and support leads will rank open projects by customer impact, then pause the bottom three." Now the sentence has owners, a time, an action, and a consequence.
Run the same edit in four passes:
- Circle the claim. What is true, or what should someone do? If neither is clear, the paragraph may not have earned its place.
- Underline actors and actions. Replace "implementation will occur" with who will do what. Missing actors often hide unmade decisions.
- Challenge abstract nouns. Ask what "alignment," "value," or "optimization" would look like. Keep a word only if the audience shares its meaning.
- Check for lost truth. Restore any condition, exception, or technical term that changes the reader's decision.
Give the result to someone who was not in the meeting and ask what happens next. If their answer differs from yours, the paragraph is not finished. This resembles using the 80/20 rule in real decisions: find the small part doing the actual work.
Where plain language fails
Plain language fails when a rewrite removes a distinction the reader needs to make a safe or accurate decision. Clarity is not the same as making every idea sound familiar.
A doctor should not replace a precise diagnosis with "a heart problem" if the condition changes treatment. A contract should not turn a defined obligation into a phrase that can be read three ways. Experts writing for experts may also use shared vocabulary; defining every established term can bury the argument.
A clean sentence can also make uncertainty sound settled. If evidence is limited, the plain version still needs "may," "usually," or "we do not know yet." Those words carry truth.
The rule is make the meaning easy to recover without making it smaller. That may require a technical term, a longer sentence, or an honest admission that the answer depends on facts you lack.
Why we're so stubborn about this
Every PlainReads book runs through the same discipline: keep the words that carry meaning, cut the ones that carry only status, and refuse to let a sentence stay vague just because vagueness is comfortable to write. It's slower to make a book this way. It's the entire reason the books are worth reading.
Because the promise we're actually making isn't "shorter." It's that when you finish, you'll be able to explain the thing to someone else — plainly, in your own words — which is the only real test of whether you understood it at all. Jargon can fake the feeling of knowing. Plain language is what's left when you actually do. That is the bar we hold ourselves to in Do Only 3 Things a Day: if a sentence in it can't survive being said out loud to a tired person, it doesn't ship.
The same standard applies to advice about follow-through. A useful guide to staying consistent when motivation runs out must tell you what to do on the low-energy day, not hide behind "maintain disciplined execution." If the reader cannot use the sentence, polish is beside the point.
Frequently asked questions
Is plain language the same as dumbing down?
No, plain language is not the same as dumbing down. Dumbing down removes ideas or qualifications; plain language keeps them and removes needless difficulty. A good rewrite preserves the meaning that affects a decision.
How do you simplify technical writing without losing accuracy?
Keep every detail that could change the reader's conclusion, action, or confidence. Define necessary terms once and test the rewrite against the source. If an exception matters, state it plainly.
Why do experts use jargon when simple words would work?
Experts often use jargon because it is efficient inside a group that shares its definitions. It becomes a problem when the audience does not, or when terminology helps the writer avoid a concrete claim. Ask whether the term compresses meaning or merely signals membership.
What is a quick way to check whether writing is clear?
Ask a reader to explain what the passage says and what, if anything, happens next. If they cannot identify the claim, actor, action, or important limit, revise those parts first. Reading aloud also exposes long sentences and abstract phrases, but comprehension is the real test.