Published August 2, 2026 Last updated August 2, 2026 12 min read

Most study advice focuses on how long or how often you review something. The two methods in this guide focus on something more fundamental: whether you actually understand what you're reviewing, and whether your brain can retrieve it later without the material in front of you. Combined, the Feynman Technique and active recall form one of the most efficient learning systems available for anyone trying to master a technical subject quickly — students, engineers and career changers alike.

The 4 core steps of the Feynman Technique

Physicist Richard Feynman was known for his ability to make complicated ideas sound simple. The technique named after him turns that ability into a repeatable study method built on one core idea: if you can't explain something simply, you don't understand it as well as you think you do.

Step 1: Choose a concept and explain it to a 12-year-old

Pick the exact concept you're trying to learn — a specific algorithm, a specific API pattern, a specific historical event — and explain it out loud or in writing, using only plain language a 12-year-old could follow. No jargon, no assumed background knowledge.

Step 2: Identify the gaps

As you explain, you'll hit points where you either can't continue simply, or where you catch yourself reaching for jargon to paper over something you don't actually understand. Those exact moments are the gaps in your knowledge — and they're far more useful to find now than during an exam or a technical interview.

Step 3: Go back to the source and fill the gaps

Return to your notes, documentation or course material specifically to resolve the gaps you just identified — not to re-read the whole topic from the start. This targeted review is far more efficient than a general re-read, because you're only spending time on what you actually don't understand yet.

Step 4: Simplify and refine your explanation

Rewrite your explanation, removing any remaining jargon and tightening the language. A good test: read it back and ask whether someone with zero background in the topic could follow it without stopping to ask a question.

In plain terms

The Feynman Technique isn't really about teaching other people — it's a diagnostic tool. Trying to explain something simply is the fastest way to find out exactly what you don't understand yet, before that gap costs you on an exam or in a real project.

Combining Feynman with active recall

The Feynman Technique is excellent at revealing gaps in understanding, but on its own it doesn't guarantee you'll remember the concept a week later. Active recall — testing yourself on information from memory instead of passively reviewing it — solves that second problem. Used together, the two methods cover both weaknesses: Feynman builds genuine comprehension, and active recall makes that comprehension stick.

Understanding a concept and remembering it later are two different skills. Most study methods only train one of them.

A simple two-method routine

  1. Learn the concept from your source material as usual
  2. Close the material and explain the concept from memory, using the Feynman method (plain language, no jargon)
  3. A few days later, without reviewing again, try to recall and re-explain the same concept from memory — this is the active recall step
  4. Compare your second explanation to the first. Anything that got fuzzy or was forgotten is exactly what needs another round of review

Why this works: testing yourself before you feel "ready" is uncomfortable, but that discomfort is the signal that real learning is happening. Reviewing material until it feels familiar creates a false sense of mastery that active recall consistently exposes.

For the research behind why this retrieval-based approach beats passive review so consistently, see our full guide on why spaced repetition outperforms re-reading.

Building a Feynman Notebook

A dedicated notebook — physical or digital, in Notion, Obsidian or a plain document — makes this system sustainable instead of something you only do occasionally. Structure each entry the same way, so reviewing later is fast and consistent.

  • Concept name — the specific thing you're learning, stated in one line
  • Plain-language explanation — your current best attempt, written from memory
  • Gaps identified — the specific points where your explanation broke down
  • Resolved explanation — the refined version after filling the gaps
  • Recall date — when you'll test yourself on this again without looking

    • Real-world example: explaining an API in plain terms

    Here's the technique applied to a concept many developers learn but few can explain simply: what an API actually is.

    Jargon-heavy first attempt: "An API is an interface that exposes endpoints allowing client applications to perform CRUD operations against a server's resources over HTTP."

    Feynman-simplified version: "Imagine a restaurant. You (the customer) don't walk into the kitchen to get your food — you tell a waiter what you want, the waiter takes it to the kitchen, and brings back your order. An API is the waiter: it takes a request from one piece of software, passes it to another system that actually does the work, and brings back the result."

    Notice what happened: writing the simplified version forces you to identify what actually matters (a messenger passing requests and responses) versus what's just technical vocabulary (endpoints, CRUD, HTTP) — vocabulary you can now attach to a concept you genuinely understand, instead of memorizing terms in isolation.

    Want to practice this on real algorithms and system design?

    Our AI research and study prompt library includes ready-to-use Feynman-style prompts for testing your understanding.

    Browse the Prompt Library

    Mistakes that quietly weaken this method

    What backfires

    • Explaining a concept silently in your head instead of out loud or in writing
    • Re-reading your notes instead of testing recall without looking
    • Reviewing everything immediately, with no gap before the recall test
    • Treating one Feynman pass as "done" instead of refining the explanation

    What works instead

    • Writing or speaking the explanation, not just thinking it
    • Testing recall days later, without the material in front of you
    • Spacing review sessions instead of cramming them together
    • Refining the explanation each time you find a new gap

    Quick-start checklist

    Start your first Feynman Notebook entry today

    • Pick one specific concept you're currently learning
    • Explain it out loud or in writing, in plain language, right now
    • Circle every point where you got stuck or reached for jargon
    • Go back to the source material only to resolve those specific gaps
    • Set a reminder to recall and re-explain it from memory in 3–4 days

    Frequently asked questions

    A learning method where you explain a concept in plain language, as if teaching it to someone with no background in the subject, to expose exactly which parts you don't actually understand yet.
    A study method where you test yourself on information from memory, rather than re-reading or re-watching material, because retrieving information strengthens memory far more than passively reviewing it.
    The Feynman Technique reveals gaps in understanding, while active recall strengthens memory of what you already understand. Used together, they cover both weaknesses at once — comprehension and retention.
    Two to five minutes for a single concept is usually enough. If you can't explain something clearly in that time, it's a sign the concept needs to be broken down further, not explained at greater length.
    Yes. Both methods are subject-agnostic — they work as well for history, languages and business concepts as they do for algorithms, APIs or system architecture.

    Final thoughts

    Neither method requires special tools or a big time investment — a notebook and a few uninterrupted minutes are enough to start. What makes the combination powerful is what each method catches that the other misses: Feynman exposes what you don't yet understand, and active recall confirms what will actually stay with you. Used consistently, together they turn studying from a passive activity into a system you can trust.

    LearningStudy TechniquesProductivity
    Share this article:
    Written by the Altiora Team
    Curated, reviewed and edited for accuracy before publishing.