"Copy the problems you got wrong into a notebook — neatly." It's a staple of study advice; you've almost certainly been told it at some point. Headings in colored pen, the model answer carefully transcribed, the important parts underlined. Finishing a notebook like that feels genuinely satisfying. But let me put the conclusion first: the prettier you make your mistake notebook, the less you improve. To be precise, the prettiness itself isn't the harm. The harm is that the time spent making it pretty produces not a single act of trying to remember — the thing that actually strengthens memory.
The reason is simple: memory consolidates most strongly not when you summarize something, but when you struggle to recall it. Rewriting, transcribing, and rereading keep your hands moving and consume time, so they produce a strong feeling of "I studied." Yet research in educational psychology has repeatedly reported that this kind of work falls into the less efficient class of methods for retention. What does work, the research says, is "retrieval practice" — recalling the answer on your own without looking — and "spaced repetition" — taking another run at something right around the time you're starting to forget it.
So we replace the design philosophy of the mistake notebook from the ground up. Build it not as a fair-copy album, but as your own personal "retest device." Minimize the time spent making it; maximize the number of times you re-solve from it. In this column I'll lay out exactly how to build and use one, with one line on "why it works" attached to every step.
What this column covers — and how it differs from cycling a problem set
Let me declare the boundary with the neighboring columns first. I previously wrote about how to cycle a problem set — "go rough on the first pass, and from the second pass on, re-solve only what you got wrong." That column is about cycling your wrong answers within a single problem set. This column handles the outside of that: a method for collecting the wrong answers that arise across multiple materials — problem sets, past exams, mock exams, class handouts — into one device and turning them into an asset. It also works as the final catch basin for the questions that survive your second and third passes through a problem set.
One more: in the column on restarting a stalled study routine with systems, I wrote the move of "putting only yesterday's wrong answers in front of you again the next day." That move and the first retest in Step 4 of this column — the next day — are the same motion. There it serves as the smallest first step for getting moving again; here it works as one part of a device you keep running until exam day.
I also once wrote about redoing your self-assessment by counting records instead of trusting memory. This column shares that spirit — deal with yourself based on records, not feelings — but the target differs: that one was about self-assessment; this one is about managing wrong answers.
Why "summarizing it neatly" doesn't work
In 2013, a large review paper comparing the effectiveness of major learning techniques was published (Dunlosky et al.). Methods in the "face the material one more time" family — rereading, highlighting, summarizing — received low ratings across the board, while only two earned the top rating: testing yourself (retrieval practice) and spacing your study out over time (distributed practice). There's also a famous experiment (Roediger and Karpicke, 2006) comparing groups who repeatedly reread a passage with groups who were repeatedly tested on it: immediately afterward the rereaders scored higher, but one week later the tested group had clearly pulled ahead.
What makes rewriting dangerous is not just its low efficiency — it's that the felt payoff is large. Gaze at a beautifully written-up notebook and a sense of "I understand this" arises. Psychology has a name for the phenomenon this resembles: the "illusion of fluency" — mistaking the smoothness of processing (it reads easily, it looks familiar) for understanding or memory. Being able to read something is no guarantee of being able to recall it. And in the exam room, the only thing you're ever asked is whether you can recall it.
The seven steps below all exist for one purpose: to embed those two principles — retrieval practice and spaced repetition — into the physical device that is your notebook.
Step 1: Select which mistakes get in — a one-line diagnosis across three causes
Don't record every mistake. First, diagnose the cause of each wrong answer in one line, as one of these three:
- Knowledge gap — you simply didn't know it, or hadn't memorized it
- Misreading — you misread the problem statement or its conditions
- Procedural slip — you knew the method, but it broke down partway through
Only mistakes carrying this diagnosis — reproducible mistakes — go into the notebook. Pure careless errors, like a slip of the pen or a transcription glitch, stay out. A careless error is not a gap in knowledge, so it sits outside this notebook's remit — re-solving is unlikely to fix it. That's the kind of mistake you prevent with mechanisms — physically confirming your answer-sheet rows with a finger, a fixed priority order for your final review — and I wrote about those in the column on exam-day time allocation.
→ Why it works: putting the cause into one line changes the nature of the work from "memorize the right answer" to "pinpoint how I go wrong," which is what lets you dodge the same trap next time — and narrowing the entry criteria turns the notebook into a device holding only questions worth re-solving, raising the value of every single retest.
Step 2: The format — problem on the left, "how I got it wrong" in one line on the right. Never copy the model answer
This is all the format you need.
- Left side: the problem itself. Write it out if it's short; if it's long, just the number and location — "workbook p. 34, problem 3." Pasting in a photocopy is fine too.
- Right side: one line on what you got wrong and how — the three-way classification from Step 1, plus one concrete note (e.g., "Procedural slip — dropped the sign when moving the term").
- What you never write: the model answer or the explanation. No transcribing.
Leaving out the model answer isn't laziness — it's the heart of this device. If the answer is written in the notebook, your eyes catch it when you re-solve, and "seeing" happens before "recalling." That kills the retrieval practice. The answer and the explanation already exist in the original problem set or past-exam solutions; there's no need to hold them twice. As long as the location is written down, you can go back there to check your work.
→ Why it works: what strengthens memory is not "seeing" but the effort of trying to recall, and physically excluding the answer from the notebook creates a structure where opening it forces retrieval practice, every single time.
Step 3: How to use it — never reread. Open it only to re-solve with the answers hidden
Fix this notebook's use to exactly one thing: retesting. Forbid yourself from flipping through it, from gazing at it for reassurance. When you open it, look at the problem on the left and actually solve it — in the margin, or on scrap paper. Don't settle for "ah, this one — yeah, I've got this" in your head. Move your hand, produce an answer, then check it against the explanation in the original material.
→ Why it works: there's a wide gulf between "I understand it when I see it" and "I can produce it on my own"; rereading can only verify the former, while re-solving directly trains the latter — and exams only ever ask for the latter.
Step 4: The re-solving schedule — next day → 3 days later → 1 week later → right before the exam
Don't leave the timing of re-solving to your mood on the day. Fix it in advance with a template.
- The next day — first retest
- Three days later — second
- One week later — third
- Right before the exam — final check
Let me be honest here: there is no rigorous basis for these exact numbers — "next day, three days, one week." What the research shows is the principle that repetitions spaced further apart make memory last longer; the optimal number of days shifts with the material and with how far away your exam is. So treat these numbers as a practical template for translating the principle into daily life. Drifting a little is fine. What you protect is the rhythm: "once more, right when I'm starting to forget."
→ Why it works: effortfully dragging a memory back from the edge of fading is said to be what consolidates it most strongly (the idea known as "desirable difficulties"), while re-solving something you still fully remember is easy — and yields correspondingly little.
Step 5: The strike-through rule — graduate after two consecutive correct answers, spaced apart
Make a small check column at the edge of each problem and mark it right or wrong every time you re-solve. Then: a problem answered correctly twice in a row, on retests separated by days, gets a horizontal line through it — it has graduated. Don't re-solve it again until the final pre-exam check.
Both conditions — "in a row" and "days apart" — carry meaning. Solving something twice on the same day may only mean the memory was still fresh. If you can produce it twice with days in between, you're entitled to judge it as retained. And to be just as honest as I was in Step 4: this "twice" is not a threshold from the research either. Once can't be told apart from recent memory; demanding three times makes the cycle too heavy to sustain. Treat it as a design value for day-to-day use, sitting between the two.
→ Why it works: without a graduation rule the notebook keeps swelling until cycling through it becomes impossible, whereas striking through keeps your time concentrated purely on the problems you still can't solve — and the growing number of struck lines, the notebook getting "thinner," becomes progress made visible. This notebook is finished not when it's written, but when every line has been struck out.
Step 6: Cap the production cost — 3 minutes per problem, 10 minutes per day
Put a physical ceiling on the making. As a guide: 3 minutes per problem, 10 minutes total per day. If you can't write an entry in 3 minutes, stop copying the problem and write only its location. If you're about to exceed 10 minutes, re-select what deserves to go in. Care beyond the cap has no value in this device.
→ Why it works: the failure of a mistake notebook I consider most dangerous is that making it becomes the goal and studying ends with the satisfaction of having made it — a time cap seals off that trap with physics rather than willpower.
Step 7: Paper or digital — decide by one criterion only: which has less friction to start re-solving
A paper notebook, or photos plus an app? Plenty of people agonize here, but you need only one criterion: which one, for you, has less friction between "I should re-solve" and actually starting? Photographing problems into a flashcard-style app is strong at collecting across multiple materials and automating the spacing. On the other hand, for subjects like math where you write your answer out by hand, opening a paper notebook and immediately solving in the margin is often faster. Splitting by subject is fine too.
Let me add one concrete example from our own shelf here. passed.jp's English problem set is built so that right after you finish a set, you check your answers against the correct ones in a list and go back to the explanations of only the questions you missed — and you can re-solve the same grade's or the same unit's questions as many times as you like. For English drilling, in other words, the site already plays something close to the role of a digital retest device. What the paper device in this column takes on is everything outside that — math and science answers written by hand, and the wrong answers scattered across multiple materials.
→ Why it works: the results this device produces are, I believe, determined almost entirely by the number of re-solves — so the choice that reduces the friction to start is precisely the choice that maximizes that count.
What not to do
Most of the prohibitions are the flip side of the steps above. Decorating with colored pens (two colors at most, if any), transcribing model answers (Step 2), opening it just to reread (Step 3), recording every careless error (Step 1) — I won't repeat them here. Folded into one line: never spend this device's time on work that produces zero attempts to remember. That's all.
Beyond those, two failures remain that haven't been named yet. Both are tempting, so let's name them in advance and seal them off.
- Don't wait to start until it's perfectly built. Starting with today's one mistake is fine. This device grows while being used.
- Don't rewrite a page you've already made. A messy page still functions. The thirty minutes a rewrite costs would buy you several re-solves.
Closing: the thinner and messier the notebook gets, the closer you are to passing
A beautiful notebook is something you make to show other people. A mistake notebook is shown to no one — so its visual polish earns you not a single point. Only two metrics measure this device: the quality of your selection of what goes in, and the number of times you re-solved from it.
And this notebook has one more fine property. Right before the exam, when little time remains, it has become the only textbook in the world made entirely of the places where you, specifically, go wrong. Store-bought materials don't know your weaknesses; this notebook contains nothing else. The value of a single hour in the final stretch transforms.
The meticulousness it takes to keep a beautiful notebook is, I think, a genuine talent in itself. Which is exactly why I'd ask you to point that meticulousness not at fair copies, but at selection and spacing. As the struck-through lines multiply and the notebook grows thinner and messier, you are getting closer to the "passed" that passed.jp hangs on its signboard.
