Skip to content
All notes
Notes3 min read

The Feynman technique: explain it to your younger cousin

The Feynman technique is explaining something in plain words to find where your understanding stops, tried here on a term insurance policy and a cousin's one question.

  • learning
  • autopilot
  • hermes

Meera has read her term insurance policy twice. At a family lunch in Pune she tells everyone she has understood it. Her cousin Aarav, nineteen, looks up from his plate and asks, "So when does the company not pay the claim?"

Meera opens her mouth. The dal gets cold. Nothing useful comes out.

What the model is

The Feynman technique is a way to test whether you really understand something. You explain it, in plain words, to someone who does not know it, and you watch where you stall. The method is named after the physicist Richard Feynman, who is often described as learning this way.

It has four steps: explain, find the gap, go back, simplify. Reading a page twice feels like knowing it. Explaining it is the quickest way to see where the knowing stops.

Meera tries it

Explain. That night she takes a blank page and writes as if Aarav is sitting next to her. "If something happens to me, my family gets a fixed sum." That part comes easily.

Find the gap. Then she writes Aarav's question at the top of a new line, and she stops. She can name one reason a claim might be refused, but only by copying the policy's own phrase, and she cannot say what it means. She also cannot say what she was supposed to tell the company when she applied. She circles both. Two gaps, after two readings.

Go back. She does not read the whole policy a third time. She goes only to the two circled places: the list of situations the policy does not cover, and the part about what an applicant must declare. She reads slowly, with a pencil. Where a word still does not make sense, she writes it down as a question for the insurer.

Simplify. She rewrites each answer so a ten-year-old could follow it, with no policy words left. Her list of situations the policy does not cover becomes a few short sentences, one per line. The next day she reads them out to Aarav. He asks one more question, and she has a gap to circle again.

Where it stops

A smooth explanation is not the same as a correct one. You can explain a mistake very clearly. The technique shows you where your understanding is thin; it does not check that what you wrote is right.

It also goes wrong when your listener only nods. Pick someone who will ask "but why?" Where the gap is in the document itself, the answer has to come from the insurer or someone qualified, not from a better explanation.

One thing to try today

Pick one thing you feel sure you know: how your EMI is worked out, how a recipe thickens, how your phone's data pack runs out. Tonight, explain it in five sentences to someone younger, or write it on a page as if to them. Mark the first sentence where you slow down. Go back to that spot only, and read just that part again.

This is a way to think, not financial, medical or legal advice.

Each Sunday: one mental model and one real decision to try it on, all in the /models library.

One model a week.

Each Sunday: one mental model and one real decision to try it on. One click stops it, and the list is never sold or shared.

By subscribing you agree to receive one weekly email from Mental Models. You can unsubscribe at any time.

Share by email