Models you can decide with
Every model in this section is admitted on one test only. Can you take it into a situation this book never scripted, and decide with it? One that passes stays; the one that failed — learning styles — was cut. You have already met the first model, the two enemies: forgetting, and understanding that never got built. Every model from here sits underneath that one, and each arrived the same way: the machinery, a two-minute check on yourself, then you decide.
In the middle of a chapter there was no room to run a model in full — it earned its page and moved on. Collected here, each one gets space to breathe: the whole machinery at once, not the compressed version you met the first time.
Recognised is not understood
Your memory does two different things with a fact, and from inside they feel identical. It can recognise: the page is in front of you, it makes sense, you can follow along. Or it can produce: nothing in front of you, and you bring the fact out yourself, in order, usable. Recognising is cheap — every re-read and every followed explanation builds it. Producing is built only by producing, then producing again after a gap. The gauge inside you reads recognition and reports it as if it were production, which is why a class you followed perfectly can still feel learned when it is not.
This is the machinery under the mirror’s traps: why re-reading and a well-followed class feel like learning when they have built only recognition. Exams pay only for production; even a multiple-choice paper asks you to produce the reason the near-miss option is wrong. So for any new way of studying — a class, a video, a group, an app — ask which of the two it is building. If the answer is recognising, add a producing step yourself, or drop it.
Take a page you read this week and feel you know. Close it, and for two minutes write out everything you can produce without looking — steps, names, the order. Open the page and mark what came back whole, what came back broken, and what was not there at all. That gap is what you actually have.
It felt completely clear in class — surely that feeling means something.
It means the class was well taught, not that the fact is yours yet. That warm, clear feeling is what recognition feels like from the inside, at its strongest — the explanation was in front of you and it made sense. Close the book tonight and produce it cold; what comes out unaided is what the feeling was actually worth.
Forgetting is fast, then slow
What you learn in one sitting does not fade evenly. It drops fast at first, then slower. Most of a single sitting is gone within a day or two; whatever survives fades on, slowly, over the following weeks. The shape is the same for every topic and every student — only the pace differs, by material and by you. Two things bend it. Each time you come back and produce the material from memory, the fall restarts higher and runs flatter than before. And a topic relearned after forgetting comes back faster than the first time — that earlier effort was never wasted.
This is the machinery behind spacing’s timing: return after a gap, before it is all gone, and later each time. That is where spacing’s widening gaps come from. It also answers what no page scripts. How early does a topic need its first pass to survive to exam day? Will tonight’s solid chapter still be there on Friday? Mostly not, unless you return. Why does a cram work for tomorrow and vanish by next month? And how do you hold a topic for a year, not a week?
Pick a chapter you studied a few days back and have not touched since. Shut the book, and in two minutes write out everything you can still produce — steps, names, the diagram. Open it and see how much came back whole, how much came back broken, and how much was gone. That gap is the curve, on your own chapter.
If most of it fades in a day or two anyway, why put in real effort on the first pass at all?
Because that first pass is what the later, faster relearning stands on. A topic properly met once and then forgotten comes back quicker than one you are meeting cold — the effort is not lost, it moves out of reach rather than out of existence. And every return afterwards restarts the fall from a higher point and lets it run flatter, so the first pass is the thing every later pull is built on.
The head holds about four things
The part of your mind that does the thinking holds about three or four things at once for almost everyone, and no trick makes it many more. A new topic feels impossible not because you are slow but because it arrives as a dozen pieces and only four fit. A worked example helps because it takes the pieces off your hands, so the four slots can watch the pattern. A table or a spelling learned until it comes without effort stops being a piece: it is one chunk, and it hands a slot back to the problem. That is the honest case for rote — not that reciting is understanding, but that a fluent chunk gives the four slots room to understand.
This is why a worked example goes first on a new type of problem and fades once the pattern is familiar. Your slots are busy watching, not solving, until the pattern is a chunk. It lets you decide, unscripted, when a topic will not go in: cut it into groups of about four and learn the groups before the whole. When a skill stays slow, find which sub-part still eats a slot and drill that one to fluency. And when choosing what to learn by heart, choose what you will need inside a bigger problem.
Pick a topic that currently feels like too much at once. Write down its separate pieces, one per line, and count them. If it is well past four, group the pieces that belong together and name each group in one word. Learn the groups first; the whole topic gets lighter once they are chunks.
Learning something by heart feels like the opposite of what this book keeps telling me to do.
Reciting from memory is producing too — that part is not the problem. What rote cannot do is stand in for understanding the thing you are chunking. Learn the table until it needs no effort, and the point of chunking it is to free a slot for the problem the table sits inside, not to replace working the problem out.
Practice carries only so far
What you practise carries over only to situations that look like the practice. The further a new situation sits from the practised one, the less of it arrives — different wording, other topics mixed in, a clock running. Near transfer is normal; far transfer is rare and never automatic. Working every exercise in the book prepares you for the book’s exercises, in the book’s own wording, and no further. Two things stretch how far it carries. Practising the same idea across varied cases makes the principle recognised in new clothes. Practising in the form the test will take builds the exact path ahead of time.
This is why mixing topics in practice carries further into an exam that mixes them too, more than running one topic at a time ever does. It lets you decide, for any exam or task this book has not covered, how far it sits from what you have actually practised. Close that distance yourself — vary the cases, match the format, add a clock — rather than doing more of the same. It also tells you which of your old skills will help in a new place and which will not.
Look at a practice question you did today and the form the real exam actually takes — timed or not, multiple choice or written, one topic or mixed. List every way they differ. Each difference on the list is distance the practice has not yet closed.
I have worked through every exercise in the textbook — doing more feels like a waste of time now.
More of the same exercise builds more of the same narrow skill: solving that exact question type, in that exact wording, with no clock running. The exam mixes topics, changes the wording and adds a clock. The efficient next step is not another textbook exercise — it is one that closes those specific gaps between practice and the paper.
The level the question asks
A question can ask for the same topic at six different levels of thinking, and the level decides what practice actually counts. From the bottom: remember it, state it, define it. Understand it — explain it in your own words. Apply it to a new case. Analyse a situation into its parts and say how they relate. Evaluate which is better and defend the judgement. Create something from it. The verb in the question names the level, and a paper’s marks sit at a level whether or not the syllabus ever says so out loud.
This is the job the past-papers tool does when it maps a paper. It reads the verbs to find which level the marks actually sit at, something the syllabus never states. Hours at the wrong level feel like preparation and are not. It lets you decide what “knowing this topic” has to mean for an exam nobody has decoded for you. Read the verbs, find the level, and practise at that level rather than below it.
Open any past paper and read only the verbs — state, calculate, compare, justify, design. Sort the questions by verb into the six levels. Look at where most of the marks land, and compare that to the level you actually practised at this week.
My teacher only ever tests definitions and formulas, so the higher levels must not matter here.
Read the actual paper, not the classroom drills — a teacher’s practice questions and the board’s own verbs are not always the same test. Open last year’s paper and read what it asks for in its own words; if “calculate” or “justify” appears, recall alone will not answer it, whatever the classroom drilled.
Skills grow at the edge
Knowledge and skill are built differently. A skill — solving a type of problem fast, writing an answer that scores, code that runs — does not improve with hours of doing it. It improves with deliberate practice. Pick the one part just beyond what you can do now. Work on that part alone, not the whole performance. Feedback on each attempt at once, correct, go again. Stop practising what you can already do; that feels productive and builds only ease. It is tiring in a specific way, because it keeps you at the edge, and it is why two people with the same hours end up years apart.
This is the loop underneath a plateau: the facts inside a skill still obey the usual tools, but the skill itself moves only by working its edge, with feedback. It lets you decide, for any skill-shaped goal, what the component is, where the feedback comes from, and where the edge currently sits. It also lets you read a long plateau honestly — is today’s practice still at that edge, or has it slid into repeating what is already comfortable?
Look at your last practice session for one skill. Name the one part that went wrong. Name where the feedback on that attempt came from — a key, a teacher, a recording, or nothing. If the answer is nothing, that is the missing piece, not the skill itself.
If daily practice is not moving me forward, maybe this subject is simply not for me.
Daily is not the same as deliberate. A session at a comfortable pace, with nothing telling you which part was wrong, trains ease at the level you already hold — it says nothing about what you are capable of. Find the one part that keeps failing, get it checked, and work that part alone before deciding what you are or are not built for.
Hours are not the measure
Ten hours on a topic feels like done, and more hours feels like more learned. What you can still produce a month later depends on what the hours did, when they fell, and whether a correcting signal came back. How many there were matters far less. The same ten hours spent re-reading in one weekend, or producing across four spaced sittings, leave very different amounts behind. The same ten problems checked against an answer key, or left unchecked, teach very different things. Hours are the input; cold recall on the day is the output, and the only measure.
A plan written only in hours — “three hours of chemistry a day” — has not actually said anything yet. It becomes a plan once it says what each hour does, how the sittings are spread apart, and where the check comes from. That is the shape every playbook in Part B takes, and the question to ask of any plan you write yourself.
Look at tomorrow’s study plan. For each hour on it, write in one line what it will actually do — re-read, produce from memory, check against an answer. An hour with no answer written next to it is an hour still undecided, not yet a plan.
I put in more hours on this subject than on anything else — that has to count for something.
It counts as effort spent, which is real and not nothing. Whether it counts as learning is a separate question, answered by what you can produce cold, not by the timetable. Test yourself on one hour’s worth of it right now, without the book, before assuming the hours already did the job.
The map of the models
Seven models, and the question each one answers when no page of this book covers your situation. Will it still be there? Return before it is gone. Do I know this, or does it just look familiar? Close the book and produce it. Why will this not go in? Chunk it. Am I practising what the paper actually asks? Read the verbs.
Will this practice carry to that test? Vary the cases, match the form. Why am I stuck at the same level? Find the part that is failing. Did I do the work, or just put in the hours? Count the sittings, the spacing, the checks. Underneath all seven, the two enemies: everything either makes you fetch or makes you build. None of this is for reciting. Each is a two-minute check and a decision; run the check, decide, and go back to work.