Writing for a general audience

The people who understand a subject best are frequently worst at explaining it, for a reason that has a name.

The curse of knowledge

The mechanism.

Once you know something, it becomes extremely difficult to imagine not knowing it.

Which means experts systematically overestimate what their audience knows, use terms that are transparent to them and opaque to others, and skip steps that feel too obvious to state.

Experimental work on this has found it robust and largely resistant to simply being told about it.

Which means the corrective must be structural rather than a matter of intention.

The structural correctives

What actually works.

Testing on an actual reader from the intended audience, and asking where they got lost rather than whether it was clear.

People will say something was clear when it was not, out of politeness or because they did not realise what they missed.

Asking them to explain it back, which reveals what was actually transmitted.

Listing your assumed knowledge explicitly and checking each item.

Reading it aloud to someone, which surfaces the places where you find yourself adding explanation — those are the gaps.

And writing the explanation you needed when you first learned it, which most people can still remember.

Jargon

The most visible symptom.

Technical terms exist because they are precise, which is a real function.

They become a problem when used with an audience that does not share them, and when used to signal membership rather than to communicate.

Practical approach: use the plain equivalent where one exists; define the term at first use if it is needed later; and remove it entirely if it is not.

The test: could a competent person outside your field read this?

Explaining something unfamiliar

The sequence that works.

Start with why it matters to the reader, since motivation precedes attention.

Connect it to something they already know.

Give a concrete example before the general principle, since examples are easier to hold than abstractions.

Build in steps, each of which depends only on what came before.

Name the thing after describing it rather than before, so the name attaches to something.

And check understanding before building further, in interactive contexts.

Analogy

Which is powerful and requires care.

A good analogy maps the unfamiliar onto the familiar and lets the reader reason about it.

Its limitation: every analogy breaks down somewhere, and readers extend it beyond where it holds.

Which means stating where it stops applying: "this is like X, except that…"

And choosing analogies from domains the audience actually knows, which requires knowing who they are.

Numbers

Which are frequently meaningless as presented.

Large numbers convey nothing without comparison — a figure in millions means little until it is expressed as a proportion, a per-person amount, or a comparison to something known.

Percentages need a base: a doubling of a small risk is still a small risk.

Round numbers are remembered and precise ones are not, which means precision beyond what matters is a cost.

And a single well-chosen comparison does more than a table.

Uncertainty

Which experts frequently either overstate or omit.

General audiences can handle uncertainty when it is stated plainly: this is well established, this is likely, this is contested, this is unknown.

What confuses is hedging that leaves the reader unable to tell how confident to be.

Which means distinguishing the levels explicitly is more useful than qualifying everything equally.

And stating what would change the answer, which is more informative than a confidence level.

Respecting the reader

The tone that works.

Simplifying language is not the same as simplifying content, and general audiences can follow complex arguments in plain words.

What loses them is unexplained terminology, missing steps and abstraction — not difficulty.

Which means the objective is accessibility rather than dilution, and writing that is condescending is as ineffective as writing that is impenetrable.

The practical test

Before publishing.

Give it to one person outside your field.

Ask them to mark where they got confused or lost interest.

Do not explain what you meant — the confusion is the data.

Fix those places.

And repeat with a different reader if it matters, since one reader's gaps are not everyone's.