The Feynman Technique for Note-Taking

The Feynman Technique for note-taking is the practice of writing an explanation in plain language, in your own words, until you reach the sentence you cannot finish — and then going back to the source to close the gap on the same page. The note is the explanation. The gap is the lesson. Everything else is rehearsal.

The technique takes its name from the Caltech physicist Richard Feynman, though the four-step formulation circulating online was popularised by Scott H. Young in 2011 ¹ and Farnam Street's Shane Parrish in the years after ². Feynman himself left two clearer artifacts. The first was a Princeton-era notebook he opened with the words "NOTEBOOK OF THINGS I DON'T KNOW ABOUT" ³. The second was a famous remark his Caltech colleague David Goodstein recorded: "I couldn't do it. I couldn't reduce it to the freshman level. That means we don't really understand it." ⁴ Both behaviours describe the same habit. Both are a recipe for a notebook.

What the Feynman Technique actually is

The Feynman Technique is a four-step loop: write the concept at the top of a blank page; explain it in plain language as if to a twelve-year-old; mark every sentence you stumble on as a gap and return to the source; then simplify and store the result ². The work happens in step three. The note is the by-product.

Most other learning systems describe what to file; this one describes what to write.

The technique is older than its current packaging. James Gleick's Genius: The Life and Science of Richard Feynman (Pantheon, 1992) describes the Princeton-era notebook in detail. As a graduate student preparing for his oral exams, Feynman "opened a fresh notebook. On the title page he wrote: NOTEBOOK OF THINGS I DON'T KNOW ABOUT. For the first but not last time he reorganized his knowledge. He worked for weeks at disassembling each branch of physics, oiling the parts, and putting them back together, looking all the while for the raw edges and inconsistencies." ^{3 5} That is the technique, named correctly: an inventory of ignorance, kept in writing.

Scott H. Young — the writer who completed MIT's four-year computer science curriculum in twelve months — published "Learn Faster with the Feynman Technique" on 1 September 2011, the earliest widely-read use of the name we can trace ¹. Farnam Street followed on 26 April 2012 with the essay that carried the method to a general audience ². Cal Newport, in a 2015 essay, named the underlying practice "the Feynman Notebook Method" and pointed at the same Gleick passage as proof that Feynman lived the habit, not just the soundbite ⁶. The packaging is recent. The behaviour is some seventy years older than the packaging.

The misattribution is worth flagging. The aphorism "if you can't explain it simply, you don't understand it well enough" is widely credited to Feynman or to Einstein, and has never been traced to either — no source places it in the mouth of either man ⁷. What Feynman actually said is the harder, sharper version. Goodstein had asked him to explain why spin one-half particles obey Fermi-Dirac statistics; it was Feynman who proposed the test, answering "I'll prepare a freshman lecture on it." He came back days later: "I couldn't do it. I couldn't reduce it to the freshman level. That means we don't really understand it." ⁴ Note what the standard is. Feynman's freshman was a Caltech freshman, not a stand-in for anyone at all — the claim is not that every idea can be made simple, but that the attempt is the diagnostic. The technique borrowed his name because the test he ran on himself is the test the technique runs on you.

Why writing-as-explanation works

Writing-as-explanation works because it forces retrieval, generation, and self-testing in a single act — the three operations cognitive psychology has identified as the highest-leverage moves in long-term learning. A page of explanation is not a record of what you read. It is a measurement of what you actually understood, taken in the same five minutes as the encoding ⁸.

The cleanest piece of evidence is Jeffrey Karpicke and Henry Roediger's 2008 study in Science. Students learned forty Swahili-English vocabulary pairs, and once a pair had been recalled correctly it was either kept in the repeated testing rounds or dropped from them. A week later, the conditions that kept retrieving the pairs recalled about 80% of them; the conditions that dropped them from testing and merely kept restudying them recalled just 36% ⁹. Every student had studied every pair — the forty-four-point gap turned on whether the recall itself was rehearsed, which is why the authors concluded that "testing (and not studying) is the critical factor for promoting long-term recall" ¹⁰. Writing your own explanation is retrieval practice for ideas instead of for words.

The second mechanism is the generation effect. Norman Slamecka and Peter Graf described it in a 1978 paper that ran five experiments. They found that "performance in the generate condition was superior to that in the read condition" across "cued and uncued recognition, free and cued recall, and confidence ratings." ¹¹ Generating an explanation forces an idea to encode against an existing scaffold instead of into empty space. Robert and Elizabeth Bjork's UCLA lab calls the broader category "desirable difficulties" — practices that feel harder during study and produce dramatically better long-term retention ¹². Writing in your own words is the cheapest desirable difficulty in the catalogue.

The third reason is that writing surfaces ignorance you cannot otherwise see. Shane Parrish, paraphrasing the broader cognitive-science consensus, has written that "writing is the process by which you realize that you do not understand what you are talking about." ¹³ Larry McEnerney, who ran the University of Chicago's writing programme for nearly four decades, makes the inverse point in his lecture The Craft of Writing Effectively: experts struggle to write to other experts because clear writing exposes the seams in expertise ¹⁴. The Feynman Technique exploits exactly that exposure. The page is a stress test.

The five-minute version

The five-minute Feynman note is the smallest version of the technique. Open a blank page. Write the concept name at the top. Set a timer for five minutes. Explain it in your own language as if to a curious teenager. When the timer rings, underline every sentence that felt forced. Those underlines are the next session.

The full procedure, on a single page:

1. Title. Write the concept on line one. One noun phrase, no qualifiers.
2. Plain explanation. In sentences a twelve-year-old could read, write what the concept is and what it does. Use no specialised vocabulary unless you can define it inline.
3. Example. One concrete instance, drawn from your own experience or work.
4. Friction marks. Underline every sentence where you slowed, hedged, or borrowed someone else's words.
5. Gaps list. Beneath the explanation, list the questions raised by the underlines. One per line. No answers yet.
6. Source pass. Open the source. Read only the parts that close the listed gaps.
7. Re-write. On a fresh page, write the explanation again — only after the gaps are closed.

Five minutes is all the system needs to start producing signal. Andy Matuschak says it cleaner than most: "Evergreen notes are written and organized to evolve, contribute, and accumulate over time, across projects." ¹⁵ The Feynman note is an evergreen note caught in the moment of formation.

The thirty-minute version

The thirty-minute Feynman note is the version you run when a concept is difficult and the five-minute pass surfaces more gaps than answers. The shape is identical; the depth is different. Block thirty minutes. Run the seven steps. Then run them again. Concepts that resist both passes belong on a separate "things I do not yet understand" list ³.

The deeper version borrows two extra moves from Kalid Azad's BetterExplained tradition, itself a structured version of the Feynman Technique applied to mathematics. Azad's ADEPT method runs an idea through Analogy, Diagram, Example, Plain English, and only then Technical detail ¹⁶. After your second plain-English explanation, sketch a diagram in the margin and write one analogy. If the analogy collapses, that is the next gap. If the diagram needs no labels, the concept has become yours.

A second move borrows from Sönke Ahrens' How to Take Smart Notes (2017). Every Feynman note, once it has settled, becomes a literature note attached to its source, and at least one permanent, atomic note attached to no source at all ¹⁷. Ahrens' rule reads: "Writing is not what follows research, learning or studying, it is the medium of all this work." ¹⁷ The thirty-minute Feynman note is that medium running at full power. Five minutes is for momentum. Thirty minutes is for understanding.

A worked example. Suppose the concept is spaced repetition. The five-minute pass produces a paragraph that says, roughly, "you review things at intervals that get longer." The friction marks land on "intervals," "review," and "longer." The gaps list is three lines: How long are the intervals? What counts as review? What is the underlying mechanism? The source pass closes the three gaps. The reader returns to Piotr Woźniak's SuperMemo essay, or to Andy Matuschak and Michael Nielsen's Quantum Country primer ¹⁸. The re-write produces a paragraph that names the SM-2 algorithm, names the testing effect as the mechanism, and uses an example from the writer's own week. That paragraph, transferred to a permanent note titled "Spaced repetition," joins the network. The source paragraph, attached to the original, becomes the literature note. Two notes. Thirty minutes. One concept genuinely understood.

How to use it on a textbook chapter

A textbook chapter is the canonical case for the Feynman Technique: it introduces defined terms faster than you can absorb them, and its authority invites you to nod along. Read the chapter with a pencil, marking only headings and worked examples. Close the book. Write one Feynman note for the chapter, then one per heading.

Feynman himself supplied the negative example. In Surely You're Joking, Mr. Feynman! (W. W. Norton, 1985), the chapter "O Americano, Outra Vez!" describes his time teaching at the University of Brazil in the early 1950s ¹⁹. He found students who could quote textbooks verbatim and who could not, on being asked a question outside the textbook's wording, recognise that the answer was on the previous page. His end-of-year public lecture delivered one of pedagogy's harshest lines: "The main purpose of my talk is to demonstrate to you that no science is being taught in Brazil!" ²⁰ The students were not failing. The system was rehearsing the act of memorising while skipping the act of understanding. Highlighting a textbook without writing about it is the same failure on a smaller stage.

The cleanest contemporary expression of the same idea is Mortimer Adler's "syntopical" reading from How to Read a Book (Touchstone, revised 1972) ²¹. Adler distinguishes elementary, inspectional, analytical, and syntopical reading. The analytical level is the level at which you can state the author's argument in your own words and identify where it fails. That is the level a Feynman note operationalises. The note is the artefact analytical reading produces. Without the note, the level above inspection has not been reached.

A note on writing by hand. Pam Mueller and Daniel Oppenheimer's 2014 paper The Pen Is Mightier Than the Keyboard reported across three studies that students who took notes on laptops "performed worse on conceptual questions" than students who took notes longhand ²². Their interpretation: typists transcribe verbatim; longhand writers must summarise in their own language. That second half has held up better than the first. Heather Urry's 2021 direct replication of the paper's Study 1 — 88 authors, preregistered — again found that laptop note-takers wrote more words and more verbatim overlap, but this time they did not score worse on the quiz; the authors concluded that "results do not support the idea that longhand note taking improves immediate learning via better encoding of information." ²³ What survives replication is the mechanism, not the pen: verbatim capture predicts worse understanding regardless of the surface it happens on. This is the same line we draw in Active Note-Taking Is Thinking, Not Transcribing — the choosing is the work, and a transcript does the choosing for you. The Feynman Technique mandates the summarising half directly. The medium matters less than the rule that the words on the page must be yours.

Common mistakes

Most people fail the Feynman Technique in the same five places. Each mistake has a specific repair. The mistakes are quiet — they look like the technique is working when it is not — which is why naming them matters more than naming the steps.

• Smuggling jargon. The whole technique collapses if "force" defines "mass" without first defining "force" in plain English. Repair: a vocabulary you cannot translate into a teenager's sentences is a vocabulary you have not understood yet. Translate or excise.
• Skipping the underlines. The friction marks are the system. Without them, the page becomes a summary. Summary is the low-utility technique that John Dunlosky and colleagues' 2013 review in Psychological Science in the Public Interest placed near the bottom of their ten-technique ranking ⁸. Repair: underline as you write, not after.
• Doing it on something you already know. Zach Highley, a medical-school blogger whose critique of the technique circulates widely in study-method circles, writes: "I use it for critical general topics to establish a basis of understanding." He draws the line in the same passage: "I've used the Feynman technique to describe obstructive vs. restrictive lung disease, but I did not use it to remember the histopathology of various lung diseases." ²⁴ Repair: reserve the technique for the small set of concepts that anchor a domain. Use flashcards for the long tail.
• Treating it as a one-shot. A single Feynman note is a snapshot. The compounding only happens when notes link to other notes and when explanations are re-written months later. Andy Matuschak's evergreen-notes pattern — atomic, concept-oriented, densely linked ¹⁵ — is the long-game version of what the Feynman Technique runs in five minutes.
• Skipping the diagram. Kalid Azad's ADEPT order puts the diagram before the technical detail for a reason: a diagram you cannot draw is a relationship you have not understood ¹⁶. Repair: every Feynman note for a concept involving more than two moving parts gets a margin sketch.

How this works in MNMNOTE

A Feynman note runs on whatever notebook is closest to your hand. MNMNOTE is a browser-based markdown editor. Open a tab, type the concept name as the title, write the plain explanation in your own words, link [[gaps]] and [[source]] notes with wiki-links, and come back to the page tomorrow ¹⁵.

Notes stay on your own device, and the editor works offline. There is no account, no install, no upload — and the file format is plain markdown, readable by every other tool on the day MNMNOTE is no longer around. The point of the notebook is to disappear behind the writing.

Frequently Asked Questions

Eight questions cover the cases that come up most often in practice: attribution, time budget, comparison with adjacent systems, medium choice, AI use, transfer to non-technical domains, throughput, and the single most common failure mode. Each answer below stands alone and points to its primary source.

Did Richard Feynman actually invent the Feynman Technique?

Not in the four-step packaging that circulates today. The label was popularised by Scott H. Young's 2011 course and Farnam Street's 2012 essay ^{1 2}. What Feynman did was practise the underlying habit, recorded in Gleick's biography as the "NOTEBOOK OF THINGS I DON'T KNOW ABOUT" — writing down what he could not yet explain, then closing each gap ³.

How long should a Feynman note take?

Five minutes for the first pass; thirty minutes for a difficult concept that resists it; an hour at most before you split the topic into two notes. Anything longer is a sign that the concept is not yet atomic. Matuschak's principle: if the explanation does not fit on a page, it is two ideas pretending to be one ¹⁵.

Is this the same as Cornell notes or Zettelkasten?

No, but they cooperate. Cornell notes are a layout for capturing during a lecture; Zettelkasten is a long-term filing system for atomic notes. The Feynman Technique sits between — the act of writing the explanation turns a Cornell capture into a Zettelkasten-worthy note. Sönke Ahrens' How to Take Smart Notes describes the same workflow under different names ¹⁷.

Does writing by hand work better than typing?

The honest answer is mixed. Mueller and Oppenheimer's 2014 study found conceptual-recall advantages for longhand, attributed to typists transcribing verbatim while longhand writers must summarise ²². Urry's 88-author direct replication in 2021 did not find that immediate-learning gap, though it did reproduce the finding that laptops produce more words and more verbatim overlap ²³. The actionable rule is active synthesis, not handwriting as such — which is exactly what the Feynman Technique enforces regardless of medium. Use whichever medium you will actually use daily.

Can I use AI to write my Feynman explanations?

No. The technique fails the moment the words on the page are not yours. The generation effect collapses to zero if a model writes the explanation ¹¹. Use AI for the inspectional pass — checking whether a concept is worth a full session — but the explanation must be human. A model writing for you is ignorance not surfaced ¹³.

How does this work for fiction or arts subjects?

The technique transfers with one change: the "concept" at the top of the page is a single claim — "Joan Didion uses present-tense italics to mark trance states" — rather than a defined term. The plain-explanation step forces the same exposure. Either the claim is defensible from the text, or the friction marks name the paragraph you cannot quite remember.

How many concepts can I run this on per week?

Three to five notes per week is sustainable; ten is unsustainable for almost everyone. The constraint is not the writing but the source-pass step. Even three notes a week compounds: in a year, that is roughly a hundred and fifty atomic explanations in your own language. Niklas Luhmann's slip-box reached roughly ninety thousand cards across a working lifetime, and carried fifty books out with it ²⁵.

What is the single biggest reason this technique fails?

Skipping the friction marks. Most people write a clean paragraph, feel virtuous, and close the notebook. The paragraph is the practice; the underlines are the learning. Without them, the technique reduces to ordinary summarisation — which Dunlosky and colleagues' 2013 review rated low-utility because no self-testing is involved ⁸. The pen marks places the highlighter cannot.

Closing

Run a single Feynman note a day for thirty days and the catalogue of concepts you can defend out loud will start to surprise you. The first sign is small. You read a new article and notice, mid-paragraph, that the author is restating a concept your last note already explained better. The second sign is harder to notice: you stop reading to feel productive, because the notes already in the book are still talking. Feynman's "NOTEBOOK OF THINGS I DON'T KNOW ABOUT" got shorter as the year went on. So will yours.

A daily Feynman note needs a notebook that survives your tools — MNMNOTE (mnmnote.com) lives in your browser, no account, no install.

Article JSON-LD

BreadcrumbList JSON-LD

FAQPage JSON-LD

HowTo JSON-LD