Dr. Wallace's Favorite Mental Models

Theory of Mind

The quiet skill behind every good explanation, every good negotiation, and every good piece of design: knowing that what's in your head is not automatically in theirs.

130-Second Overview

The idea in one sentence: theory of mind is the ability to recognize that other people hold their own beliefs, knowledge, intentions, and perspectives — ones that can be different from yours — and to use that recognition to predict and interpret what they'll do next.

Where it comes from

Psychologists David Premack and Guy Woodruff introduced the term in 1978 while studying whether a chimpanzee named Sarah could infer a person's hidden goal from a video, rather than just copying what she saw. In 1985, Simon Baron-Cohen, Alan Leslie, and Uta Frith built the classic test for it in children: the Sally-Anne false-belief task.

Why it matters

Almost every failure to explain, persuade, design, or manage well traces back to the same root error: assuming other people already have the information, context, or framing that's sitting in your own head. Theory of mind is the habit of checking that assumption before you act on it.

2Mental Model Compass

Type of thinking
Social cognition / perspective-taking
Best for
Predicting how someone will read or react to something
Difficulty
Simple to grasp, easy to forget under pressure
Time to apply
2–10 minutes per decision

Reach for it any time you're about to explain something, write something, negotiate something, or design something for someone whose starting knowledge, goals, or assumptions are not identical to yours — which is almost always.

3Walk Through It

4What You Know vs. What They Believe

Pick a situation below, then compare what the person with more information actually knows to what the other person currently believes — and watch where the gap causes trouble.

What you actually know

What they currently believe

5Diverse Examples

Management
A manager who has been thinking about a reorg for three months announces it in a five-minute meeting, then is surprised the team is anxious — the team is reacting to three months of change compressed into five minutes, with none of the context the manager had time to absorb.
Product & UX design
Designers who use a product daily place an advanced setting one tap away because it feels obvious to them; new users, who have no mental model of the menu yet, never find it. The feature isn't missing — the designer's theory of the user's mind was wrong.
Negotiation
A seller assumes a buyer knows the production costs that justify a price; the buyer, who doesn't see those costs, reads the same price as padding. Naming the cost structure out loud closes a gap the seller didn't know existed.
Onboarding & teaching
An experienced employee explaining a process to a new hire skips the "obvious" first step, because it stopped being a conscious step for them years ago. The new hire doesn't know it's missing, because they don't know what they don't know either.
Customer support
A support agent tells a frustrated customer to "check their API key scopes," using language that assumes technical familiarity the customer doesn't have, which reads to the customer as being brushed off rather than helped.
Working with AI assistants
Getting a useful answer from an AI assistant often depends on modeling what context it does and doesn't have in front of it — the same discipline, applied to a system rather than a person. (Researchers are actively debating whether language models have anything like real theory of mind themselves, see Section 8 — this is about modeling the tool, not crediting it with a mind.)

6Worked Application

Situation: a product manager ships a redesigned dashboard. The new "Export" button moved from the top toolbar into a menu, which feels like a minor, sensible cleanup to the team that built it. Two weeks after launch, usage of the export feature has dropped by a third, and support tickets about "missing" export are piling up.

  • Step 1 — Notice the gap: the product manager knows exactly where Export moved to, because they watched it move across a dozen design reviews. Users have no such history — their only mental model is the old toolbar.
  • Step 2 — Catch the default assumption: the team's instinct is to assume the new location is "discoverable" because it's discoverable to them. That's the curse-of-knowledge trap, not evidence about new users.
  • Step 3 — Model the user's actual belief: a returning user's working theory is still "Export lives in the top toolbar, roughly where it always has." When it's not there, their next guess is usually "this feature got removed," not "this feature got relocated."
  • Step 4 — Predict their move, then test it: if the belief is "it's gone," the predicted behavior is giving up or opening a support ticket rather than hunting through menus — which matches what actually happened. A one-time tooltip pointing from the old toolbar location to the new menu, shown only to users who used the old Export button, directly targets that specific false belief rather than the feature in general. Export usage recovers within a week of shipping the tooltip.

7Common Mistakes

Assuming others share your information. This is the single most common failure — treating your own knowledge as the default state of everyone else's mind, rather than something you had to acquire.
Confusing it with empathy. Theory of mind is a cognitive read of what someone believes, knows, or intends; empathy is an emotional connection to how they feel. You can model someone's beliefs accurately while feeling nothing for them, and feel deeply for someone while badly misjudging what they actually think.
Treating one correct read as proof you always read people correctly. Guessing right once breeds overconfidence in guesses you haven't checked. Theory of mind is a habit of checking, not a credential you earn and then stop verifying.
Projecting your own motives instead of modeling theirs. It's easy to slide from "what do they believe" into "what would I want if I were them" — which quietly substitutes your values for their actual ones.
Over-pathologizing "deficits" from a single test format. Much of the research on theory of mind differences — in autism in particular — has had to be revisited, because behavioral false-belief tests and brain-imaging measures of the same people don't always agree, suggesting a measurement gap rather than a clean cognitive one.
Assuming the skill looks the same everywhere. Studies of children in Vanuatu found delays on standard false-belief tasks tied to a local norm against speculating openly about other people's thoughts — a cultural difference in what's considered polite to say out loud, not evidence of a universal developmental gap.

8When Not to Use It

  • When you can just ask. Inferring what someone believes is a fallback for when you can't check directly — it's not a substitute for asking a direct question when that's available and appropriate.
  • As a clinical or diagnostic instrument on its own. Performance on a short false-belief test doesn't reliably predict how someone actually functions socially day to day; treat it as a classroom concept and a personal habit, not a screening tool.
  • As a way to claim certainty about someone's "real" motives. A model of what someone believes is still a model, built from limited evidence. Holding it loosely, and updating it, is the whole point.
Counterpoint: critics of the concept argue that treating other minds as hidden, private spaces you must infer from the outside misdescribes a lot of real social understanding, which often happens directly and immediately through tone, context, and shared activity — not step-by-step inference. Use the model to catch the specific failure of assuming shared information, not as a complete theory of how people understand each other.

9Related Models

10Try It Yourself

11Save as Skill

Turn this mental model into a reusable instruction you can hand to any AI assistant — or to yourself — before any explanation, pitch, design decision, or negotiation that depends on someone else's current beliefs.

Copied!