Thinking 101 — Fluency, Confirmation Bias, and the Opposite Question

Hypotheses are not for forming — they’re for doubting

When I notice something at work, I tend to form a hypothesis first, then investigate it from multiple angles. For sources with definitive answers — like vendor documentation — there is no need to doubt. But for sources without a fixed answer, like Q&A sites or anecdotes, I have always believed that a hypothesis only becomes my own conviction after I have asked others, read books, and verified it in practice.

The Yale intensive lecture book Thinking 101 (Japanese title: 思考の穴) gave me a sharper vocabulary for that habit. In this note I summarize the five concepts that stood out, and tie them to my own experience leading a small team.

Fluency — the illusion of “I could do that”

When people misunderstand or over-trust something, fluency is usually behind it. Fluency means visual information being processed smoothly, without noise or distortion, in our minds.

Watch a clip of Michael Jackson moonwalking ten times and many people start to feel “I could probably do that too.” The footage is smooth, the mental replay is smooth — and that smoothness gets misread as ability. That is fluency-driven overconfidence.

You notice a thinking hole the moment you try to explain it concretely

So how do we catch ourselves in this trap? The book’s answer is simple: try to explain it concretely.

The moment someone asks, “to perform a moonwalk, how exactly do you lift your heel and shift your weight?”, most of us go silent. The smooth mental footage and the procedural knowledge our body would need are two completely different things.

The gap you cannot explain is the thinking hole the title points to.

Plans are always too optimistic — assume it

We make plans before any action. And they slip. In the worst case they collapse. Why? Because at the moment of planning, everything is running fluently in our head. The plan stands on a foundation of fluency-driven overconfidence.

The book offers two countermeasures:

Drop wishful thinking and break the plan into concrete tasks
Add a 50% time buffer on top of your original estimate

Build the inevitability of the unexpected into the structure. This resonates with what I wrote in Failure Science — life is too short to experience every failure firsthand on absorbing failure as a system rather than a personality trait.

”2, 4, 6” and confirmation bias

A famous experiment from the book: show people the sequence “2, 4, 6” and ask them to guess the hidden rule.

Most people hypothesize “increases by 2” and then look for evidence that supports their hypothesis — they propose “8, 10, 12” and feel validated. But the actual rule might be “any number larger than the previous one.” If you only try cases that confirm your guess, you will never reach the real rule.

That tendency — collecting only evidence that supports what you already believe — is confirmation bias. Its biggest danger is that it produces conviction, and conviction leads directly to irrational decisions. The placebo effect is a cousin of the same family.

Confirmation bias is also a survival strategy

So why does such a costly bias survive in humans? The book’s answer: cognitive economy.

If we had to rebuild every hypothesis from scratch on every observation, the moment we met a lion in the forest we would freeze trying to verify whether it was really a threat. Fast pattern-based judgment is what made human adaptation possible. Confirmation bias is not a defect — it is a trade-off baked into our cognition.

This connects to what I wrote in What reading really gave me was the habit of thinking from many sides. You cannot remove confirmation bias. You can only build the habit of forcing multiple sides on top of it.

The opposite question — the simplest tool for disconfirmation

To surface confirmation bias, the book recommends one disarmingly simple practice: ask the opposite question.

Right after asking “Am I introverted?”, ask “Am I extroverted?”. The first answer will of course color the second — but just treating both questions equally and seriously is enough to dodge a surprising amount of biased reasoning.

Reading this chapter, I was reminded of A manager’s job is asking, not answering — questions are not soft skills, they are a technology for restructuring a team’s thinking. The opposite question is metacognition in its smallest, sharpest form.

A real example: hypothesis testing and psychological safety

Let me close with the experience the book helped me reinterpret.

At the start of one project, I spent time chatting with each team member individually, asking what they wanted to do in this project. Then I assigned tasks accordingly. My hypothesis: a team rooted in each member’s own intent is stronger than one assigned top-down.

Midway through, one member told me, “I really appreciate that you act on what I actually meant.” The hypothesis was validated; it became a piece of trusted knowledge for me.

After reading Thinking 101, I can describe it more precisely: what I was really doing was asking each member the opposite question. Not just “what do you want to do?” but “what do you not want to do?”. Picking up both halves is what kept the team’s smooth-running narrative from carrying us somewhere no one had really chosen.

Summary

Thinking 101 gives you a way to loosen your own fluency, notice confirmation bias, and welcome disconfirmation.

Fluency: the trap of feeling capable just from watching
Thinking hole: only visible when you try to explain concretely
Plans are too optimistic: break them down, add a 50% buffer
Confirmation bias: the habit of collecting only supporting evidence — and a survival trade-off
Opposite question: the simplest technique to invite disconfirmation

As an engineer and as a team lead, these five lenses raise the quality of everyday hypothesis testing. Just stopping to ask “this smooth mental movie I am replaying — could I actually reproduce it?” is enough to change the precision of a decision.

Failure Science — life is too short to experience every failure firsthand — building a culture that absorbs failure as a system
A manager’s job is asking, not answering — questions as a tool for restructuring a team’s thinking
What reading really gave me was the habit of thinking from many sides — how books grow the habit of self-questioning