Reviewing your whole system#

The other reviews in this section all point inward — at one session, one test, one mistake. This one points at the machine that runs them. Every so often, pull back from the page and ask a bigger question: is the way I’m learning actually working? Not “did today go well,” but “is my whole approach — my state, my process, the techniques I lean on — earning its keep?” That’s a system review, and it’s the outermost loop of the whole learning cycle : the same plan-do-review wheel, turned slowly, with your own method as the thing under examination.

It matters because the rest of the manual gives you a lot of moving parts, and nobody adopts all of them at once. Over weeks you drift. You quietly keep the comfortable habits and let the awkward-but-useful ones lapse — usually without noticing. A system review is the scheduled moment you notice on purpose, before the drift hardens into “just how I study.”

Why bother — and how often#

This isn’t busywork; it’s the part of self-regulation that researchers find separates strong learners from the rest. Across a large body of evidence, learners who plan, monitor and reflect on their own learning tend to outperform those who don’t — and, importantly, these are learnable habits, not fixed traits (Zimmerman, 2002). The single-session reviews build the habit at small scale. The system review does it at the scale of your whole method, where the biggest, slowest mistakes hide.

You don’t need to do this often. Once a month, or at the natural seams of a project — end of a unit, after an exam, when you start something new — is plenty. The point is that it happens at all, on a schedule, rather than only when something has already gone badly wrong.

What to check#

Walk the dimensions of the system and ask a hard question of each. Keep your training assertions and recent review log entries open while you do — the patterns are usually already written down.

State. Are you actually getting yourself into a fit state to learn — rested, watered, focused — or have you been grinding tired and calling it discipline? Which parts of learning state have you let slide?
Process. Are you running the full loop — exploring , locating , arranging , reinforcing , reviewing — or skipping straight to the comfortable middle? If you’re cutting a step, name why. Usually it’s that the step felt slow, not that it was useless.
Techniques. This is the big one, because not all techniques are equal and it’s easy to keep the wrong ones. Decades of comparison have shown that some popular study habits — rereading, highlighting, lone re-summarising — do far less than they feel like they do, while a small set of methods (spaced retrieval practice above all) reliably outperform them (Dunlosky et al., 2013). So ask the pointed version: which of my go-to techniques are high-payoff, and which just feel productive? Which proven ones have I never given a fair run? A system review is where you cull the comfortable-but-weak and promote the awkward-but-strong.
Styles and approach. Which styles and senses are you leaning on, and which could you bring in? And at the planning end — are you setting real targets and tracking against them, or flying by feel?

These are prompts, not a form to file. Run down a chapter’s headings to trigger more of your own, and reread the sections you’ve struggled with — often the “technique that isn’t working” is one you half-remember and never set up properly.

Don’t stop at what’s in this guide#

One frank note to close on. Throughout this manual I’ve kept things to a workable depth — enough to use, not the last word on anything. So when a system review turns up a topic you want to go deeper on, don’t treat what’s written here as the ceiling. Two of the principles of the Explore step are to go wider and deeper, and they apply to your own learning method as much as to any subject. Chase the thread — a good paper, a better book, a coach who can see the gap you can’t. The whole aim of a system review is to send you back into the loop running a sharper version of it than before.

Takeaway#

Periodically step back and review the whole machine, not just the last session: your state, your process, and above all your techniques — keeping the ones that genuinely pay off and dropping the ones that only feel like work. Do it on a light schedule, lean on the patterns your review log already caught, and let it feed your next plan . It’s the slowest turn of the loop, and often the one that changes the most.