Try this before you close the tab: read any article, then explain it out loud to an imaginary 12-year-old. No jargon. No “basically it’s about synergy.” If you stall in under 30 seconds, you didn’t learn it. You just scrolled past it.
A Redditor in r/ChatGPTPromptGenius turned that test into a ChatGPT Project. They’ve used it 20+ times, and the results stayed consistent. Let’s steal it.
🛠 How to set it up
- Create a new Project in ChatGPT and name it Feynman Technique.
- Set Memory to Project Only, so your learning sessions don’t leak into the rest of your chats.
- Set Space Access to Disabled.
- Paste the instructions into the Project’s instruction box. They’re long (about 900 words), but the structure is simple. You’re telling ChatGPT to act as your learning coach and run four stages: Select and Map, Explain It Simply, Review and Refine, and Test and Archive.
- Paste a full article or a YouTube transcript after the phrase “Simplify this” and hit enter.
The key rules in the prompt are the ones that make it feel different from a normal summary. It explains in plain words first and adds terminology later. It works on one concept at a time. It won’t finish the exercises for you, so you have to think first. And it keeps asking you to explain things back in your own words.
A quick practical note before you hit enter: pick something you actually care about for your first run. A dry article you’re forcing yourself through will make you skim, and skimming is exactly what this setup is designed to expose. Also, answer out loud or type your replies fully, even when it feels silly. Half-answers in your head always sound better than they are.
🎯 What the results mean
The author says the output comes back as the article’s concepts in plain language. It also quizzes you along the way and judges what you understand from your answers.
Here’s how to read that:
- You answer fast and in your own words: the idea stuck. Move on.
- You catch yourself using a term you can’t define: that’s the gap. The prompt is built to find it and send you back to the weakest spot first.
- You keep nodding but can’t answer the quiz questions: you were skimming. Annoying, but useful to know.
The prompt also tells the AI not to accept an explanation just because it sounds technical. Sounding smart and understanding something are two different skills, and this prompt checks for the second one.
One more way to read your results: pay attention to where you hesitate, not only to what you get wrong. A correct answer that took you a long pause usually means the idea is shaky. Note that spot and come back to it tomorrow. If the same concept trips you up twice, go find a second source on it instead of rereading the same article.
💡 Extra tips
- Learn the commands. The prompt recognizes shortcuts like “Start: [topic]”, “Map this”, “Feynman check”, “Test me”, “Archive this”, “Quick mode” and “Deep mode”. Quick mode is your friend on busy days.
- Use “Archive this” at the end. It writes a Learning Archive entry with the concept, a simple explanation, the vocab, an example, the common misconception, what you got wrong at first, and a suggested review date. Later, “Review: [topic]” quizzes you on it. Put the review date in your calendar the same minute you save the entry, or it will never happen.
- Trim it if you want. One commenter joked that at 900 words you could call it the Bananarama Technique and get the same result. Fair point. The author hasn’t tested that, and neither have I. If you shorten it, run the same article through both versions and see which one catches your gaps better.
- Try it on messy material. The author plans to feed it an AI-generated code repository next. Another commenter asked about uploading a full service training manual. Neither has been tested yet, so treat those as experiments. Start with one article, and if it holds up, go bigger.
- Keep sessions short. One article, one concept at a time, maybe 15 minutes. Short sessions you actually finish beat marathon sessions you abandon.
✨ Prompt of the day
Don’t want to build the full Project yet? Paste this into any chat:
“You are my learning coach. I’ll paste an article. Explain it like I’m 12, one concept at a time. Then ask me to explain the first concept back in my own words, tell me exactly what I got right and wrong, and quiz me one question at a time without showing the answers first.”
It’s the same idea in about 60 words. Run it on the next thing you read and see how long you last before the first quiz question stumps you.
🚀 Your move
Pick one article you read this week and swear you understood. Run “Simplify this” on it and be honest about your answers. Then tell me how it went! Did it find a gap you didn’t know you had? 🏴☠
Frequently Asked Questions
Q: Can this work on a long manual, like a service guide for a device?
Yes, the same approach works on any pasted text, and a service manual is a solid test case. For a long document, paste one section at a time so each round of quizzing stays focused. Add the audience to your request, like ‘explain this for a 12-year-old,’ and ask the coach to keep safety warnings word for word.
Q: Do you need the long custom instructions, or does a plain ‘Simplify this’ do the job?
One commenter thinks a plain request gets you most of the way and that a 900-word prompt would give about the same result. The author’s view is that the custom instructions add the quizzing and the check on what you understand, and a plain request skips that step. Run both on the same article and see whether the extra setup is worth it for you.
Q: Can you use it on code, not just articles?
One commenter plans to test it on an AI-generated project, a small Swift Apple Notes clone, while the author has so far only pasted in articles and transcripts. Start with a small project and paste in one file along with a sentence about what it does, so the explanations have something concrete to anchor to.
Please try my Feynman Technique Prompt in Projects
by u/Jordan-Peterson-High in ChatGPTPromptGenius