For years, I wrote variations of this exact sentence: "Consistent content production builds trust in your brand." A true sentence. So true that nobody could possibly object to it. And for that exact reason—nobody stopped to read it.
We didn't realize this through gut feeling, but through a single side-by-side comparison. We published two versions of the same article. In one, the core anchor paragraph remained abstract: "consistent content builds trust." In the other, we replaced that exact claim with a single scene: "The client walked into the meeting holding a printed screenshot of our blog post from three months ago." On the scroll map, the difference was immediately visible: in the abstract version, readers didn't slow down their scrolling speed on that paragraph; in the scene version, a distinct pause band appeared. The completion rate for the scene version was also measurably higher.
A single data point. A small sample size. But once you see it, it's a pattern you can no longer unsee.
What the abstraction tax is
When a reader encounters a sentence structured like "X is important," they perform an instant cognitive classification: I already know this. And they don't read what they think they already know—they scan. Eye-tracking research by Nielsen Norman Group shows that web readers scan text in an F-pattern rather than reading line by line, focusing their attention heavily on the left edge of text blocks and the first few words of lines (originally published in 2006, updated in 2017). If the first few words of a paragraph are generic and predictable, the reader's subconscious decision to continue reading resolves negatively.
Underneath this lies an established cognitive foundation. Allan Paivio's dual coding theory posits that concrete words are encoded both verbally and visually, whereas abstract words remain primarily verbal. As a result, concrete language demonstrates a consistent recall advantage in memory experiments replicated since the 1960s. In other words, the assertion that "readers process concrete language better" isn't workshop folklore—it is a half-century-old empirical finding known as the concreteness effect.
And the effect extends beyond single words. In a 1993 study by Mark Sadoski and colleagues on expository text, paragraph concreteness showed a strong positive correlation with comprehensibility and recall; concreteness emerged as the single strongest predictor of recall. Note: the study was conducted with English texts, so exact numerical ratios cannot be directly transplanted into other languages. But the direction is clear.
A further note on intellectual honesty: to my knowledge, there is no single published study directly proving that "a reader skips a paragraph in real time the instant they see an abstract sentence." What we are presenting is a synthesized inference combining NN/g's scanning patterns with memory literature, alongside our own small internal measurement. If I don't disclose that this is an inference, I would be paying the overclaiming tax myself.
Anatomy of the measurement — and its limits
What did we count? Three things: scroll deceleration aligned with the paragraph, selected text copying, and article-level completion rate. We used an operational definition for "abstract claim sentence" because relying on intuition doesn't work: a generic subject ("people," "companies," "good content") + an evaluative predicate ("is important," "is necessary," "is critical," "increases") + zero observable detail. If the sentence answered none of the questions "who, did what, what was seen," we classified it as an abstract claim.
Now, the limitation: scroll and attention-map metrics measure "dwell time on screen," not actual "reading." As documentation from Microsoft Clarity and Hotjar clearly distinguishes, a scroll map shows how far down the page a reader navigated; it does not prove they stopped and read. Readers who leave tabs open or scroll rapidly back and forth contaminate the data. Therefore, rather than relying solely on paragraph dwell time as a single honest metric, we measured the completion rate delta between the two versions. The pause band told us "something is happening here"; the completion delta told us "they kept reading." Together they are meaningful; alone, both are incomplete.
Before / after
Before: "Consistent, high-quality content production is one of the most critical factors in building customer trust over the long term."
After: "The client walked into the meeting holding a printed screenshot of an article we published three months ago—with handwritten notes in the margins."
What changed at the sentence level? The subject became individualized: not "content production," but a specific client. The verb became observable: you cannot film "increases" with a camera; you can film "walked in holding a printout." Time and place entered the frame: a meeting, three months ago. The scene test is simple: can a camera film the sentence? If there is a person + a single action + a sensory or measurable detail, the answer is yes.
And crucially: the scene was not added alongside the abstract sentence. It took its place. The underlying claim remains—"content builds trust"—but it is no longer stated; it is shown.
The counter-example: when we crammed an example into every sentence
Seeing these initial results, we made an admitted mistake: for several weeks, we shoved a scene into virtually every paragraph. Mini-anecdotes in transition sentences, second examples attached to sentences that already contained numbers and names. Our articles expanded by 30–40% in length, and completion rates dropped. A second example attached to an already concrete sentence was processed by readers as "redundancy," not "proof."
Cognitive literature had partly anticipated this, and we should have reviewed it sooner: Ruth Garner and colleagues' 1989 study on "seductive details" demonstrated that adding interesting but non-essential concrete details can impair recall of the main thesis. One caveat: that study focused on "interesting but irrelevant details," which is not identical to our situation of adding "relevant but unnecessary second examples." This specific part of our bloat hypothesis rests more on our internal measurements and editorial experience than on formal experimental literature. Yet the mechanism is similar: attention is a finite budget, and every scene spent in the wrong place steals bandwidth from the core thesis.
Condition map: where scenes are required vs. where they are dead weight
A scene is mandatory under this condition: when the sentence carries the core thesis of the piece and invites the reader to ask, "Really?" A contestable generalization deserves empirical form.
A scene is dead weight under these three conditions: (1) transition and navigational sentences—adding an example to sentences that merely direct reading traffic is like writing a narrative on a road sign; (2) already concrete sentences—adding a second example to a sentence that already has numbers, names, or observable actions creates pure redundancy; (3) uncontroversial premises—where the reader already agrees, providing proof is wasteful.
This distinction also sets this microtactic apart from simple adjective/verb choice or conjunction edits, which are intra-sentence interventions. This adjustment operates at the level of claim-and-evidence structure: first, you locate which sentence carries the weight of the text, and then you change that sentence's evidentiary form. A flawlessly written scene constructed with great words yields zero impact if placed beside the wrong sentence.
Set up your own test
A single data point is not universal law; this was a small sample, one language, and a specific reader profile. In Made to Stick (2007), Chip Heath and Dan Heath reference a Stanford classroom exercise where only 5% of listeners recalled an individual statistic while 63% recalled stories—though that was a classroom demonstration rather than a peer-reviewed controlled trial. It indicates direction, not guaranteed ratios. The right approach is to test it in your own writing.
A minimal test setup: two versions of the same text. In V1, the anchor claim remains abstract; in V2, that same sentence is replaced with a single concrete scene. For measurement, either have 5–10 readers review it and ask an open-ended recall question ("What did this paragraph say?"), or compare live completion rates across both versions. Add a V3—a longer version where a second example is appended to an already concrete sentence—so you can test the bloat hypothesis in your own material. One variable, two (ideally three) versions; the rest is honest curiosity.
One non-accusatory final note: we don't write abstractly out of laziness. This is the exact mechanism Steven Pinker describes in The Sense of Style (2014) as the "curse of knowledge"—the expert already possesses concrete examples in their mind, making abstraction feel effortless. In the words of the Heath brothers, abstraction is the luxury of the expert. Those examples do not exist in the reader's mind; you have to put the scene onto the page.
The rule to take back to your workshop
Find the most ambitious abstract sentence in your draft—generic subject, an "is important / must / critical" predicate, and zero observable detail. Do not add a second sentence to it; replace it with a single concrete scene. You do not append examples; you substitute the abstract.