Learning Memory Productivity
Stop Memorizing, Start Understanding: The Pre-Processing Secret Top Learners Use
Why your flashcards keep failing you — and what Justin Sung says to do instead
You have studied. You have reviewed. You built a flashcard deck that would make a librarian weep with admiration. And then the exam arrived — or the meeting, or the real-world moment — and the information simply was not there.
It is a frustrating experience that most serious learners have had. For years, the conventional wisdom blamed the storage system: use better mnemonics, space your repetitions more carefully, try the memory palace. All of that advice aims at the same thing — getting information in and making sure it stays.
Justin Sung, a former medical doctor turned learning coach, argues that this framing gets the problem almost entirely backwards.
"The problem isn't usually the storage system — it's what gets fed into it."
In other words: most learners encode shallow, surface-level understanding, then wonder why retrieval breaks down under pressure. The fix is not a better storage method. The fix happens before storage even begins.
What is pre-processing?
Pre-processing, as Sung uses the term, is the mental work that happens before you try to commit anything to memory. It means building a framework that maps the structure and relationships of a topic — understanding how the pieces connect, why they matter, and what role each plays in the larger picture.
Think of it as drawing a map before you start driving. Without a map, every intersection looks the same. With one, every turn makes sense because it is part of a route you already understand.
Without pre-processing, you store isolated facts. With it, you store a web of interconnected meanings. This distinction matters enormously for one reason: retrieval is path-dependent. The brain does not look up information the way a search engine does. It follows chains of association. If a concept is connected to many other things you know, there are many paths back to it. If it is stored as a lone fact, you have to hope you enter through exactly the right door — and under pressure, that door is often locked.
Shallow encoding vs. deep encoding: a comparison
The difference between shallow and deep encoding comes down to what actually gets stored — and how many ways your brain can find its way back to it.
A concrete example: learning the cardiovascular system
Consider a medical student preparing an exam on how the heart regulates blood pressure.
The student makes flashcards: "What does the baroreceptor reflex do?" Answer: "It detects changes in blood pressure and sends signals to the brain to adjust heart rate and vessel tone." They drill this until it feels automatic.
On exam day, when the question is framed differently — "Why does a patient standing up quickly sometimes feel faint?" — the student draws a blank. The stored answer is tied to the exact question shape they practised.
Before any flashcards, the student maps the system: Blood pressure drops → baroreceptors in the carotid sinus detect the drop → they signal the medulla → the medulla increases sympathetic output → heart rate rises, vessels constrict → pressure is restored. They understand this as a feedback loop — the same kind that controls a thermostat.
Now the orthostatic hypotension question is easy: blood pools in the legs when you stand, pressure drops, the reflex kicks in. If the reflex is sluggish (dehydration, medication, age), you feel faint. The student did not memorise that answer. They derived it.
The second student is not smarter. They pre-processed. They stored a structure, not a sentence.
The five pre-processing questions
Before studying any new material, run through these five questions. They are designed to force your brain to do structural work before it starts encoding specifics.
What is the big picture?
What is this topic fundamentally about? What problem is it solving, or what phenomenon is it describing? State it in one sentence without jargon.
What are the major categories?
How does the subject naturally divide? Are there types, stages, causes, components, or phases? Sketch these as branches before reading in detail.
How do the parts relate to each other?
Does A cause B? Does B regulate A? Do C and D work in parallel or in sequence? Relationships are the architecture; the facts are just the furniture.
Where does this fit with what I already know?
What existing concept does this most resemble? The immune system is a surveillance and response network — like a security team. Enzyme kinetics follows the logic of supply and demand. Analogies are not dumbing things down; they are building bridges.
What would break it?
What happens when this system fails or this rule is violated? Edge cases and exceptions reveal structure better than the normal case does.
How to build a pre-processing framework: a walkthrough
Here is the full process applied to a non-technical topic: understanding inflation.
Step 1 — State the core in plain language
Inflation is when the purchasing power of money falls over time. More money chases the same goods, so prices rise.
Step 2 — Sketch the major categories before reading
Demand-pull
Too much money chasing too few goods. The economy is running hot.
Cost-push
Production gets more expensive (oil, wages) — sellers pass costs on.
Built-in
Workers expect prices to rise, demand higher wages, which raises prices further.
Step 3 — Map the cause-and-effect chains
Central bank prints money → more money in circulation → consumers spend more → demand rises faster than supply → prices rise → workers demand higher wages → businesses raise prices further (feedback loop). Central bank raises rates → borrowing becomes expensive → spending slows → demand falls → price growth slows.
Step 4 — Anchor to something familiar
Inflation works like a game where you suddenly give every player double the chips without adding anything to buy. The game does not get richer — the chips just become worth less each.
Step 5 — Identify what would break it
What if prices rise but wages do not? You get a cost-of-living crisis. What if the central bank raises rates too aggressively? You tip into recession. Edge cases reveal the system's pressure points — and they are almost always the questions your teacher will ask.
Pre-processing vs. traditional study methods
| Method | What it does well | What pre-processing adds |
|---|---|---|
| Flashcards / spaced repetition | Maintains access to already-encoded information | Ensures what you encode is worth retaining |
| Re-reading / highlighting | Familiarity with the text's surface | Replaces passive exposure with active structuring |
| Practice testing | Identifies gaps in what can be retrieved | Reduces gaps by building richer initial encoding |
| Mind mapping (generic) | Visual organisation of notes | Adds deliberate relationship-mapping before content exposure |
Pre-processing does not replace any of these methods — it upgrades the input they work with. Spaced repetition on deeply understood material is far more efficient than spaced repetition on surface definitions.
Common mistakes when trying this for the first time
The takeaway
Justin Sung's insight is not that memory is unimportant. It is that the quality of what you feed memory determines everything that follows. The most sophisticated storage system in the world cannot make isolated facts reliably retrievable under real conditions.
Pre-processing transforms information from a list of things to memorise into a structure that can be reasoned with, extended, and retrieved from any angle. It takes longer upfront. It pays back many times over.
The next time you sit down to study, before you open a flashcard app or pick up a highlighter, spend fifteen minutes on the five questions. Map the structure. Build the framework. Then let your memory system do what it was actually designed to do — store something worth keeping.
Found this useful? Share it with someone who is grinding through flashcards and wondering why nothing is sticking.
