Feynman Technique & 80/20 Rule

TL;DR

The Feynman Technique forces deep understanding by making you explain concepts simply. The 80/20 Rule (Pareto Principle) tells you which 20% of a subject gives you 80% of the results. Combined, they are the fastest way to learn the important stuff deeply.

Explain Like I'm 12

Learning is like packing for a trip. The 80/20 Rule tells you to only pack what you'll actually wear — no need to bring 15 shirts for a 3-day trip. The Feynman Technique tells you to explain your packing list to a 5-year-old: "I'm bringing this jacket because it's cold there." If you can't explain why you packed something, you probably don't understand your trip well enough.

Together: pick the important stuff (80/20), then make sure you really understand it (Feynman). That's it. That's the whole secret.

The Big Picture

The Feynman Technique 4-step loop and 80/20 focus funnel

The 80/20 Rule for Learning

Where it comes from

In 1896, Italian economist Vilfredo Pareto noticed that 80% of Italy's wealth was owned by 20% of the people. The pattern keeps showing up everywhere: 80% of bugs come from 20% of the code. 80% of sales come from 20% of the customers. And in learning: 20% of concepts give you 80% of practical knowledge.

Real examples

Here's what 80/20 looks like across different subjects:

Subject The 20% that matters What you can skip (for now)
SQL SELECT, WHERE, JOIN, GROUP BY, subqueries Window functions, CTEs, recursive queries, temp tables
Python Variables, loops, functions, lists, dicts Decorators, metaclasses, async/await, generators
Excel Formulas, VLOOKUP, pivot tables, charts VBA, Power Query, macros, custom functions
Healthcare Claims process, coding (CPT/ICD), plan types Risk adjustment, HEDIS measures, EDI standards

How to find the 20%

  1. Read the table of contents. The first 3-5 chapters are almost always the core 20%.
  2. Ask an expert: "If I could only learn 5 things, what should they be?"
  3. Look at job descriptions. What skills are "required" vs "nice-to-have"? Required = 20%.
  4. Find the most-referenced concepts in beginner tutorials. If every tutorial mentions it, it's in the 20%.
Start with the smallest useful set. You can always expand later. The goal is to be dangerous, not perfect. A developer who knows 5 SQL commands well is more useful than one who vaguely remembers 50.

The Feynman Technique — Step by Step

Named after physicist Richard Feynman, who was famous for explaining impossibly complex ideas in simple language. His secret wasn't genius — it was a method anyone can use.

The 4 Steps

  1. Pick ONE concept (not a whole chapter, not a whole book — one concept).
  2. Write an explanation in plain English, as if teaching a curious 12-year-old. No jargon. No copying from the source material. Your words, your analogies.
  3. Find your gaps. Where you get stuck or resort to vague hand-waving = what you don't actually understand. Go back to the source material for just that gap.
  4. Simplify further. Use analogies. If your explanation is longer than 3 paragraphs, it's too complex. Cut it down.

The loop: Explain → Find gaps → Study gaps → Explain again → Repeat until crystal clear.

If you're just paraphrasing the textbook, you're not doing Feynman. You need to use YOUR words, YOUR analogies. The discomfort of translating jargon into simple language IS the learning. If it feels easy, you're probably just copying.

Feynman in Action — Worked Example

Let's walk through a real Feynman cycle. Topic: "What is a database JOIN?"

Attempt 1 (bad)

"A JOIN combines rows from two or more tables based on a related column between them."

This is just a textbook definition. You could say this sentence without understanding a single thing about JOINs. It doesn't pass the Feynman test.

Gap found

What does "related column" actually mean in practice? What happens to rows that don't match? Why would I need this instead of putting everything in one table?

Attempt 2 (better)

"Imagine two spreadsheets: one has student names and their class IDs, the other has class IDs and teacher names. A JOIN is like saying 'match them up by class ID so I can see which student has which teacher.' If a student doesn't have a class, they disappear from the result (that's an INNER JOIN). If you want to keep ALL students even without a class, that's a LEFT JOIN."
Notice the difference. Attempt 2 uses a concrete analogy (spreadsheets, students, teachers), explains the WHY (you want to connect related data), and even handles edge cases (what about unmatched rows?). That's the Feynman test: could a 12-year-old follow this?

Combining 80/20 + Feynman

These two techniques are even more powerful together. Here's the workflow:

  1. Use 80/20 to identify the 5-7 key concepts. Don't try to Feynman everything — just the stuff that matters.
  2. Use Feynman on EACH of those concepts. Write an ELI12 explanation for every one.
  3. Write your Feynman explanations into a personal cheat sheet. One page, 5-7 concepts, each with a plain-English explanation.

This cheat sheet becomes your go-to reference and review tool. When you need a refresher, you read your words, not a textbook. And because you wrote it, the act of reading it triggers deeper recall.

This is exactly what QuickLearnPro does for every topic: identify the core concepts (80/20), then explain them simply (ELI12 = Feynman). The TL;DR boxes, the ELI12 sections, the cheat sheets — you're already using these techniques by reading this site. Now you know how to create them yourself for anything.

Common Mistakes

Mistake Which rule it breaks What to do instead
Trying to learn everything at once Violates 80/20 Pick the top 5-7 concepts first. Expand later.
Copying definitions instead of creating your own Violates Feynman Close the book. Write from memory. Use your own words.
Skipping the "explain it" step (just reading) Passive learning After every section, pause and explain it aloud or in writing.
Never going back to fill gaps Incomplete Feynman loop When you get stuck, that's the signal to go deeper — not to skip.
The biggest mistake of all: thinking that reading = learning. Reading is the start. Understanding comes from explaining. Retention comes from testing. Reading alone gives you the illusion of competence without the reality.

Test Yourself

Q: What is the 80/20 Rule in the context of learning?

20% of the concepts in any subject give you 80% of the practical knowledge. By identifying and focusing on that critical 20% first, you get the biggest learning ROI in the shortest time.

Q: What are the 4 steps of the Feynman Technique?

(1) Pick one concept. (2) Write an explanation in plain English as if teaching a 12-year-old. (3) Identify gaps — where you get stuck or hand-wave. (4) Go back to the source for just those gaps, then simplify your explanation further. Repeat until crystal clear.

Q: How do you identify the "20%" for a new subject?

Read the table of contents (first 3-5 chapters are usually core), ask an expert what's essential, look at job descriptions for required vs nice-to-have skills, and find the most-referenced concepts across beginner tutorials.

Q: What's wrong with this Feynman explanation: "A JOIN combines rows from two tables based on a related column"?

It's just paraphrasing the textbook. A real Feynman explanation would use a concrete analogy (like matching two spreadsheets by a shared column), explain WHY you'd want it, and cover edge cases in simple terms. The discomfort of creating your own analogy is where the learning happens.

Q: How do you combine 80/20 and Feynman into a practical workflow?

Step 1: Use 80/20 to identify the 5-7 key concepts. Step 2: Use the Feynman Technique on each concept (write a plain-English ELI12). Step 3: Compile your Feynman explanations into a one-page personal cheat sheet that becomes your go-to review tool.

Interview Questions

Q: How would you apply the Feynman Technique to learn a new technology in one week?

First, I'd use the 80/20 Rule to identify the 5-7 core concepts by scanning documentation, reading introductory tutorials, and checking what skills are listed as "required" in job postings. Then for each concept, I'd write an ELI12 explanation from memory — no copying. Wherever I got stuck, I'd go back to the docs for just that gap. By end of week, I'd have a personal cheat sheet with all core concepts explained in my own words. I'd know I understood something when I could explain it simply without looking at any reference.

Q: Give an example of the 80/20 rule applied to your last project.

A good answer picks a specific project and identifies what the critical 20% of work/knowledge was. For example: "On a data pipeline project, 80% of the business value came from 5 core SQL transformations. I focused on getting those right first before optimizing edge cases. Or: "When learning Power BI, I focused on DAX measures, relationships, and visual filters first — that covered 80% of the dashboards my team needed."

Q: How do you decide what to learn first when starting a new domain?

I look at three signals: (1) What concepts are mentioned in every beginner resource? Those are the foundation. (2) What do job descriptions list as "required" vs "preferred"? Required = 20%. (3) I ask someone already in the domain: "If I could only learn 5 things, what should they be?" Then I learn those 5 things deeply using the Feynman Technique before expanding into less critical areas.

Related Topics

Core Concepts
5 learning techniques that work: 80/20 Rule, Feynman Technique, Active Recall, Spaced Repetition, and Immersion.
Active Recall & Spaced Repetition
Test yourself instead of re-reading. Review at increasing intervals. The most scientifically proven way to build long-term memory.
Your Learning System
A practical day-by-day system that combines all 5 techniques into a repeatable 4-week workflow.