Yükleniyor...
I wrote the sentence "quality content matters" hundreds of times—and it was so uncontestably true that it told nobody anything.
"Quality content matters" is a sentence I have written hundreds of times. Every single time, I felt safe, because the statement was true. Nobody was going to show up and argue, "No, low-quality content matters." That was precisely the problem: the sentence was so undeniably true that it told nobody anything.
It took me years to realize this. And when the realization hit, it didn't come from a flash of theory, but from sheer embarrassment: three months after drafting an opening paragraph, I reread it and could not identify which article it belonged to. It began: "In today's digital world, consistency plays a critical role." That sentence could have been mine, my competitor's, or a bank's corporate blog. It belonged to no one, really—because it made no actual claim.
The underlying mechanism is not a matter of taste; it is a matter of memory. One of cognitive psychology's most robust findings is the concreteness effect: concrete words and sentences are remembered significantly better than their abstract counterparts. Allan Paivio's dual coding theory, the standard explanation for this finding since 1971, posits that concrete language is coded across both verbal and visual-imagistic channels, whereas abstract language stays confined to a single channel. A sentence detailing "who did what, and what happened" automatically stages a scene in the reader's mind. The "X is important" formula builds no scene—it can't, because nobody is in it.
On the web, this reality is even more unforgiving. According to Jakob Nielsen's classic 2008 analysis for Nielsen Norman Group, users read roughly 20 to 28 percent of the text on an average page. Readers don't read; they scan. While scanning, they look for something to latch onto. An abstract generalization gets skipped in a scan because the eye finds no friction to catch on. A concrete scene stops the scroll.
In other words, the sentence "quality content matters" doesn't fail because it's false. It fails because it is too general to dispute. Readers don't remember sentences they can't push back against; they glide right over them.
Before, as originally written for a client presentation:
"Content quality is a decisive factor in reader retention."
After, with the exact same paragraph deleted and rewritten:
"The client's team had spent 40 minutes on that blog post. We opened the analytics dashboard together: the average reading time was 8 seconds. The article wasn't bad—its opening line was just identical to the first sentence of the other 200 articles on the site."
Nobody remembered the first version. Someone quoted the second version back to me while explaining it to their own team. That was the first time a paragraph I wrote came back to me. In Made to Stick (2007), Chip Heath and Dan Heath explain this through the Concreteness principle: abstract corporate language is a symptom of an expert's curse of knowledge. The expert assumes everyone already visualizes the examples in their head, skips the scene, and jumps straight to the summary. Steven Pinker makes the same point in The Sense of Style (2014): as writers master a subject, they ascend from concrete events to meta-concepts—"levels," "processes," "approaches." I had lived that 8-second scene; it was crystal clear in my mind. That is why I saw no need to put it on the page. In the reader's mind, however, there was nothing.
This insight isn't new. In 1958, David Ogilvy didn't write "quiet and comfortable" for Rolls-Royce; he wrote, "At 60 miles an hour the loudest noise in this new Rolls-Royce comes from the electric clock." A single measurable scene substituted for abstract praise. The exact same lesson has stood for over sixty years, and I only learned it once I saw 8 seconds on my own analytics panel.
Now comes the honest part, because without the second half of this story, the first turns into dangerous advice.
Once I discovered the power of the scene, I began turning every single sentence into a scene. Every generalization was treated as a crime; I was going to catch them all and replace them with an example. The result: an 800-word post ballooned to 2,400 words. Three client stories, descriptions of two analytics screenshots, a snippet of meeting dialogue—and my editor friend's only question: "What was the core claim of this piece?" I couldn't answer. The examples no longer carried the claim; they had replaced it.
This is precisely the objection raised against fiction's "show, don't tell" dogma within craft literature: writers like Ursula K. Le Guin argue that summarizing (telling) is a legitimate tool—in transitions, for background information, or when pacing demands it, abstract exposition works better. A text that dramatizes everything bloats and loses its hierarchy of importance. Educational science offers a parallel finding: research on "concreteness fading" shows that transfer improves when learning starts with a concrete example and gradually fades toward an abstract principle. Staying purely in the concrete impedes generalization. A concrete scene is proof; an abstract sentence is a portable takeaway. You need both.
The distinction I drew from that bloat phase is this: an example is mandatory for a paragraph's load-bearing claim; it is dead weight in supporting and transitional sentences. The practical test for identifying a load-bearing sentence is simple: if quoted in isolation from the paragraph, the sentence that represents the text's thesis is the load-bearing one. The others are its rationale, transition, or nuance. If you invest your scene budget in a supporting sentence, you misspend the reader's attention budget; everything ends up looking equally heavy, which means nothing feels heavy.
And for the scene itself, the minimum triad is: agent (who), action (did what), observable outcome (what happened). Anything less isn't an example; it's an ornamental adjective. As names, dates, locations, and dialogue pile on, the example drifts into anecdote. My test: if the scene can be understood entirely on its own without reading the claim, it has grown too large. The example must serve the claim, not substitute for it.
If you are in doubt, there is another quick screening tool—a common editorial intuition, not a scientific method, but effective: write the opposite of the sentence. If the opposite is an absurdity no one would ever defend ("low-quality content matters"), the original sentence is filler, not a claim. Either attach a scene to it or delete it. The test doesn't apply to every sentence, of course—the opposites of definitions are nonsensical, yet definitions are not empty; transitions are not expected to carry claims anyway. It is a claim test, and not every sentence needs to be a claim. But when applied to that flashy generalization in your opening paragraph, it often stings.
Throughout this week, we will unpack this distinction with before-and-after editing pairs: under what conditions an example is mandatory versus superfluous; at how many elements a scene stays an example versus becoming an anecdote; and how to dismantle the ubiquitous "X is of vital importance in today's business world" corporate boilerplate. More details in the upcoming posts.
For now, here is the single rule to take back to your workbench: At most one scene per paragraph; but the load-bearing claim cannot go without one.
Which sentence in your own draft is so "true" that no one could ever defend its opposite?