You read constantly. You highlight. You take notes. You save articles for later. And yet, when you sit down to write, almost none of it shows up in your work. The reason has been studied for decades and has a name: the knowing-doing gap (Pfeffer & Sutton, 1999). Most reading apps make this gap worse, not better, by optimizing for capture and ignoring the harder part — turning what you read into something you can actually do.
You've read more books in the last three years than most people read in a decade. You've highlighted thousands of passages. You have folders of articles, a wall of saved tweets, a notebook of quotes.
And the writing? The writing is fine. It hasn't gotten dramatically better. The ideas in your books, when you can identify them, aren't visible in your prose. You suspect, sometimes, that you've been collecting reading material the way some people collect stamps — with great care, and no intention of ever using it.
This is one of the most common quiet frustrations among serious nonfiction writers. The reading should be feeding the writing. Most of the time, it isn't.
The knowing-doing gap (Pfeffer & Sutton, 1999) is the dominant problem in professional practice — not ignorance, but failure to convert knowledge into action. Highlighting stays at the comprehension layer. The fix is an active step that follows reading.
What does the research actually say?
In 1999, the Stanford business professors Jeffrey Pfeffer and Robert Sutton published a book called The Knowing-Doing Gap. They studied why organizations that knew what to do — they'd read the books, attended the seminars, hired the consultants — so often failed to do what they knew. The gap between knowing and doing, they found, was the dominant problem in professional practice. It wasn't ignorance that held people back. It was the failure to convert knowledge into action.
This finding generalizes well beyond business. The educational psychologist Benjamin Bloom and his colleagues, back in 1956, built a taxonomy of cognitive levels that placed mere comprehension near the bottom of the learning ladder. Application — the ability to use what you understand — sat several rungs higher. Analysis, synthesis, and creation sat higher still. Bloom's point was simple: understanding something is a small accomplishment. Doing something with it is the real one.
The psychologist K. Anders Ericsson's work on deliberate practice, developed over decades and popularized in the 1990s, sharpened this further. Expertise doesn't come from exposure. It comes from active, effortful engagement — the kind of practice that forces you to use what you know, fail, adjust, and try again. Reading without practice is the educational equivalent of watching someone exercise.
For writers, this has a hard implication. If your reading consists of highlighting, capturing, saving — without an active step that forces you to use what you've read — you've stayed in the comprehension layer. The ideas don't make it into your writing because they were never converted to action.
Why aren't highlighting and capture enough?
Most reading apps are built around the assumption that the goal of reading is to remember what you read. Highlight it, save it, tag it, surface it later. The implicit theory is that if you can re-read your highlights, you'll absorb the ideas.
This is roughly the same theory of learning that underpins the textbook. Pick up a textbook from your high school days and ask yourself: did re-reading the highlighted passages make you fluent in the subject? It didn't. The textbook was useful only when paired with the active work — solving problems, writing essays, making arguments. Reading alone produced almost nothing.
The same is true for grown-up reading. Highlighting feels productive. It produces a satisfying record of your engagement. But the record is mostly inert. It doesn't force you to do anything with the ideas. So the ideas stay where they were — in the book, not in your work.
What actually helps?
The principle is straightforward: the moment of reading needs to be followed by a moment of doing.
Discuss the passage, not just with yourself but in real conversation. Articulating a half-formed idea to another mind tends to expose what you actually understand and what you don't.
Explain the passage in your own words, addressed to a specific reader. This is what teachers have always done, and it's why teaching a thing is one of the fastest ways to learn it.
Practice the passage. Turn the idea into something you can begin doing today, in your actual life or in your actual writing. This is the step almost nobody does, and it's the one that closes the knowing-doing gap.
Note the passage in your own words, not as a quote. The act of paraphrasing forces engagement at a deeper level than highlighting.
Most reading apps offer the first three only weakly, if at all. They offer highlighting and capture, which sit at the lowest rung of Bloom's taxonomy and don't actually convert reading into capability.
How Wretify's Reading Room works
Wretify is the only writing app I know of that puts reading and writing in the same room. When you read a passage that matters, you have four actions available: Discuss, Explain, Practice, and Note.
Discuss starts a conversation with the AI about the passage — and the AI has read your own writing, so it's talking to you, not to a stranger reading the same book. Explain unpacks the passage with the context of the chapter around it. Practice — the one no other app offers — turns the idea into something you can begin doing today. Note is the simplest action: write the passage in your own words, no AI, just you. The note is saved to whichever chapter of your own writing you're currently working on, exactly where it belongs.
The Practice button is the one I'm proudest of. It's the embodiment of the knowing-doing gap, addressed directly. Reading something useful is no longer the end of the transaction. It's the beginning of a small experiment in your own life or your own writing.
I built this because I'd spent years filling Readwise with brilliant highlights and watching them go nowhere. The highlights weren't the problem. The absence of a next step was the problem.
Reading without practice is the educational equivalent of watching someone exercise.
- The knowing-doing gap (Pfeffer & Sutton, 1999): the dominant problem isn't ignorance — it's failure to convert knowledge into action.
- Bloom's taxonomy (1956) places comprehension far below application, analysis, and synthesis.
- K. Anders Ericsson's deliberate practice: expertise comes from active engagement, not exposure.
- Highlighting and capture stay at the comprehension layer — they don't convert reading into capability.
- Wretify's reading mode offers Discuss, Explain, Practice, and Note — with Practice being the unique one that closes the gap.
This article was written in Wretify. Try it free →
Frequently asked questions
Mildly. The research on highlighting as a study technique is unflattering — it produces a feeling of productivity without proportionate gains in retention. It's useful as a marker, not as a learning method.
Explain is an AI-assisted unpacking of the passage in the context of what you're reading. Note is what you write, in your own words, with no AI involvement. Both have value. Explain helps you understand; note forces you to articulate.
The AI takes the idea in the passage and suggests something concrete you could try, today, in your own life or your own writing — a small experiment in applying what you just read. The point isn't to do everything it suggests. The point is to convert the reading from an idea into a beginning.
Not quite. The goal is to make reading and writing one activity. Reading that doesn't flow into writing is incomplete. Writing that isn't fed by reading goes thin fast.
That's a useful signal. If the passage doesn't suggest any action you could try, it might not be as actionable as it felt. Or it might be a passage you're meant to sit with rather than apply. Both are fine. The Practice button is an invitation, not an obligation.