feynman techniquestudy methodsunderstandingactive recallstudents

The Feynman Technique for Studying: Step-by-Step With Worked Examples

How to use the Feynman Technique to actually understand what you study: four steps, three worked examples (biology, economics, programming), a 20-minute session plan, a gap log, and the mistakes that make it feel useless.

You can read a chapter, nod along, highlight the key terms, and still freeze when a question asks why something happens. That gap between “this looks familiar” and “I can explain it” is exactly what the Feynman Technique is built to expose.

This guide turns the technique into a repeatable study session: the four steps, three worked examples from different subjects, a 20-minute timer plan, a simple gap log, and the mistakes that make people give up on it. Free forever. A blank page and a pen are enough.

If you want the bigger picture of memory-based studying (blurting, question lists, flashcards), start with active recall: how to remember what you study. This article goes deep on one method: explaining a concept in plain words until the weak spots show up.

What the Feynman Technique is (and is not)

The method is named after the physicist Richard Feynman, who was known for explaining difficult ideas in simple language. The study version is straightforward:

  1. Pick one concept.
  2. Explain it in plain words, as if to someone with no background.
  3. Notice where your explanation breaks, gets vague, or leans on jargon.
  4. Go back to the source, fix those gaps, and explain it again more simply.

It is not a memorization tool. Flashcards are better for dates, definitions and vocabulary. The Feynman Technique is for processes, causes, mechanisms and “why” questions: how a reaction works, why a market price changes, what a loop actually does line by line.

It is also not about sounding clever. A good Feynman explanation sounds almost too simple. That is the point.

The four steps in detail

Step 1: Name one concept, narrowly

Write the concept at the top of a blank page. Keep it small enough to explain in a few minutes.

Too broad Right size
Cell biology How osmosis moves water across a membrane
Macroeconomics Why a price ceiling can cause a shortage
Python What a for loop does with a list
World history Why the printing press spread ideas faster

If you cannot explain the topic in roughly half a page, split it.

Step 2: Explain it to a beginner, from memory

Close your notes. Write (or say out loud) an explanation aimed at a curious 12-year-old or a friend from a different major. Rules:

  • No notes open. This is a retrieval attempt, not a copying exercise.
  • Short sentences. One idea per sentence.
  • Use an example. A concrete case beats an abstract definition.
  • Ban unexplained jargon. If you use a technical word, define it in the next sentence.

Speaking out loud works well if writing feels slow. Record a voice memo on your phone and listen back.

Step 3: Mark the gaps

Read your explanation back and mark every spot where:

  • you wrote a term but could not define it,
  • you skipped a step (“and then somehow…”),
  • you used a vague word like “basically,” “affects,” or “stuff,”
  • you could not give an example,
  • you were not sure if a claim was true.

Circle or highlight those spots. These marks are the most valuable output of the whole session. They tell you exactly what to study next, instead of re-reading everything.

Step 4: Go back, fix, and simplify

Now open the textbook, slides or lecture notes, but only for the marked gaps. Fix each one, then rewrite the explanation from the top, shorter and clearer than before. If you can explain it cleanly in fewer words, with an example, you understand it well enough for most exam questions.

Worked example 1: Biology (osmosis)

First attempt (from memory):

Osmosis is when water moves across a membrane because of concentration. Water goes to where there is more concentration. It’s basically diffusion but for water.

Gaps marked:

  • “Because of concentration” — concentration of what? Water or the dissolved stuff?
  • “More concentration” — ambiguous; this is the classic mix-up.
  • “Basically diffusion” — what is different?
  • No example.

After checking the source and rewriting:

A cell membrane lets water through but blocks some dissolved particles, like salt. If there is more salt on one side, water moves toward that side, from where water is more plentiful to where it is less plentiful, until things even out. That movement of water is osmosis. Example: put a slice of cucumber in very salty water and it goes limp, because water leaves the cucumber cells toward the salty side.

Notice what changed: the vague word is gone, the direction is precise, and there is an example you could draw in an exam.

Worked example 2: Economics (price ceiling)

First attempt:

A price ceiling is a maximum price. If it’s below equilibrium it causes a shortage because demand and supply change.

Gaps marked: “Demand and supply change” is wrong in a subtle way. The curves do not shift; the quantities change. No example. No reason why sellers supply less.

Rewrite:

A price ceiling is a legal maximum price. If it is set below the price the market would settle at, more people want to buy at that low price, but sellers are willing to offer less, because each sale earns them less. Buyers want more than sellers provide, so there is a shortage. Example: if rent on apartments is capped well below the market rate, more people look for apartments while fewer new ones are offered, and waiting lists grow.

Worked example 3: Programming (a for loop)

First attempt:

A for loop goes through a list and does something for each item.

That sounds fine, but try explaining what happens to the variable, or what the loop prints. That is usually where the gap is.

Rewrite with a trace:

scores = [70, 85, 90]
total = 0
for s in scores:
    total = total + s
print(total)

The loop takes the first item in scores (70) and calls it s. It adds s to total, so total becomes 70. Then s becomes 85 and total becomes 155. Then s becomes 90 and total becomes 245. There are no items left, so the loop stops and the program prints 245.

For code, a line-by-line trace is the plain-language explanation. If you cannot trace it, you have found your gap. Pair this with the problem set practice workflow for technical subjects.

The 20-minute Feynman session

Minutes Do this
0–2 Write one narrow concept at the top of a blank page
2–8 Explain it from memory to a beginner, with one example
8–10 Mark gaps: jargon, skipped steps, vague words, missing example
10–16 Open sources for marked gaps only and fix them
16–20 Rewrite the explanation from the top, shorter, notes closed

Two or three sessions fit inside a normal study block. If you use the Pomodoro technique, one Feynman session fits neatly inside one 25-minute focus block, with time to spare for the gap log.

Keep a simple gap log

Every marked gap goes into one running list, in a notebook or a single note:

GAP LOG — [Course]
Date | Concept | Gap I found | Fixed? | Re-test date
-----|---------|-------------|--------|-------------
Oct 19 | Osmosis | Mixed up direction of water | Yes | Oct 22
Oct 19 | Price ceiling | Said curves shift | Yes | Oct 22

A few days later, re-explain only the logged concepts from memory. If the gap is gone, cross it off. If it is back, it gets another session. This turns the technique into lightweight spaced repetition without fancy software.

Who to explain to (when no one is around)

  • Blank page: the default. Writing slows you down enough to catch vague words.
  • Voice memo: fast, and hearing yourself stumble is revealing.
  • A study partner: take turns explaining one concept each, and the listener may only ask “why?” or “for example?” See study with roommates focus rules for keeping it on task.
  • An empty chair or a rubber duck: sounds silly, works well. Programmers call this rubber-duck debugging.

If you use an AI chat tool, use it only to check your explanation against your course material, never to write the explanation for you. The learning happens when you generate the words yourself, and your course or school may have rules about AI use, so follow those.

Common mistakes that make it feel useless

Mistake What happens Fix
Topic too big Explanation turns into a vague summary Split into one mechanism or one question
Notes open during Step 2 You copy instead of retrieve, so no gaps appear Close everything first
Skipping the gap marking You feel productive but study nothing new Spend a full two minutes marking
Re-reading the whole chapter in Step 4 Takes forever, loses focus Look up marked gaps only
No example Understanding stays abstract Every explanation needs one concrete case
Doing it once Gaps return before the exam Re-test logged gaps a few days later

When to use it in your week

Feynman session checklist

[ ] One narrow concept written at the top
[ ] Notes closed
[ ] Explained in plain words, short sentences
[ ] At least one concrete example
[ ] Gaps marked (jargon, skipped steps, vague words, unsure claims)
[ ] Sources checked for marked gaps only
[ ] Rewritten from the top, shorter, notes closed
[ ] Gaps copied into the gap log with a re-test date

Start with one concept today

Pick the topic from this week that you would least like to be asked about. Write it at the top of a blank page, close your notes, and explain it to an imaginary beginner. The places where you stall are not failures. They are your study plan for the next 20 minutes.

E-it’s — practical digital productivity & study systems.