Building Your Own Study System

Most people don't have a study system — they have a pile

Ask someone how they study and the honest answer is usually: attend the lecture, keep the slides somewhere, re-read them in a panic before the exam. That's not a system, it's a pile — material goes in and nothing happens to it until the night before, when you try to learn a term's worth of content in one terrified sitting. It half-works, feels awful, and forgets almost everything by summer.

A system is different: it's a pipeline where material reliably moves from encountered to learned without you having to decide, each time, what to do with it. The decisions are made once, up front, and then you just run the loop. That's the whole value — it takes the willpower out of studying, because you're not choosing to study, you're running a system you already built.

LN-01 gave you the two engines that actually build memory — active recall and spaced repetition. This lesson is the machine you bolt them into so they run every week instead of only in the pre-exam panic. Three stages: Capture → Process → Review.

What you'll have at the end

• A three-stage pipeline set up in tools you already have
• A weekly cadence so nothing rots in the pile
• The system running on one real subject, not just designed on paper

Stage 1 — Capture: get it in, don't lose it

Capture is just: material has one reliable home, and it always goes there. Lectures, readings, problem sets, that thing the tutor said would be on the exam — all of it lands in one place per subject, not scattered across a notebook, three apps, some loose PDFs and your memory.

Two rules:

• One inbox per subject. A doc, a notebook, a folder — the tool barely matters (see LN-05's point that the tool is not the skill). What matters is that there's exactly one, and you never wonder where something went.
• Capture is not learning. Copying slides or highlighting is capture, and it creates the illusion of studying while building almost no memory. Don't confuse having the material with knowing it — that confusion is why re-reading feels productive and isn't. Capture fast, then move to Process, which is where learning happens.

Stage 2 — Process: turn material into recall questions

This is the stage everyone skips, and it's the one that does the work. Processing means converting passive material into things you can test yourself on — because testing yourself (active recall) is what builds memory, and you can't test yourself on a wall of slides.

For each chunk of material, make retrieval prompts: questions, flashcards, or blank-page prompts that force you to produce the answer rather than recognise it.

Slide says:   "The mitochondrion is the site of aerobic respiration,
               producing ATP via the electron transport chain."
Process into: Q: Where does aerobic respiration happen, and what does
                 it produce?
              Q: What's the role of the electron transport chain?
              Q: (harder) Why can't this happen without oxygen?

• Questions over highlights. A highlight says "this was important"; a question makes you retrieve it. Only the second builds memory.
• Do it soon after capture, while it still makes sense — the gap between capturing and processing is where material goes stale.
• The Feynman move for anything you can't turn into a clean question: you don't understand it well enough yet, which is itself the signal to go re-learn that bit (full method: LN-09).

Processing is slower than highlighting. That slowness is the learning — it's the "desirable difficulty" from LN-01.

Stage 3 — Review: spaced recall, on a schedule

Now the retrieval prompts from Stage 2 go into a spaced review schedule (LN-01): you test yourself on them at expanding intervals, so each item comes back just as you're about to forget it. This is where the memory actually consolidates — capture and process prepare the material, review learns it.

• Review = attempt from memory first, then check. Reading the answer isn't review; struggling to produce it is.
• Failed items come back sooner; nailed items go to a longer interval. A flashcard app does this automatically; a paper system does it with dated piles or a simple "revisit on" column.
• Little and often beats a lot rarely. Fifteen minutes of spaced recall four times a week crushes four hours the night before — same total time, wildly different retention.

The weekly cadence — the glue

A pipeline only works if it runs on a rhythm. Add one recurring block that keeps the system alive (this is exactly what the calendar/task system in TL-07 is for):

AFTER EACH CLASS (5 min):  capture lands in the subject inbox
TWICE A WEEK (30–45 min):  process new material into recall questions
MOST DAYS (15 min):        spaced review of due questions
SUNDAY (20 min):           weekly review — what's behind, what's the
                           exam-relevant priority, tidy the inbox

The Sunday review is the load-bearing habit: it's the moment you catch material rotting in the pile before it becomes a pre-exam emergency. Miss everything else and keep this, and you still have a system.

What this means for you

• A pile isn't a system. Decide the pipeline once, then run it — that's what removes the willpower cost.
• Capture ≠ learning. Highlighting and copying feel productive and build almost no memory.
• Processing into recall questions is the real work — and the step everyone skips.
• Review is retrieval from memory, spaced — that's where it sticks (LN-01).
• A weekly cadence is the glue; the Sunday review catches problems while they're small.
• The tool doesn't matter; the loop does. Use what you already have.

Exercise (45 min, verifiable output)

1. Pick one real subject you're studying now.
2. Set up the one inbox for it (a doc/folder/notebook) — capture this week's material into it.
3. Process one chunk: turn one lecture or reading into 8–10 recall questions (not highlights).
4. Do one review session: attempt those questions from memory, mark which you missed, schedule the missed ones sooner.
5. Block the weekly cadence in your calendar/task system (TL-07): the after-class capture, the twice-weekly process, the daily review, the Sunday review.

✅ Finish check: one subject with an inbox, one chunk processed into recall questions, one review session done from memory, and the weekly cadence scheduled — a system that's actually running, not just drawn.

Summary card

• Replace the pile with a pipeline: Capture → Process → Review.
• Capture: one inbox per subject; capturing isn't learning.
• Process: convert material into recall questions, not highlights — the step that does the work.
• Review: spaced retrieval from memory (LN-01); little and often beats cramming.
• Weekly cadence is the glue; the Sunday review catches rot early.
• The tool is irrelevant; the loop is everything. Decide once, then just run it.

Sources

1. Roediger, H. & Karpicke, J. — Test-Enhanced Learning, 2006
2. Allen, D. — Getting Things Done, 2001
3. Dunlosky, J. et al. — Improving Students' Learning With Effective Techniques, 2013

Next lesson: LN-03 — Exam Strategy: Time, Question Selection, Guessing (L2) Related: LN-01 Active Recall and Spaced Repetition · LN-06 Reading Technical Material · LN-09 Teaching to Learn · TL-07 Calendar and Task System Path: related — the backbone most study runs on