Latest
Anthropic Bans Cruelty Toward Claude: What It Means for WritersWork-for-Hire Contracts: What the Asimov’s Cover Fight Teaches FreelancersGenre Fiction vs Literary Fiction: Don’t Confuse Taste With SkillFlorida Hurricane Prep Rituals: The Grocery Run, the Water Pallet and the Generator in the BoxThe Most Insulting Line of Dialogue Ever Written for the ScreenLoki Through the Ages: From Norse Myth to Marvel, The Mask and Dogma“You Are Utterly Disgusting”: A Book Festival, an AI Cover Ban and a Pile-OnWho Rewrote the Sligachan Legend: AI or the Tour Buses?Why I Don’t Like Reedsy for Ghostwriting: The NDA ProblemLayers: How I Ride Out Florida Power Outages in My ApartmentThe Enshittification of AmazonPublishers Cancel Books Over AI While Using It in SecretI Was Getting 100 Spam Emails a Day. $4.50 a Month Fixed It.World Mental Health Day: Nothing Was Wrong With MeKessler Syndrome: How Space Debris Could Close Earth’s OrbitAmazon Is Blocking Real Readers From Book ReviewsShould a Novella Get a Paperback, or Go Ebook Only?BookFunnel Download Problems: Fixes, Scams and AlternativesSir Sean Connery: A TributeHow to Find Plot Holes in Your Novel (Most Are Character Holes)Reshoring: The Factory Is the Easy PartMost of the Books I Was Forced to Read in High School Were CrapPlot Armor: Signs Your Hero Is Too Safe, and How to Fix ItShould You Sell Lifetime Rights to Your Self-Published Book for a Modest Advance?Shame Doesn’t Stop Artists From Using AI. It Stops Them From Telling You.AI Labels on TikTok and Meta Are Flagging Human WorkAuthor Richard Lowe Completes Peacekeeper, a Four-Book Science Fiction Series He Started at Age 14Sir Sam Neill: A TributeFan Art Copied by AI: Glass Houses, Copyright and the Pile-OnReal Names in a Book: Who Gets Sued, the Author, the Publisher or the Ghostwriter?When Characters Take Over the Plot, Let ThemDoes Human Writing Have a Soul?“You’re Not a Real Author”: The Pile-On Over AI-Assisted BooksDoes AI Have a Soul? Wrong QuestionHumor in Book Marketing: Getting Attention Without BeggingHow Long Should a Chapter Be? Manuscript Habits That Save You LaterThe Business Novel and the Companion Workbook: Two Formats Business Authors OverlookThe Back of the Book: Index, About the Author, Acknowledgments and Back Cover CopyI Build My Own Software Tools With Claude, and Some of Them Bit MeWhat Years of Buying From IT Vendors Taught MeI Write Books for a Living. I Barely Read Them Anymore.Three Management Habits That Waste Good PeopleThe Coach and the Webinar That Sold Me NothingThe Work I’d Cringe At Now, and Why I’m Glad I DoWho Is Your Book For? Build a Reader Avatar Before Chapter OnePreface, Prologue, Foreword or Introduction: What Goes WhereWhy I Won’t Build a Ghostwriting Business That ScalesHow I Hire a Virtual Assistant: Do It, Script It, Hand It OffThe Mail Carrier Who Thought Flipping Houses Was EasyWhat Wedding Photography Taught Me About Pricing Creative Work

Stop Doing the Thinking for Your Reader

TL;DR: A book that reaches every conclusion on the reader’s behalf produces agreement and no retention. People keep what they worked for. The craft version of this is giving the reader the evidence in the right order and stopping one step short of the conclusion. That’s harder than it sounds and is what separates a book from a briefing.

A briefing tells you what to conclude. A book gives you enough to conclude it yourself. Most nonfiction is written as a briefing. The chapter states its point, supports the point, and restates the point, and the reader agrees three times without ever having done anything. Then a fortnight later they can’t tell you what was in it.

The books people quote back to me years later all have one thing in common. They left something for the reader to do.

Over-explaining is the habit I fight hardest in manuscripts, my own included, and I think it’s a failure of nerve. The writer doesn’t trust the reader, so the writer says everything twice, and the reader walks away with nothing of their own. The book gets forgotten, and the author never figures out why nobody recommends it.

Why does pre-digested writing fail to stick?

Why pre-digested writing fails to stickRetention follows effort, and pre-digested writing supplies none. When a reader assembles a conclusion from evidence the author supplied, the conclusion is partly theirs: they remember it as something they worked out, which is a much stronger form of memory than something they were told, and they repeat it to other people as their own view. Hand them the same conclusion directly and they file it as the author opinion, and filed opinions do not survive contact with the next book. The mechanism is not mysterious and almost nobody writes as though they believe it, because handing over the conclusion feels like clarity and withholding it feels like being difficult.Why the conclusion should be theirsThey remember what they worked out. They file what they were told.1You supply the evidenceAnd stop there, which feels wrong2The reader assembles itThe conclusion is now partly theirs3They remember it as their ownAnd repeat it to other peopleas their own view4The alternativeHand it over, and it gets filedas your opinion, and forgottenHanding over the conclusion feels like clarity. Withholding it feels like being difficult.
Why pre-digested writing fails to stickRetention follows effort, and pre-digested writing supplies none. When a reader assembles a conclusion from evidence the author supplied, the conclusion is partly theirs: they remember it as something they worked out, which is a much stronger form of memory than something they were told, and they repeat it to other people as their own view. Hand them the same conclusion directly and they file it as the author opinion, and filed opinions do not survive contact with the next book. The mechanism is not mysterious and almost nobody writes as though they believe it, because handing over the conclusion feels like clarity and withholding it feels like being difficult.Why the conclusion should betheirsThey remember what they worked out. They file whatthey were told.1You supply the evidenceAnd stop there, which feels wrong2The reader assembles itThe conclusion is now partly theirs3They remember it as their ownAnd repeat it to other peopleas their own view4The alternativeHand it over, and it gets filedas your opinion, and forgottenHanding over the conclusion feels like clarity.Withholding it feels like being difficult.

Because retention follows effort, and there was no effort.

When a reader assembles a conclusion from evidence you supplied, the conclusion is partly theirs. They remember it as something they worked out, a much stronger form of memory than something they were told, and they’ll repeat it to other people as their own view.

Hand them the same conclusion directly and they dismiss it as your opinion. Filed opinions don’t survive contact with the next book.

I’d rather a reader argue with me in their head than nod along and forget me by the weekend. Agreement the reader didn’t work for leaves no trace, and a book built on it has wasted everybody’s evening.

The mechanism isn’t mysterious and almost nobody writes as though they believe it, because handing over the conclusion feels like clarity and withholding it feels like being difficult.

The book on this: Ridiculous Things People Actually Believe gives the reader the evidence and stops. That’s harder to write than the explaining version.

What does leaving work look like in practice?

Stopping one step short, on purpose, at the point where the reader can take the step themselves. You give the situation, the specifics, and the thing that makes it odd. Then you stop. The reader closes the gap. It matters that the gap is small enough to be closeable, because a gap too wide is just an unfinished argument.

In Ridiculous Things People Actually Believe I describe somebody demanding peer-reviewed evidence for a medical treatment while accepting a blurry video as proof of magnetism. I don’t then write a paragraph explaining that this is inconsistent. The reader has it before the sentence ends, and that they got there first is why the example lands.

Write that paragraph and the example becomes an illustration of a point instead of the point arriving in the reader.

The book on this: Family Cybersecurity shows the reasoning and states the instructions plainly, the split this piece argues for.

Does leaving gaps work for practical instruction?

Less, and knowing where it stops applying is the whole skill.

Nobody wants a puzzle when they’re trying to configure a router or decide which publishing platform to use. Instruction should be direct, ordered, and free of anything the reader has to work out. Withholding there is obstruction. I’m tired of instructions written as riddles, where the writer gets to look clever and the reader’s left with a router that still doesn’t work.

The place for the technique is the reasoning: why this matters, what it means and what follows from it. Those are the parts a reader should build. The procedure gets none of it, and when the practical section arrives it should be as plain as you can make it.

Family Cybersecurity does both in the same chapter. The reasoning about why security fails at the human seam is shown instead of announced. The list of what to do first is direct, ordered and boring on purpose.

How do you know if you are over-explaining?

Look for the sentence after the good sentence.

Writers produce a line that works, then get nervous and add another explaining what it meant. The second sentence is nearly always the problem. It’s the writer checking that the reader understood, and its effect is to tell the reader they weren’t trusted.

Read a chapter and mark every sentence that restates the previous one in flatter language. Most drafts have one every few paragraphs. Cutting them makes the prose sharper and hands a great deal back to the reader in a single pass.

The other tell is the phrase that announces a conclusion. In other words. What this means is. The lesson here is. Each of those is a signal that you’re about to do the reader’s work, and the material underneath is usually strong enough not to need it.

The book on this: The Death of Thinking is 29 chapters on what happens to judgment when somebody else does the thinking, at a larger scale than one book.

What if some readers miss the point entirely?

Some will, and the trade is worth it.

This is the objection every writer has and it’s a real cost. A reader who doesn’t close the gap gets less from the chapter than if you’d spelled it out. That happens. What you get in exchange is that everybody else gets considerably more, and the book builds a reputation as one that treats people as capable. Writing for the reader who would miss it means writing down to everybody, and readers can feel that within a page even when they can’t name it.

There’s a middle option. Say it plainly once, at the end of a section instead of the start, after the reader has already had the chance to arrive.

The ones who got there feel confirmed. The ones who didn’t get a second route in, and nobody has been told the answer before they had a chance at it.

How do you make a business book the reader participates in?

It turns a summary into an argument the reader participates in. Business books are the worst offenders because the format encourages it. Every chapter announces its takeaway, delivers three supporting points, and closes with the takeaway again. The reader has been walked through a slide deck, and I think the publishers and coaches who push that template are selling executives books nobody will remember a month later.

The version that works gives the reader a situation they recognize, shows what happened, and trusts them to see the principle. Then the principle can be named, once, without being repeated in the summary box.

If you want the neighboring pieces, why your book needs your stories and how to structure a thought leadership book both sit next to this one. The Writing Hub has the rest of the craft material, and my ghostwriting service spends a lot of its time removing the sentence after the good sentence. I think a writer who spells out every conclusion is wasting the reader’s time and throwing away the book’s one real chance to change somebody’s mind, and I’d cut that sentence every time.

Frequently Asked Questions

Why do readers forget most nonfiction books?
Because retention follows effort and the reader was never given any. A conclusion handed over directly reads as the author’s opinion. A conclusion the reader assembled from evidence is remembered as something they worked out, and repeated as their own view.
How do you make a reader think instead of just agree?
Give the situation, the specifics and the thing that makes it odd, then stop one step short of the conclusion. The gap has to be small enough to close, or it reads as an unfinished argument instead of an invitation.
Should practical instructions also leave work for the reader?
No. Instruction should be direct, ordered and free of anything the reader has to work out. The technique belongs to the reasoning sections, not to the procedure, and withholding in a how-to section is obstruction.
How can you tell if you are over-explaining in a book?
Look for the sentence after the good sentence. Writers produce a line that works, get nervous, and add a flatter one explaining it. Also watch for phrases like in other words and what this means is, which announce that you’re about to do the reader’s work.
What if readers miss the point of your book?
Some will, and that’s the cost. Writing for the reader who would miss it means writing down to everybody. A middle option is to state it plainly once at the end of a section, after readers have already had the chance to arrive.

About the Author
Richard Lowe, professional ghostwriter

Richard Lowe is a professional ghostwriter and author with 113+ books authored and 54+ ghostwritten. Before writing full time he spent 33 years in enterprise technology, including 20 years as Director of Computer Operations and Technical Services at Trader Joe's. He writes nonfiction, fiction and memoir, and works with executives and experts on books that build authority.

More about Richard Lowe →

Disclaimer

The views and opinions expressed in this blog post are solely those of Richard Lowe and are based on personal experience and research. This content is for informational purposes only and should not be construed as professional legal, financial, accounting, or business advice. Always consult with qualified professionals before making important business or legal decisions. Richard Lowe is not a lawyer, accountant, or licensed professional advisor, and this content does not establish any professional relationship.

0 comments

No comments yet. Yours can be the first.

Was this useful?

Leave a comment