It's Not Just Being a Good Speaker
When someone tells you,
That was super easy to understand
you probably think,
Maybe I just talk well
But if you made sense of a brand-new document on the spot and then explained it right away, smooth talking alone can't account for that.
That's because you have to organize the information in your head before you open your mouth.
Say there are several finely divided categories, and you explain them like this:
The details differ a little.
But the overall flow is the same.
And if you zoom out further, it's just three steps.
That isn't just "making the wording simpler."
You've redesigned the structure of the original information itself.
You Hand Over a "Map" First
What trips up beginners most is this:
I can't tell where in the big picture the thing I'm hearing right now fits
Someone explains A.
Then B comes along.
C has an exception.
Only D has a separate form.
If you take everything in order, it all ends up in one flat pile.
So you hand over a map first:
The whole thing is three steps
And then you add:
A through E are just the finer divisions inside those three steps
After that, every time a new point comes up, the listener can place it:
Oh, this is about step two
This lowers a beginner's cognitive load, and it's a sound way to help them build a schema, a mental framework for the topic.[4]
Asking "Got It?" Doesn't Tell You Whether They Really Understood
After explaining, you ask,
Got it?
and the answer comes back,
Yes
But you can't tell whether that "yes" means
- they truly understood
- they sort of feel like they get it
- they don't want you to stop explaining
- asking a question feels like a hassle
- it's hard to admit they're lost
So instead you hand them a new case:
Okay, so what do you think happens in this situation?
If they can sort it out themselves and explain why, you've confirmed pretty solidly, at least for the moment, that they understood.
What's happening here is close to retrieval practice (pulling information out of memory) and to transfer, which means applying a framework you've learned to a new problem.
In a study by Karpicke and Blunt, retrieval practice, where you pull learned material out of your head and rebuild it yourself, produced better results in meaningful learning than simply rereading or than elaborating with concept maps.[7]
The Person Doing the Teaching Is Learning, Too
Here's the really interesting part: the person who's teaching.
To teach someone, you have to
- separate the key points from the side details
- change the order
- avoid words the other person doesn't know
- come up with examples
- answer questions
- spot where they've misunderstood
Koh and colleagues showed that part of the learning benefit of teaching others may be explained by retrieval, pulling information out of memory while you teach.[8]
Researchers are still debating the mechanism in follow-up studies.
So we can't go as far as saying,
Teaching someone will always make you smarter
Still, the idea that explaining from memory, rather than just reading your notes, helps learning is consistent with the retrieval research.
Clear Explanations Aren't Just About Compression
That said, shorter isn't always better.
Compress too much and you end up with
So it's all the same
and the exceptions vanish.
A good explanation looks like this:
Compress what the items have in common
Keep only the differences that matter for making decisions
In other words, you can say:
A through E are basically the same
Except this one category differs here
That isn't oversimplifying. It's structured omission.
If It Works on a Document You've Never Seen, It's Not Rote Explaining
If someone wrote a script ahead of time and got good by giving the same explanation 100 times, that's explained by routine expertise, meaning skill at handling familiar, standard situations.
But when it goes like this:
A document you've never seen
↓
Pull out its structure on the spot
↓
Rephrase it for a beginner
↓
Adjust your answers to their questions as you go
then you're closer to adaptive expertise.
Hatano and Inagaki distinguished routine expertise, which handles familiar situations efficiently, from adaptive expertise, which applies knowledge flexibly even in new situations.[9]
A review by Carbonell and colleagues also concludes that the difference in adaptive expertise shows up especially when people face unfamiliar situations.[10]
That's why it matters that the explanation worked on a document you'd never seen.
Calling Someone "Bad at Understanding Things" Doesn't Add Up
Suppose the verdict
Poor comprehension
were accurate. Then you'd have to explain behavior like this:
- spotting the shared structure of a document on first sight
- compressing several categories into a few big steps
- translating it for beginners
- checking understanding with a new case
Of course, one success story isn't enough to declare someone "highly capable" either.
But if the same pattern keeps repeating across multiple situations, then
Poor comprehension
is too thin an explanation.
It would be more accurate to look at these separately:
- the ability to structure information that's stated openly
- the ability to infer unspoken expectations
- how well someone performs under pressure
- communication with the person evaluating them
- job knowledge
