Why is recalling better than re-reading?
There is a big difference between knowing where an answer is and being able to produce it. Re-reading a times-table chart makes the numbers feel familiar, and familiarity tricks you into thinking you have learned them. Then the chart disappears and the answer will not come.
Retrieval practice flips this. Instead of looking the answer up, you pull it out of memory. That act of producing the answer is what builds fast, reliable recall, and it is the core of how SIXTY trains you.
What is the testing effect?
The testing effect, also called retrieval practice, is the finding that testing yourself on material teaches you more than restudying the same material for the same amount of time. The act of trying to remember is not just a measure of learning; it is an event that causes learning.
Every time you successfully retrieve a fact, you strengthen the path back to it, so it comes faster and easier next time. A times-table chart never makes you do this. A quiz that hides the answer does it on every single question.
Why does recalling beat recognizing or re-reading?
Recognition is easy: you see 7 × 8 = 56 and nod because it looks right. But nodding at a correct answer is not the same as generating it. Recall makes you build the answer with nothing to lean on, and that effort is what cements it.
Re-reading mostly raises familiarity, which is a poor guide to whether you can actually perform. The smoother the chart feels, the more confident and the less prepared you can become. Retrieval gives you honest feedback and stronger memory at the same time.
What are the generation effect and desirable difficulties?
The generation effect is the bonus you get from producing an answer yourself instead of reading one. Typing 56 from memory leaves a deeper trace than seeing 56 printed in front of you.
These benefits come from desirable difficulties: practice that feels harder in the moment but pays off later. A little struggle to retrieve is a feature, not a bug. If practice feels effortless, you are probably recognizing, not learning.
Why should every practice rep end in a correct retrieval?
What you practice is what you wire in. If a rep ends on a wrong answer or a shrug, you have reinforced a gap. The goal is for the final state of every fact to be a correct answer you produced yourself.
SIXTY enforces this: a missed problem stays on screen until you type the right answer, so no problem ends in failure. You always close the loop on a correct recall, which is exactly the state you want stored.
How do I make my practice retrieval-based?
The rule is simple: hide the answer, then produce it. Anything that forces you to commit a response from memory counts; anything you can passively skim does not.
Typing your answer is a clean way to do this because you cannot fake it. There is no half-remembered glance at a chart, just you and the number you can or cannot retrieve.
- Cover or close any chart or answer key before you start.
- See a problem and commit to an answer before checking it.
- Type or say the full answer rather than just recognizing it.
- When you miss, retrieve the correct answer once more so the rep ends right.
- Keep sessions short and frequent so you get many honest reps.
Reading is review. Recall is what sticks.
Start a 60-second sprint →