kernWhy You Forget What You Read (and How to Stop)
It's not you. It's not the book. It's a 140-year-old curve — and once you see it, you can't unsee what it does to every book you finish.
The forgetting curve, in one paragraph
In 1885, Hermann Ebbinghaus memorized lists of nonsense syllables and tested himself at intervals, producing the first quantified picture of forgetting. The result — replicated many times since, including a faithful 2015 reproduction — is an exponential decay: memory falls off a cliff in the first days, then keeps sliding more slowly for weeks. Without any retrieval, the majority of new information is inaccessible within a month.
What that means for a book
Say you finish a 300-page non-fiction book today. Roughly, here's the trajectory:
- Day 1: The argument feels vivid. You could explain the thesis, the best examples, the surprising claims.
- Week 1: The structure is blurring. You remember the big idea and the two or three examples that hit hardest.
- Month 1: You remember that the book was good, its rough topic, and a feeling. Asked to explain its actual argument, you paraphrase the marketing copy.
- Year 1: The title, the cover, one anecdote you've retold enough times to keep — because retelling is retrieval.
That last point is the tell. The parts of books you do remember are the parts you retrieved: ideas you told a friend about, used at work, argued with. Retrieval is not how you check what you remember. Retrieval is what creates remembering.
Recognition is lying to you
Reopen a book you read last year and skim a chapter. It all feels familiar — "yes, I know this." That's recognition, and it's nearly free: the text is in front of you doing all the work. Recall — reproducing the idea with the book closed — is the expensive operation, and it's the only one available in real life. In a meeting, mid-conversation, or when a decision needs the idea, there is no page in front of you.
This gap is why re-reading and skimming highlights feel productive while doing almost nothing. They train recognition. Life tests recall.
The one intervention that changes the slope
Every time you successfully retrieve an idea, two things happen: the memory gets stronger, and its decay gets slower. Retrieve it again later and the curve flattens further. After a handful of well-timed retrievals — spaced days, then weeks, then months apart — the idea becomes cheap to keep for years.
The timing matters. Retrieving too soon is easy and teaches little; too late and the memory is already gone. The sweet spot is just before you'd forget — which is exactly what a spaced repetition algorithm computes for you.
Books don't fade because your memory is bad. They fade because reading is a single exposure, and single exposures always decay. Scheduled retrieval is the fix, and it costs minutes.
Watching the curve — and beating it
Kern is built around exactly this loop. Add any book you've finished — just the title — and it becomes a deck of recall cards built from the book's key ideas. Then the app schedules your retrievals: cards resurface right as they start to slip, and five minutes a day covers your whole library.
Kern even makes the forgetting curve visible. Every book lives on the Wall: review it and it stays inked; neglect it and you literally watch it fade toward "going cold." No streaks or guilt mechanics — just an honest picture of what's still in your head.
Books fade. Bring them back.
First two books free. No account, no sign-up, works offline.
Download on theApp StoreFrequently asked
Is forgetting faster for some people?
Decay rates vary a little, but nobody escapes the shape of the curve. Prior knowledge helps — ideas that connect to things you already know decay slower — which is one reason the tenth book on a topic sticks better than the first.
Does writing a summary stop the decay?
It helps encoding (one good retrieval, right after reading), but a single retrieval only bends the curve once. Retention needs repeated, spaced retrievals over weeks and months.