A Servitor for Learning: Retrieval, Not Exposure
Exposure feels like learning and leaves no trace. Retrieval is the part that sticks.
Table of Contents
Exposure is not learning
Rereading a page feels productive because it is fluent. Fluency is not recall; it is familiarity with the text, and it disappears under exam conditions.
Retrieval is the act of producing the answer without the page. It feels worse and works better. A learning servitor should be built around retrieval sessions.
This is the one place where the practice borrows directly from cognitive science: testing yourself is a study method, not an assessment.
Counting retrieval
Write the task as retrieval sessions: "twenty retrieval sessions of twenty minutes before 20 December, with a score recorded for each".
Name the material. A session on "everything" is not a unit; a session on one chapter or one deck is.
Write the minimum score that counts as a session. A session where you recalled nothing is still a session, but it is a different data point.
Spacing and review
Space the reviews: today, in three days, in a week, in three weeks. The gap is what makes retrieval effortful, and effortful retrieval is what consolidates.
Keep one deck or one notebook. Splitting material across five apps is how review becomes browsing.
At each review, write the score in the log. The score is the only honest measure of whether the spacing is working.
Feeding before study
Feed before the session, not after. The feeding is the cue: mark, name, count, first question.
Do not feed after a good score. That turns the practice into a reward system and makes a bad score feel like a failed ritual.
If you study at different times, keep the feeding time fixed even when the session moves.
Scores, not hours
Hours studied is an input. Score is an output. Track the score.
At the end date, compare the first three scores with the last three. Improvement is the result; a plateau is also a result.
If the scores are flat, change one variable: the spacing, the question format or the material size. Do not add hours first.
Passive review
The common failure is a session that turns into rereading. If the page is open, the retrieval is not happening.
The second is a deck so large that each review is a tour. Smaller decks, more sessions.
The third is measuring the servitor instead of the learning. The score is the measure; the construction is the schedule.
Checklist
One material, one deck, one notebook.
Twenty minutes, questions closed-book.
Record a score for every session.
Space reviews at 1, 3, 7 and 21 days.
Change one variable when the scores plateau.
Building the question set
A retrieval session needs questions, not pages. Write ten questions per chapter or deck and keep them in one place. The writing is the first retrieval.
Do not reuse the same ten every session. Rotate the order and add new questions as the material grows; otherwise you memorise the sequence, not the content.
The week before the test
Stop adding material. The last week is for retrieval under time pressure: full sets, closed book, timed. Feed the same schedule and record the scores.
If a score drops, do not add hours. Review the specific questions you missed and schedule them sooner.
Notes that support retrieval
Notes written by copying the page support fluency, not recall. Write questions instead: one line per idea, phrased as a question you will answer closed-book.
A page of questions is a deck. A page of highlights is a reread waiting to happen.
Quick rules
- Write questions, not summaries.
- One idea per question.
- Answer closed-book.
- Schedule the questions.
- Retire the ones you always get right.
The day before
The day before a test is not for new material. It is for a final closed-book set and a short review of the questions you missed twice.
Stop early enough to sleep. A tired retrieval session produces a low score that tells you nothing about what you know.
Studying with someone else
A partner can ask the questions while you answer closed-book, which removes the temptation to reread. Agree the questions in advance and keep the session to twenty minutes each way. The servitor holds the schedule; the partner holds the questions.
Using past papers
Past papers are the best question bank you can get, because they match the format of the test. Work them closed-book, timed, and record the score. Then review only the questions you missed and schedule them sooner. A past paper read with the answers open is a reread, not a retrieval session.
FAQ
Can a servitor make me remember?
It can hold the retrieval schedule. Memory comes from the retrieval, not from the construction.
What if I do not have an exam?
Use a skill: a language, an instrument, a programming language. The score is a task completed without notes.
Should I feed it during the exam?
No. Feed before the session. The exam is the test, not the ritual.
How many sessions a week?
Three to five is sustainable. Daily sessions are harder to keep and easier to fake.
Can I use someone else's question bank?
Yes, if it matches your material. The questions are the unit; the source matters less than the fit.
Should I feed during the test week?
Yes, at the same time as always, but not during the exam itself. The feeding is the cue for the session, not a reward for the result.
Should I cram the night before?
No. The last night is for sleep and a short review. Cramming raises familiarity and lowers recall.
How many questions per deck?
Ten to twenty is enough for a twenty-minute session. More than that turns retrieval into a tour and the score stops meaning anything.
How do I know the questions are good?
A good question can be answered in one sentence without the page. If it needs the page, it is a note, not a question.
References
- Carroll, P. J. Psychonaut. 1987.
- Hine, P. Condensed Chaos. 1995.
- Spare, A. O. The Book of Pleasure. 1913.