Knowledge Modeling Personal productivity method

Feynman Technique

The Feynman Technique makes understanding visible through a simple, precise explanation and closes knowledge gaps deliberately.

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.

Core question

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

Plan Feynman Technique Method guide

Start comparison

Give feedbackIs this method useful to you?

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

Each step produces a concrete domain result for the complete run.

Paper illustration for Feynman Technique.

Concept
Bound topic
Choose one concept, audience, and purpose for the explanation.
Explanation
Write simply
Explain in your own words with an example and intermediate steps.
Gap
Mark sticking points
Mark every place where jargon, omission, or uncertain claim carries the explanation.
Source
Check understanding
Use a primary or reliable technical source to resolve and learn marked gaps.
Simplification
Explain again
Rewrite, test the example, and name remaining uncertainty.

Study each remaining gap, explain again from memory, and test with a new transfer case.

A good fit when

Use it for individual learning, onboarding, and preparing an explanation where real understanding matters.

Ideal for

Individual Learning
Onboarding
Concept Mastery

Not good for

Group decisions
Pure fact recall without a learning goal

Outputs

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

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

First step

Choose a narrow concept and a concrete person you would explain it to.

Open the method guide

Good to do first

Paper illustration of a Concept Map with concepts and labelled links

Knowledge Modeling

Concept Mapping

Supplies the concepts and their relations to be explained.

Where to go next?

Knowledge Modeling

Peer Instruction

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

Knowledge Modeling

Knowledge Mapping

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

Deep dive

Purpose

The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work.

How it works

First, a topic is explained in simple words without hiding behind jargon. As soon as the explanation stumbles, gaps are identified, relearned, and simplified again. This grows a brief explanation into real understanding with robust wording.

In detail

The Feynman Technique works because it tests understanding through explainability, quickly exposing hidden knowledge gaps. It becomes solid when complex content is translated into clear everyday language without losing technical precision. It helps to immediately rework sticking points, skipped intermediate steps, and imprecise terms, so felt understanding turns into robust competence.

Facilitation

Start with a clearly bounded topic and an imagined audience the explanation should truly suit. The important turning point comes with terms that can only be explained using further jargon; that is where the real learning need shows up. In the end there should be an improved short version that can be used directly the next time it is repeated or taught.

The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.

Open method guide

Your perspective

Does this method help with your work?

Your feedback helps shape the next improvements to methodatlas.

Sources and topics

Topics

Learning Knowledge Understanding

Sources

Farnam Street · original teaching examplefs.blogFarnam Street by Shane Parrish; describes the four-step Feynman Technique from capturing knowledge to simplifying it.

In playbooks

Transfer Learning and KnowledgeMove from implicit knowledge to verifiable understanding, repetition, and team learning.

Artifact templates

Feynman Technique: WorksheetPlan the question, inputs, complete run, and review with clear ownership.

markdown

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.