The people best at a subject are often the worst at explaining it โ not from arrogance, but because expertise erases the memory of not understanding.
You no longer notice the steps you skip, because to you they are not steps.
The gap you cannot see
- You compress several steps into one without noticing.
- You use terms that feel plain to you and are not.
- You start from the structure of the subject, not from where the learner is.
- You skip the part you personally found obvious โ which is often the part others find hardest.
The fix is not to simplify. It is to find out where the learner actually is, and build from there.
Build from what they already know
- Ask what they already understand about the area before explaining anything.
- Connect the new idea to something familiar โ this is what makes an explanation stick.
- Name the misconception if there is a common one. People cannot absorb a correct model while holding an incorrect one; the wrong idea has to be addressed directly.
- Go one step at a time and check before moving on.
Using examples properly
- Concrete before abstract. Show a specific case first, then generalise. Almost every confusing explanation does this in the opposite order.
- Use more than one example โ a single example gets learned as the rule.
- Include a non-example โ showing what the concept is not sharpens the boundary faster than more examples of what it is.
- Choose examples from their world, not yours.
Analogies: useful and dangerous
- A good analogy makes an idea graspable immediately.
- Every analogy breaks somewhere โ and learners will follow it past that point.
- So state where it breaks, explicitly. This one habit prevents a lot of later confusion.
- Drop the analogy once it has done its job โ do not build further ideas on top of it.
Checking understanding
Asking whether that makes sense does not work. People say yes for social reasons and because they do not yet know what they have missed.
What works:
- Ask them to explain it back in their own words.
- Give a new case and ask them to apply it.
- Ask what would happen if โ a question that requires the model, not the words.
- Ask what part is still unclear โ this gets better answers than asking if anything is unclear, because it assumes something is.
When someone is stuck
- Do not repeat the same explanation louder. If it did not work the first time, it will not work the third.
- Find out what they think is happening โ the wrong model tells you exactly which explanation is needed.
- Go back further than feels necessary. The block is usually earlier than where it surfaced.
- Try a different mode โ draw it, walk through a concrete case, have them do it while you watch.
- Give it time. Some ideas need a night in between; pushing harder in the moment rarely helps.
Language
- Define a term the first time you use it, then use it consistently.
- Do not use two words for the same thing โ learners assume they are different.
- Prefer short sentences. Complexity of subject does not require complexity of sentence.
- Watch for words with a specialist meaning that differs from ordinary use โ these are a major source of silent misunderstanding.
- For learners working in a second language, plain language and consistent terms matter even more.
Structure of a good explanation
- Say what it is for before saying what it is. People retain explanations better when they know why they need them.
- Give the short version first, then the detail. Detail without a frame is hard to hold.
- Show a worked example all the way through.
- Have them do one while you watch.
- Summarise in one sentence at the end.
Getting better at this
- Notice the questions you get repeatedly โ each one marks a place your explanation fails.
- Keep a note of the misconceptions you encounter; they are the most valuable teaching material you own.
- Watch someone else teach the same thing.
- Ask a beginner to explain it back and listen for the distortion โ that is where your version was ambiguous.
One thing worth remembering
The mark of a good explanation is not that it sounds thorough. It is that the learner can use the idea afterwards without you present.
Everything above is a way of testing for that earlier rather than later.
FAQ
Why are experts often poor explainers?
Because expertise erases the memory of not understanding โ you compress steps without noticing and skip the parts you personally found obvious, which are often the hardest for others.
What order should examples come in?
Concrete before abstract โ show a specific case first, then generalise. Almost every confusing explanation does this in the opposite order.
How should analogies be used?
Use them, but state explicitly where the analogy breaks, and drop it once it has done its job rather than building further ideas on top of it.
How do I check whether someone understood?
Not by asking if it makes sense. Ask them to explain it back in their own words, apply it to a new case, or answer a what-would-happen-if question.
What should I do when someone is stuck?
Find out what they think is happening โ the wrong model tells you which explanation is needed โ and go back further than feels necessary, because the block is usually earlier than where it surfaced.