methodatlas
Method guideKnowledge Modeling

Feynman Technique

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityLow
Time20-60 min
Participants1
FormatAsync
MaturityEstablished
Plan Feynman Technique
01

Prerequisite

What needs to be finished first

Complete firstExplanation

Name one concept and the intended listener. Close the source before producing the first explanation from memory.

Choose one concept and one explanation purpose.
Complete firstCheck

Create four areas: plain explanation, example, marked gaps, and revised version. Introduce technical terms only after a plain explanation.

Introduce the term after mechanism and example.
02

Preparation

What needs to be ready before start

Materials

Blank sheet or document, original source, pen, optional recorder, and one transfer example.

People / roles

Learner as explainer · optional non-expert test listener · reliable source for gap checks

Pre-read

Name one concept and the intended listener. Close the source before producing the first explanation from memory.

Time needed

20–60 minutes per clearly bounded concept; use several loops for large subjects.

Setup

Create four areas: plain explanation, example, marked gaps, and revised version. Introduce technical terms only after a plain explanation.

03

Core question

The one question this method answers

Can I explain this concept without skipping a step or hiding behind jargon?

04

Flow

Phases with goal, actions, output and pitfall

The Feynman Technique asks one person to explain a bounded concept in their own everyday language. Sticking points are marked, checked against sources, and used to improve the explanation.

Feynman learning sheet

Fictional example

Fictional explanation of HTTP caching for a new colleague.

Concept and listener

What exactly are you explaining, to whom, and for what purpose?

HTTP caching for a new frontend colleague so she can diagnose stale responses.

Explanation in own words

How does it work without unexplained jargon?

A cache keeps an earlier response. Before reusing it, the browser checks rules supplied by the server.

Gap

Where does the explanation jump or rely on an unexplained term?

Open: when must the browser ask the server again even though it has a copy?

Targeted source correction

Which source closes exactly this gap?

Check MDN on Cache-Control; restate max-age and revalidation in plain language.

Test and transfer

Which new situation must the explanation predict?

Why can a response after max-age be refreshed with 304 rather than a full payload?

The explanation is deliberately short and is not a complete HTTP specification.

Farnam Street · original teaching example

  1. 1

    Concept

    Bound topic

    Goal

    Bounded learning target: Choose one concept, audience, and purpose for the explanation.

    Inputs for this step

    • Name one concept and the intended listener. Close the source before producing the first explanation from memory.

    Actions

    • Choose one concept, audience, and purpose for the explanation.

    Output

    Bounded learning target

    Bounded learning target

    Quality check

    Is the concept small enough to explain fully with one example?

    Pitfall

    The subject is Machine Learning and too broad for a testable explanation. Return to “Bound topic” and repeat this method step: Choose one concept, audience, and purpose for the explanation.

    Timing: 3–5 minutes

  2. 2

    Explanation

    Write simply

    Goal

    First explanation in own words: Explain in your own words with an example and intermediate steps.

    Inputs for this step

    • Bounded learning target

    Actions

    • Explain in your own words with an example and intermediate steps.

    Output

    First explanation in own words

    First explanation in own words

    Quality check

    Does the text explain mechanism and relationship rather than list definitions?

    Pitfall

    The text copies definitions or replaces explanation with technical terms. Return to “Write simply” and repeat this method step: Explain in your own words with an example and intermediate steps.

    Timing: 8–15 minutes

  3. 3

    Gap

    Mark sticking points

    Goal

    Marked understanding gaps: Mark every place where jargon, omission, or uncertain claim carries the explanation.

    Inputs for this step

    • First explanation in own words

    Actions

    • Mark every place where jargon, omission, or uncertain claim carries the explanation.

    Output

    Marked understanding gaps

    Marked understanding gaps

    Quality check

    Are jumps, jargon, and uncertain claims explicitly marked?

    Pitfall

    Hesitation is polished away instead of marked as a knowledge gap. Return to “Mark sticking points” and repeat this method step: Mark every place where jargon, omission, or uncertain claim carries the explanation.

    Timing: 5–10 minutes

  4. 4

    Source

    Check understanding

    Goal

    Source-checked corrections: Use a primary or reliable technical source to resolve and learn marked gaps.

    Inputs for this step

    • Marked understanding gaps

    Actions

    • Use a primary or reliable technical source to resolve and learn marked gaps.

    Output

    Source-checked corrections

    Source-checked corrections

    Quality check

    Does the source answer the exact marked gap, with the correction restated in the learner's own words?

    Pitfall

    The entire source is reread without resolving the specific gap. Return to “Check understanding” and repeat this method step: Use a primary or reliable technical source to resolve and learn marked gaps.

    Timing: 5–20 minutes

  5. 5

    Simplification

    Explain again

    Goal

    Simplified, tested explanation: Rewrite, test the example, and name remaining uncertainty.

    Inputs for this step

    • Source-checked corrections

    Actions

    • Rewrite, test the example, and name remaining uncertainty.

    Output

    Simplified, tested explanation

    Simplified, tested explanation

    Quality check

    Can a test listener follow the example and correctly predict a new case?

    Pitfall

    The version sounds simple but is tested with neither a listener nor a transfer case. Return to “Explain again” and repeat this method step: Rewrite, test the example, and name remaining uncertainty.

    Timing: 5–10 minutes

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

Feynman Technique · Learning through ExplanationExplain a concept simply, mark understanding gaps, check sources, and simplify the explanation
Feynman TechniqueThe visual shows a concept, a simple explanation, marked gaps, targeted source work, and a simplified explanation as a learning loop.Test understanding by explaining it simplyThe explanation itself becomes the test: where it stalls, learning and simplification become targeted.explainmarkclosesimplifyConceptWhat do I really want tounderstand?Explanation in simple wordsIf I cannot say it simply, understanding ismissing.Example instead of term chain.Gapsstumbling, jargon, unclear causeCheck sourceslook up precisely, do not collect anewSimplified explanationshort, concrete, without fog
Form

Versioned explanation in the learner's own words with example, marked knowledge gaps, source corrections, and transfer question.

Versioning / ownership

Version the simplified, tested explanation with date, owner, source state, and review date. Preserve earlier observations and append changes with their reason.

Tool alternatives
  • Blank sheet or document for explanation, gaps, and revision
  • Primary or reliable specialist source for targeted gap checks
  • Test listener or transfer question to check the explanation

feynman-technique-working-template.md

Plan the question, inputs, complete run, and review with clear ownership.

Feynman Technique: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Complete run Time: 20–60 minutes per clearly bounded concept; use several loops for large subjects.

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: Blank sheet or document, original source, pen, optional recorder, and one transfer example.
  • Roles: Learner as explainer · optional non-expert test listener · reliable source for gap checks
  • Advance information: Name one concept and the intended listener. Close the source before producing the first explanation from memory.
  • Overall time needed: 20–60 minutes per clearly bounded concept; use several loops for large subjects.
  • Setup: Create four areas: plain explanation, example, marked gaps, and revised version. Introduce technical terms only after a plain explanation.

Prepare for the work steps

Concept: Bound topic

  • Name one concept and the intended listener. Close the source before producing the first explanation from memory.

Explanation: Write simply

  • Bounded learning target

Gap: Mark sticking points

  • First explanation in own words

Source: Check understanding

  • Marked understanding gaps

Simplification: Explain again

  • Source-checked corrections

Feynman learning sheet

Concept and listener

What exactly are you explaining, to whom, and for what purpose?

...

Explanation in own words

How does it work without unexplained jargon?

...

Gap

Where does the explanation jump or rely on an unexplained term?

...

Targeted source correction

Which source closes exactly this gap?

...

Test and transfer

Which new situation must the explanation predict?

...

Close the source for the first explanation; inspect gaps afterwards.

Farnam Street · original teaching example

Concept: Bound topic

Expected artifact: Bounded learning target

Bounded learning target

Entry:

...

  • Is the concept small enough to explain fully with one example?

Explanation: Write simply

Expected artifact: First explanation in own words

First explanation in own words

Entry:

...

  • Does the text explain mechanism and relationship rather than list definitions?

Gap: Mark sticking points

Expected artifact: Marked understanding gaps

Marked understanding gaps

Entry:

...

  • Are jumps, jargon, and uncertain claims explicitly marked?

Source: Check understanding

Expected artifact: Source-checked corrections

Source-checked corrections

Entry:

...

  • Does the source answer the exact marked gap, with the correction restated in the learner's own words?

Simplification: Explain again

Expected artifact: Simplified, tested explanation

Simplified, tested explanation

Entry:

...

  • Can a test listener follow the example and correctly predict a new case?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/feynman-technique/run-sheet

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

feynman-technique-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: Feynman learning sheet

Concept and listener

HTTP caching for a new frontend colleague so she can diagnose stale responses.

Explanation in own words

A cache keeps an earlier response. Before reusing it, the browser checks rules supplied by the server.

Gap

Open: when must the browser ask the server again even though it has a copy?

Targeted source correction

Check MDN on Cache-Control; restate max-age and revalidation in plain language.

Test and transfer

Why can a response after max-age be refreshed with 304 rather than a full payload?

The explanation is deliberately short and is not a complete HTTP specification.

07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. Bound topicThe subject is Machine Learning and too broad for a testable explanation.View in phase
  2. Write simplyThe text copies definitions or replaces explanation with technical terms.View in phase
  3. Mark sticking pointsHesitation is polished away instead of marked as a knowledge gap.View in phase
  4. Check understandingThe entire source is reread without resolving the specific gap.View in phase
  5. Explain againThe version sounds simple but is tested with neither a listener nor a transfer case.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Pause or return to the previous step when this check is not satisfied: Is the concept small enough to explain fully with one example?
Pause or return to the previous step when this check is not satisfied: Does the text explain mechanism and relationship rather than list definitions?
Pause or return to the previous step when this check is not satisfied: Are jumps, jargon, and uncertain claims explicitly marked?
Pause or return to the previous step when this check is not satisfied: Does the source answer the exact marked gap, with the correction restated in the learner's own words?
Pause or return to the previous step when this check is not satisfied: Can a test listener follow the example and correctly predict a new case?

Method after Richard Feynman. Curated with 1 sources.

Sources: Farnam Street · original teaching example

Flow, timeboxes, and pitfalls are editorially curated practice recommendations based on the listed sources.

Where to go next?

Paper illustration for Peer Instruction.
Knowledge Modeling
Peer Instruction

Tests the simplified explanation with a concept question in the group.

Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping

Plans transfer of the now-clear explanation to other knowledge holders.

View in playbookTransfer Learning and KnowledgeMove from implicit knowledge to verifiable understanding, repetition, and team learning.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profileMore methods