Review and reflect: close the loop#

Here’s the step almost everyone drops first. You finish a study session, close the book, and move on — no pause to ask how it actually went or why. That pause is enquire, the review-and-reflect phase of the learning loop, and skipping it is the single most expensive habit a learner has. Not because reviewing is some virtuous chore, but because review is where the next round of real learning gets decided. Do it well and every session afterwards is aimed better. Skip it and you’ll keep planning tomorrow on a flattering guess about today.

I used to call this “the last step.” That was the wrong word, and the wrong shape. Calling it last quietly tells you the real work is over and review is a tidy-up — a record of what you did wrong. It isn’t. The answer you get here rolls straight into your next plan, which is why the learning process is a loop, not a line. Review isn’t the end of the lap. It’s the steering for the next one.

Reflection isn’t reading your notes again#

The trap is that reviewing feels like rereading, so people reread — and rereading is exactly the method most likely to fool you. When the page flows easily the third time through, your mind reads that smoothness as proof you know it. You don’t; you just recognise it. That’s the illusion of competence, and it’s why fluent-feeling study routinely overestimates what you’ve actually retained (Dunlosky et al., 2013). A real review makes you produce the material with the book shut, not slide your eyes over it one more time.

So enquire is the practical home of metacognition — judging what you actually know versus what you only think you know. It’s worth getting the full story on that, because it’s the most useful skill a learner can build: see knowing what you know . The short version drives everything below: the warm glow of familiarity is not evidence of memory. If a session felt frictionless, treat that as a reason to check, not a sign you’re done.

Keep a review log#

Reflection that lives only in your head evaporates by tomorrow. Write it down. A review log is just a running record of what you set out to do, what actually happened, and what you’ll change — kept somewhere you’ll see it before the next session.

• What format, and when to use one. A notebook line, a spreadsheet row, a note on your phone — the medium matters far less than the habit. Match it to how complex the learning is.
• Phrase it as a next move, not a verdict. “Couldn’t recall the second half — self-test it cold tomorrow” beats “did badly.” Reflection that names the action is the kind you actually act on.
• Turn recurring lessons into assertions. Patterns you keep relearning become a short training-assertions list — and you can make that list stick by memorising it.

Run the four reviews#

There isn’t one review; there are four, at four different timescales. Each catches something the others miss.

• Immediate review — feedback while you work. Catch and correct errors as they happen, ideally against the worked answer right after you attempt the problem, not forty problems later. One caution from the modern picture of feedback: don’t stay on a permanent drip. If something corrects you every time you drift, you never learn to notice the drift yourself — so the scaffolding should fade on purpose as you take over. There’s a whole page on getting this right: the modern model of feedback .

• Lesson review — what worked, and why. After a session, write a few frank notes: what were you aiming at, what came out, where did it break down? Mark review points as they crop up (a symbol in the margin works well), then dig past the surface — the five whys is a simple way to chase a problem down to its root cause, and “five actions” turns that root cause into something you’ll actually do differently next time. Pull others in too — an instructor, coach, or colleague sees gaps you can’t.

• Formal review — test to confirm, and to cement. Tests, exams, orals, quizzes. The old framing treated these as pure measurement — a thermometer for recall. They’re more than that. The act of retrieving under test conditions is itself one of the strongest ways to make a memory stick: testing doesn’t just measure learning, it produces it (retrieval practice ). So view a test as a learning event, not a verdict — and when results don’t match what you expected, that gap is information about your judgement, not a reason to despair. Always review after the exam, not just before it.

• System review — is Memletics itself earning its keep? Step back periodically and review your overall use of the system: which techniques are pulling their weight, which parts you’ve quietly stopped using, what to adjust. Each part of the manual gives you something to check here.

Don’t fear the mistakes — but do mine them#

Reviewing well means looking straight at what went wrong, and that’s uncomfortable. So let’s be clear: making mistakes is part of how learning works, not a sign you’re bad at it. A wrong answer you then correct teaches you more than a right one you got by luck — even an unsuccessful attempt to recall something improves the next attempt, as long as you find out the right answer afterwards (Kornell & Bjork, 2008). The point of enquire isn’t to keep a tidy ledger of your failures. It’s to notice them while you can still act, understand why they happened, and aim the next round better.

There’s a calibration trap worth naming, too. The less you know about something, the worse you are at judging how little you know — beginners’ confidence is least trustworthy exactly when it feels most solid (Kruger & Dunning, 1999). So when you’re new to a topic, lean harder on the cold test and lighter on the feeling. Let the closed-book result, not the warm glow, tell you where you stand.

Takeaway#

Review isn’t the end of the lap; it’s the steering for the next one. Don’t reread — test: close the book, see what you can actually produce, and treat the gap between what you expected and what you managed as your truest feedback. Keep a review log , run the four reviews at their four timescales, and mine your mistakes instead of filing them. Then the answer rolls straight into your next plan — which is the whole point of running learning as a loop rather than a line.