Dr. Wallace’s Favorite Mental Models

The Illusion of Explanatory Depth

Learn it → Apply it → Save as Skill

You understand it — until you have to explain it. Most people feel they grasp how everyday things and familiar plans work. That feeling collapses, fast, the moment someone asks for the actual step-by-step mechanism.

Why This Library Is Different

Learn it. Apply it. Save as Skill.

The Dr. Wallace’s Favorite Mental Models is designed to turn useful ways of thinking into reusable tools. Each model gives you a fast visual overview, deeper interactive learning, practical application exercises and an AI-ready Markdown skill you can save for future use.

Instead of merely reading about mental models, you can gradually build your own AI skills library: a collection of portable reasoning skills that can help ChatGPT, Claude, Grok and other AI assistants apply the mental models you value.

30-Second Understanding
Fluency isn't depth.

You can recognize something, use it daily and talk about it smoothly, and still have no real model of how it works underneath. The gap only shows up when you're forced to produce the mechanism step by step, out loud, for someone who knows nothing.

Core question: Could I actually explain this, step by step, to someone who knows nothing about it — without hand-waving over any step?

The memorable shorthand

High
Lower

Before explaining self-rated understanding is high. After explaining — once you try to write the actual mechanism — it drops. The drop size varies by person and topic; what matters is that it drops at all.

Mental Model Compass

Use it when confidence outpaces testing.

The model is most useful whenever someone (including you) claims to understand a mechanism, system or plan, but that claim has never actually been tested by producing the explanation.

CalibratePrimary use case
BeginnerDifficulty
3 minUnderstand
10–20 minApply with a real topic
Hiring & interviewsTechnical reviewsTeaching & onboardingPolicy & civic debateProduct decisionsSelf-assessment
Model at a Glance

Claim → Explain → Re-rate → Locate the gap.

The method is a small, repeatable test you can run on yourself or, carefully, invite someone else to run on their own claim.

01Claim

Rate how well you understand something, on a simple scale, before you try to explain it.

02Explain

Write or say the actual step-by-step mechanism, out loud, with no hand-waving over any step.

03Re-rate

Rate your understanding again, honestly, right after attempting the explanation.

04Locate the gap

The drop between the two ratings points to exactly which step was never actually understood.

When Should I Use This?

Recognize the situation.

Open a use case to see what the model changes.

Hiring
A candidate sounds fluent about a system they built

Fluent description is not proof of depth. Ask the candidate to walk through what happens, step by step, when a specific input hits the system — including the parts that usually get summarized rather than explained.

Technical Leadership
A team says a design is "well understood"

Before approving a plan, ask one person to produce the actual causal chain on a whiteboard. The exercise reliably surfaces the step everyone assumed someone else owned.

Product
You're confident you understand how users behave

Write the mechanism you believe drives a metric, step by step, before proposing a fix. If the explanation stalls, the fix is premature — test the mechanism first.

Education
Students say "I get it" after a lesson

Replace "do you understand?" with "explain it back to me, step by step." The request itself, done kindly, is the diagnostic.

Policy & Civic Debate
Strong opinions on a complex policy

Research on this effect has been studied most in politics: asking people to explain exactly how a policy would work, mechanism by mechanism, tends to moderate overconfident positions more than asking them to justify why they hold them.

Self-Assessment
Deciding whether you're ready to teach or ship something

Before presenting, draft the explanation cold, without notes. Gaps found in private cost nothing. Gaps found live cost credibility.

Worked Example

"I understand our recommendation engine." Do you?

This is an illustrative example designed to teach the method.

Before: confident
Starts explaining
Reaches ranking step
Reaches tie-break logic
Reaches edge cases
After: calibrated
SITUATIONA product manager is about to approve a roadmap change to the recommendation engine.
CLAIMRates their understanding of how it ranks items as 6 out of 7.
EXPLAINWalks an engineer through the ranking logic step by step, out loud.
RE-RATEGets stuck at the tie-break and cold-start steps; re-rates understanding at 3.
GAP FOUNDThe exact steps they could not explain are the steps the proposed change would touch.
NEXTPairs with the engineer on those two steps before approving, instead of after shipping.
Do not conclude: "I never really understand anything." The useful finding is narrower — exactly which steps were fluent-sounding guesses, so you know where to check before acting on them.
History & Accuracy

A precise finding, often loosely retold.

Expand for the distinction between the original study, a famous related illustration, and two commonly confused neighbors.

What did Rozenblit and Keil actually find?

In 2002, Yale psychologists Leonid Rozenblit and Frank Keil coined "the illusion of explanatory depth" after asking a small group of undergraduates to rate how well they understood everyday devices and mechanisms, then write a detailed, step-by-step explanation of how each one worked, then rate their understanding again. Ratings were consistently lower after the explanation attempt than before it. The researchers concluded that the act of generating a mechanistic explanation — not just thinking about the topic — is what exposes how little is actually known.

Is the bicycle-drawing study the same research?

No, and this is the most common mix-up. The bicycle illustration comes from a separate, later study: Rebecca Lawson's 2006 paper "The Science of Cycology," which asked people — including regular cyclists — to complete a simple diagram of a bicycle's frame and chain. Many got the mechanism wrong despite years of daily familiarity. It is a related, independently useful demonstration of the same underlying gap between felt and demonstrated understanding, not a replication of the original Rozenblit–Keil study.

How is this different from the Dunning-Kruger Effect?

Dunning-Kruger is about self-assessed ability, and is usually framed around people of low-to-moderate competence overestimating their skill relative to others. The illusion of explanatory depth is about self-assessed explanatory knowledge of a mechanism, and research suggests it affects nearly everyone — including genuine experts, though typically less severely in their own specialty.

How is this different from the Curse of Knowledge?

The curse of knowledge is about forgetting what it was like not to know something once you do know it, which makes your explanations to novices too compressed. The illusion of explanatory depth is about not actually possessing the mechanism in the first place, no matter who you're explaining it to. The two often travel together — a true expert can suffer from the curse of knowledge about parts they genuinely understand, while still having illusory depth about parts they don't.

Common Mistakes

Simple does not mean foolproof.

Mistaking fluency for depth

Smooth, confident talk about a topic is not evidence of a working causal model. Only the step-by-step explanation tests that.

Assuming experts are immune

The effect is reduced, not eliminated, for genuine subject-matter experts — and can return the moment they're asked about an adjacent part of their own field.

Using it to shame, not calibrate

The point is recalibration, not "gotcha." Run it on yourself first, and frame it gently when used with others.

Testing facts instead of mechanism

Reciting correct facts about a topic is not the same as explaining how its parts cause its outcomes. Ask "what happens next, and why," not "what is it called."

Confusing it with asking for reasons

Research on political topics found that asking people to justify why they hold a position can backfire and entrench it further. Asking them to explain how the mechanism works is what tends to moderate overconfidence.

Overapplying it to practiced motor skill

Being unable to explain how bicycle gears work is not the same failure as being unable to ride one. Don't use this model to doubt a demonstrated, practiced skill.

When Not to Use It

Some claims don't need this test.

Use direct testing when...

the stakes require demonstrated performance, not self-rated understanding — watch the person actually do the task instead of asking them to explain it.

Skip it for practiced skills when...

the claim is about procedural or motor competence rather than explanatory knowledge — riding, typing, or driving don't require a verbal mechanism.

Use it sparingly when...

time is short and action is urgent — demanding a full mechanistic explanation mid-crisis can stall necessary decisions rather than improve them.

Counterpoint: an explanation can sound complete and still be wrong. Passing this test shows you can produce a mechanism, not that the mechanism you produced is correct — verify the content separately.
Combine It With

One model rarely does the whole job.

Try It Yourself

Build an explanatory-depth check prompt.

This browser tool structures your thinking. It does not send your information anywhere or perform AI analysis.

Your AI-ready prompt

Complete the fields, then build your prompt.
Save as Skill

Turn this mental model into a reusable AI skill.

Save as Skill converts the model into portable Markdown instructions that teach an AI when and how to apply the illusion of explanatory depth, what questions to ask, what evidence to seek, what mistakes to avoid and how to structure its analysis.

Build your own Mental Models Skills Library

Save the skills you find useful and organize them into your own reusable library. The Markdown is intentionally model-neutral, so it can be used wherever an AI system accepts uploaded files, project knowledge, custom instructions or reusable text context. Platform capabilities differ, so this is a portable skill file rather than a claim of one-click installation.

Go Deeper

For readers who want the nuance.

Does explaining it to someone else matter, or is writing it down alone enough?

Writing a private, step-by-step explanation is usually enough to trigger the recalibration — the audience doesn't have to be real. What matters is forcing the mechanism into explicit, ordered steps rather than letting it stay as a vague felt sense.

Why does explaining work better than just thinking harder about it?

Silent reflection lets vague, compressed mental shortcuts stand in for a mechanism without ever being checked. Producing an explicit, ordered explanation forces each step to be stated, which is where the missing links become visible.

Does this mean confident people are usually wrong?

No. Confidence and accuracy are correlated in many domains, especially with real practice and feedback. The illusion specifically targets a narrower claim: confidence about possessing a step-by-step causal mechanism, which is a different and more demanding kind of understanding than general competence or familiarity.