Learn the four Feynman technique steps and how to apply them to a certification syllabus to expose knowledge gaps before the exam does.
Try this right now: close the study guide and explain, out loud, how the concept you revised yesterday actually works — as if the listener were a bright colleague from a different department. Most candidates stall within two sentences. That stall is not a failure; it is the single most useful piece of diagnostic information you can get before an exam, and the Feynman technique is a structured way of producing it on demand.
Named after the physicist Richard Feynman, who was famous for insisting that anything truly understood can be explained simply, the technique turns "teach it in plain language" into a four-step study loop. For certification candidates it solves a specific problem: exams increasingly test whether you can apply a concept to a scenario, and recognising the right words in a study guide is not the same as being able to use them.
The Feynman technique is a study method in which you explain a concept in plain language, as if teaching a beginner, then use the points where your explanation breaks down to identify exactly what you have not yet understood. You then return to your source material to repair those specific gaps, simplify the explanation further, and repeat until it flows.
It is a form of self-testing, and that matters because the evidence favours it. Roediger and Karpicke's 2006 research on test-enhanced learning found that practising recall beats restudying for long-term retention, and Dunlosky and colleagues' 2013 review rated practice testing among the highest-utility study techniques while rating rereading low. Explaining from memory is retrieval practice with an added demand: you must also connect ideas and put them in your own words, which is where shallow familiarity gets exposed. If you want the fuller evidence comparison, our article on active recall versus rereading walks through it.
The classic loop has four steps. Here is how each one maps onto studying for a professional certification rather than a university course.
Write the concept at the top of a blank page — but choose it from the exam's official objectives list, not from a chapter title. "Networking" is too big; "explain the difference between symmetric and asymmetric encryption" is the right size. Certification blueprints already break domains into testable statements, which makes them a ready-made queue of Feynman targets. If you have never worked from one, learn how to read a certification exam blueprint first — it turns this step from guesswork into a checklist.
Below the title, write or speak an explanation aimed at someone intelligent but new to the field. Two rules make this work:
Speaking out loud works better than most candidates expect, because your ear catches hand-waving that your eye forgives.
Every time you hesitate, circle back to vague filler ("it sort of handles the traffic"), or realise you are reciting a memorised phrase you could not rephrase — mark it. These marks are your actual study list. Return to the course, documentation, or study guide and re-learn only those points. This is the step that separates the Feynman technique from ordinary summarising: you are not producing notes, you are producing a gap report.
Rewrite the explanation more simply. Where a concept stays slippery, build an analogy: a load balancer as a restaurant host seating diners at free tables, DNS as a phone directory. Then stress-test the analogy by asking where it breaks — the host does not health-check the tables, but a load balancer does check its targets. Knowing where your analogy fails is itself exam-grade understanding, because scenario questions live precisely in those edge cases.
Suppose a cloud fundamentals candidate picks "shared responsibility model" as the target. First attempt: "The provider secures the cloud and the customer secures what's in the cloud." It sounds complete — and it is exactly the kind of memorised slogan that fails under a scenario question. Pushed to teach it, the candidate stalls on a concrete case: who patches the operating system on a virtual machine versus a managed database service? The stall reveals the real gap: responsibility shifts with the service model, and that shifting line is what the exam actually probes. One targeted re-read later, the explanation becomes: "The more the provider manages for you, the more security tasks move to their side of the line — so for a virtual machine you patch the OS yourself, while for a managed service the provider does." That sentence would survive an exam scenario; the slogan would not.
The Feynman technique is deliberately narrow. It builds conceptual understanding, and it is slow per topic — a proper loop on one objective can take fifteen to twenty minutes. That has three practical consequences:
If a topic keeps refusing to click even after several loops, the problem is usually a missing prerequisite rather than a failed technique — our playbook on studying difficult technical topics covers that diagnosis.
No — and it does not claim to be. It is the understanding engine in a study system that also needs capture (notes), retention (spaced review — see spaced repetition for certification exams) and verification (practice questions). Used on the right targets, though, it does the one thing rereading never will: it makes your gaps visible while there is still time to close them, instead of letting the exam find them for you.
Exam facts in this guide were checked against official certification-provider pages on . Fees, exam codes and policies change — confirm on the provider’s own site before you book.
Put it into practice
Reading about an exam only takes you so far. Work through practice questions for your certification and find the gaps before exam day does.
·7 min read
Timing, score benchmarks and review technique for CompTIA practice tests — how to turn A+, Network+ and Security+ practice scores into a genuine pass signal.
Continue reading·8 min read
How to use CISA practice tests properly — when to take them, how to benchmark scores across the five domains, and how to turn wrong answers into study priorities.
Continue reading·8 min read
A practical buyer's checklist for choosing a reliable certification practice test: objective alignment, explanations, simulation features and red flags.
Continue reading
