Principles: George Orwell's 1946 essay "Politics and the English Language" begins with a diagnosis: "Most people who bother with the matter at all would admit that the English language is in a bad way, but it is generally assumed that we cannot by conscious effort do anything about it." Orwell disagreed.[1]

The essay outlines six rules for clear writing, the most quoted being: "If it is possible to cut a word out, always cut it out." Those rules remain influential nearly 80 years later, reproduced in style guides and taught in writing courses.

Later research supports several ideas compatible with Orwell's advice, including coherent structure, audience adaptation, and reducing unnecessary processing demands. It has not validated his six rules as a unified empirical framework, and some do not hold universally: the passive voice is genuinely useful when the object matters more than the actor, and cutting every removable word is an editorial principle rather than a tested law.[12]

What follows is a WhenNotesFly framework, drawing on discourse-comprehension research, cognitive-load theory, and plain-language practice. The organising idea is that clarity is less about vocabulary than about the fit between how the communicator has organised an idea and what the receiver can reconstruct from it.

What Clarity Means

Clarity is helping a specific audience build a sufficiently accurate and usable understanding for a particular purpose.

Clarity often requires simplification, but not simplification that changes the meaning. The useful distinction is between accurate simplification, which removes detail the audience does not need, and distorting simplification, which removes relationships or conditions the conclusion depends on. The goal is the simplest representation that preserves the relationships, conditions, and distinctions the audience actually needs.

A good popular explanation of quantum mechanics does reduce the formal complexity: the mathematics, the scope, much of the apparatus. What it preserves are the conceptual relationships that matter for the reader's purpose. Richard Feynman's public lectures are often praised for exactly this, using concrete examples and carefully built conceptual steps.

Clarity is a relationship between sender and receiver, not a property of a message alone. A message perfectly clear to one audience may be opaque to another that lacks the prerequisite knowledge, or may invite incorrect interpretations when a general reader fills gaps with wrong assumptions.

This has a practical consequence: "Is this clear?" is not answerable without asking clear to whom, in what context, with what prior knowledge, and for what purpose.

The WNF Five-Principle Framework

The five principles below are a WhenNotesFly synthesis of ideas from discourse comprehension, cognitive-load research, plain-language practice, and communication theory. They are an editorial model, not an established research taxonomy, and no single study establishes this exact five-part set.

PrincipleWhat It RequiresCommon ViolationWhy It Helps
1. Lead with purpose and main pointState what this is for and what it concludes, then elaborateBuilding to a conclusion revealed only at the endReaders can organize incoming detail once they know what it is for
2. Sequence prerequisite ideasEstablish what a concept depends on before using itUsing terms before defining themUnfamiliar terms otherwise get filled with wrong assumptions
3. Ground abstractions concretelyAnchor abstract claims with specific casesAbstract claims with no illustrationAbstractions without referents are memorable but hard to apply
4. Preserve important conditionsState the boundaries where the claim stops holdingUnconditioned claims that invite misapplicationReaders lacking domain knowledge cannot supply the conditions
5. Verify understandingDesign a way to check what was actually receivedOne-way delivery with no comprehension checkMeaning-level failures are invisible without feedback

1. Lead with purpose and main point

Receivers should not have to guess what a piece of communication is trying to accomplish or how its parts relate. In practice this means stating the point or requested action early, signalling transitions explicitly, providing navigation in longer documents, and relating the conclusion back to the opening question.

Delaying the organizing point can increase processing demands, particularly when the material is unfamiliar or delivered only once.[5] Readers of written text can reread, take notes, form provisional models, and lean on prior knowledge, so this is a matter of degree rather than an absolute limit.

This principle has real exceptions. For decision-oriented communication, stating the conclusion or requested action early usually helps. Evidence-first sequencing may be more appropriate in scientific reasoning, investigative journalism, legal argument, teaching where discovery is part of the point, narrative, and cases where stating the conclusion first would bias how the audience weighs the evidence.

2. Sequence prerequisite ideas

Order information so each element can be understood from what has already been established. This requires modelling what the receiver knows at each point.

The sequencing task is made harder by the curse of knowledge: people who know a subject well systematically underestimate the background their explanation assumes.[7] "Load distribution in redundant structures follows the stiffness of each load path" is not unclear in itself; it is unclear because it sits on prerequisites a non-engineer does not have.[13] We cover this effect in the curse of knowledge.

Two common cautions are less absolute than they sound. Examples do not always follow the principle: a concrete case first often helps an audience infer an abstraction, and example-first instruction can be more effective for some learners. Put examples where they best support understanding. Exceptions do not always follow the base case: establish the base case clearly, but surface any exception that materially changes safety, legality, or the main conclusion early enough to prevent misuse.

Wikipedia's Manual of Style illustrates the underlying idea: the lead section is required to introduce the article and summarise its most important contents, so a reader can get the main point without reading the full detail.[9]

3. Ground abstractions concretely

Clarity is relative to the receiver's existing knowledge, so build on reference points they demonstrably have: connect new concepts to familiar ones, use examples from domains the audience knows before domain-specific ones, and establish what an idea resembles before what makes it different.

Because the curse of knowledge impedes accurate modelling of what the audience knows, the practical move is to check more often than feels necessary rather than assume a concept landed before building on it.

4. Preserve important conditions

Include the conditions under which claims hold, not just the claims. Claims stated without boundaries are incomplete and get misapplied by receivers who lack the domain knowledge to supply the conditions themselves.

"This adhesive sets in 30 minutes" is incomplete if that timing only applies within a particular temperature and humidity range. A reader who bonds a joint in a cold workshop and loads it after half an hour has been misled by a technically accurate sentence.

Preserving conditions does not mean hedging everything. It means identifying the boundary conditions where a claim breaks down most significantly or most predictably, and stating those while omitting less consequential qualifications.

A practical editorial heuristic: would a reasonable reader who accepts this claim as stated apply it in a situation where it fails? What counts as reasonable varies, so treat this as a judgment aid rather than a test with a definite answer, and require more explicit boundaries as the consequences of misapplication grow.

5. Verify understanding

One strong test of clarity is whether the receiver can accurately restate or apply the model, rather than confirm that they followed it. A simple "does that make sense?" is weak evidence, because people may not recognise their own gaps or may hesitate to admit confusion.

Repeating words back is also weaker evidence than it appears, and questions may indicate engagement rather than successful transfer. The more informative checks ask the receiver to generate something:

  • apply the concept to a new case;
  • predict what the model implies;
  • produce a counterexample or identify a boundary;
  • find the error in a sample application;
  • explain it back in their own words rather than yours.

Relevance signalling belongs here too, as part of designing communication that can be checked. Marking what is load-bearing ("the central point is...") versus supplementary ("for completeness, note that...") helps for several reasons at once: scanning and search, task orientation, decision speed, navigation, and accessibility, as well as managing processing demands.

Without signalling, readers still allocate attention selectively, but according to assumptions that may not match the communicator's intended hierarchy.

What the Evidence Supports

Discourse coherence. Walter Kintsch and Teun van Dijk's 1978 paper in Psychological Review developed an influential model of how readers build coherent mental representations from propositions and larger discourse structures.[2] It is a theoretical and computational model rather than a single recall experiment, and its contribution here is conceptual: it supports treating clarity as a matter of organization and coherence rather than vocabulary alone.

Worked examples. John Sweller and Paul Cooper (1985) found that novice algebra students studying worked examples required less instructional time and afterwards solved structurally similar problems faster and with fewer errors than students given conventional problem-solving practice.[3] The advantage was less clear when test problems differed in structure, so this is not a general proof that showing your reasoning always transfers.

Worked-example effects have been studied across several procedural learning domains, mostly with novices, and later research on expertise reversal found that the same support can become redundant or even counterproductive for more experienced learners.[4]

Plain language. The U.S. federal plain-language programme and the Plain Writing Act of 2010 reflect a sustained government commitment to writing public documents in plain language. In 1998 the Securities and Exchange Commission adopted plain-English requirements for prospectus cover pages, summaries, and risk factors, so that information material to investors would be more understandable.[8]

These are documented policy commitments; we are not aware of published controlled experiments attaching specific comprehension percentages to them, and this article does not claim any.

Attention and what goes unnoticed. Simons and Chabris's 1999 selective-attention study, widely known as the invisible gorilla, is a behavioural experiment showing that observers absorbed in counting basketball passes often fail to notice an unexpected event in plain view.[6] By analogy, content whose relevance is not made apparent may be overlooked. This is an illustrative parallel rather than a neural account of how readers process documents.

Clarity in High-Stakes Contexts

Challenger. Before the Space Shuttle Challenger launch on January 28, 1986, Morton Thiokol engineers recommended against launching below 53°F, and the Rogers Commission documented their objections. It would be wrong to say they failed to state a conclusion: they did recommend not launching, and were overruled.

Edward Tufte later argued that the charts presented that night did not clearly display the relationship between temperature and O-ring damage. That analysis has itself been debated, with other scholars and participants disputing aspects of the reconstruction and arguing the available data were less conclusive than his account suggests.

The defensible reading is that presentation was one contributor within a wider failure involving management pressure, normalisation of prior anomalies, data uncertainty, and organizational authority. Clarity mattered; it was not the sole cause.

Checklists. The WHO Surgical Safety Checklist is a concrete example of communication designed for reliability rather than brevity. It confirms patient identity, procedure, and surgical site, prompts the team to state anticipated critical events, and requires spoken confirmation from named team members at defined pauses.[10]

Atul Gawande's The Checklist Manifesto is a practitioner account of this work rather than a controlled study, and the checklist is not an application of the framework above; it is an independently developed protocol that happens to make prerequisites and shared terminology explicit.[11]

When Clarity Is Resisted

Clarity is not always the goal, and it helps to recognise when something else is operating.

Ambiguity can be strategic. In negotiation, politics, and organizational strategy, vagueness sometimes serves a purpose: not revealing priorities, addressing constituencies with conflicting interests, avoiding commitment to measurable targets. These are plausible incentives rather than established universal explanations, but where they apply, diagnosing the problem as poor writing misreads the situation.

Specialized language does several jobs. Technical vocabulary can be genuinely necessary for precision, and disciplinary convention, intended specialist audience, and methodological requirements all shape how academic and professional writing reads. In some settings it can also function as a marker of group membership or status. Both can be true, and assuming the social motive across a whole field is unfair.

Clarity can expose weak thinking. Writing plainly forces reasoning into the open rather than letting abstraction gesture at it. Where the underlying thinking has gaps, achieving clarity means first doing harder analytical work, which is one honest reason it gets avoided.

Determining which elements carry meaning and which interfere is closely related to the signal versus noise problem, which deals with prioritising information for a specific decision.

Clarity and Trust

Investing in clarity can demonstrate respect for the receiver's time and needs. It is worth being careful with the inverse claim: unclear communication does not by itself establish the sender's motives. Complexity also results from limited editing time, genuine subject difficulty, legal constraints, uncertainty, inexperience, or writing for several audiences at once.

We can call the orientation that produces clarity communicative generosity, a WhenNotesFly term rather than an established construct: a genuine interest in whether the receiver understood, which leads you to find out and adjust. The principles are the tools; without the orientation they stay technique, and without the tools the orientation stays aspiration.

A Practical Checklist

  • What must this audience understand, decide, or do afterward?
  • Have I stated that up front, or is there a reason this audience needs the evidence first?
  • Which terms and models does my draft assume, and are they established before use?
  • Which abstractions still lack a concrete case?
  • Which conditions, if omitted, would let a reasonable reader misapply this?
  • What is load-bearing versus supplementary, and is that visible?
  • How will I check what was received, beyond asking whether it made sense?

Sources & Further Reading

  1. Orwell, G. "Politics and the English Language." Horizon, 1946. View source(The six rules discussed in the opening.)
  2. Kintsch, W. & van Dijk, T. A. "Toward a Model of Text Comprehension and Production." Psychological Review, 85(5), 363-394, 1978. DOI: 10.1037/0033-295X.85.5.363(Discourse coherence and macrostructure.)
  3. Sweller, J. & Cooper, G. A. "The Use of Worked Examples as a Substitute for Problem Solving in Learning Algebra." Cognition and Instruction, 2(1), 59-89, 1985. DOI: 10.1207/s1532690xci0201_3(Worked-example effect and its limits.)
  4. Kalyuga, S., Chandler, P., Tuovinen, J. & Sweller, J. "When Problem Solving Is Superior to Studying Worked Examples." Journal of Educational Psychology, 93(3), 579-588, 2001. DOI: 10.1037/0022-0663.93.3.579(Expertise reversal.)
  5. Sweller, J. "Cognitive Load Theory, Learning Difficulty, and Instructional Design." Learning and Instruction, 4(4), 295-312, 1994. DOI: 10.1016/0959-4752(94)90003-5(Processing demands in instruction.)
  6. Simons, D. J. & Chabris, C. F. "Gorillas in Our Midst: Sustained Inattentional Blindness for Dynamic Events." Perception, 28(9), 1059-1074, 1999. DOI: 10.1068/p281059(Inattentional blindness, used here as an analogy.)
  7. Nickerson, R. S. "How We Know - and Sometimes Misjudge - What Others Know: Imputing One's Own Knowledge to Others." Psychological Bulletin, 125(6), 737-759, 1999. DOI: 10.1037/0033-2909.125.6.737(Curse of knowledge.)
  8. U.S. Securities and Exchange Commission. A Plain English Handbook: How to Create Clear SEC Disclosure Documents, 1998. View source(The plain-English disclosure requirements.)
  9. Wikipedia. Manual of Style/Lead Section. View source(Lead-section summary convention.)
  10. World Health Organization. WHO Surgical Safety Checklist, 2009. View source(Checklist components described above.)
  11. Gawande, A. The Checklist Manifesto: How to Get Things Right. Metropolitan Books, 2010. View source(Practitioner account of checklist adoption.)
  12. Williams, J. M. & Bizup, J. Style: Lessons in Clarity and Grace, 12th ed. Pearson, 2017. (Sentence-level clarity craft.)
  13. Pinker, S. The Sense of Style. Viking, 2014. (Curse of knowledge in writing practice.)

Frequently Asked Questions

What are the five principles of clear communication?

In the WhenNotesFly framework used in this article: lead with purpose and main point, sequence prerequisite ideas, ground abstractions concretely, preserve important conditions, and verify understanding. This is an editorial synthesis, not an established research taxonomy, and no single study establishes this exact five-part set. Each principle has situations where it does not apply cleanly, covered alongside the principle itself.

Is clarity the same as simplicity?

Not quite. Clarity often requires simplification, but not simplification that changes the meaning. The useful distinction is between accurate simplification, which removes detail the audience does not need, and distorting simplification, which removes relationships or conditions the conclusion depends on. The target is the simplest representation that keeps the distinctions the audience needs.

Should I always state my conclusion first?

For decision-oriented communication, stating the conclusion or requested action early usually helps, because readers can organize incoming detail once they know what it is for. It is not universal: evidence-first sequencing can suit scientific reasoning, investigative journalism, legal argument, teaching where discovery is part of the point, narrative writing, and cases where stating the conclusion first would bias how the audience weighs the evidence.

Should examples come before or after the principle?

Either can work; the common advice to always state the principle first is too rigid. A concrete case presented first often helps an audience infer an abstraction, and example-first instruction can suit some learners and subjects. The same applies to exceptions: establish the base case clearly, but surface any exception that materially changes safety, legality, or the main conclusion early enough to prevent misuse.

How much qualification should a claim carry?

Enough to prevent predictable misapplication, without hedging that buries the point. Identify the boundary conditions where the claim breaks down most significantly, state those, and omit less consequential ones. Ask whether a reasonable reader who accepts the claim as stated would apply it in a situation where it fails. Require more explicit boundaries as the consequences of getting it wrong grow.

How can I tell whether I was actually understood?

Not by asking whether it made sense. That is weak evidence, because people may not recognise their own gaps or may hesitate to admit confusion, and repeating words back can happen without understanding. The more informative checks ask the receiver to generate something: apply the concept to a new case, predict what the model implies, produce a counterexample, find the error in a sample application, or explain it back in their own words rather than yours.

Contributors