On this page
Every JEE and NEET student knows the feeling: you see the answer key, and the mistake was not hard physics but a slip you would have caught if you had looked again. Daniel Kahneman's work on fast and slow thinking gives a useful way to think about these errors, as long as you take the parts the research supports and leave the rest.
What is fast and slow thinking?
Kahneman shared the 2002 Prize in Economic Sciences "for having integrated insights from psychological research into economic science, especially concerning human judgment and decision-making under uncertainty" (Nobel Prize, 2002 summary). In his prize lecture he said the work cited by the committee was done jointly with Amos Tversky.
In that lecture he described "two generic modes of cognitive function". The operations of System 1 "are fast, automatic, effortless, associative, and difficult to control or modify". Those of System 2 "are slower, serial, effortful, and deliberately controlled" (Kahneman's prize lecture, PDF). One job of System 2 is to monitor what System 1 produces, and Kahneman and Shane Frederick had suggested that this monitoring is "normally quite lax". He later popularised the ideas in *Thinking, Fast and Slow*, first published in 2011 (Open Library record).
The bat-and-ball problem
The lecture's best-known example comes from Frederick: "A bat and a ball cost $1.10 in total. The bat costs $1 more than the ball. How much does the ball cost?" Almost everyone reports an initial pull towards "10 cents". Kahneman reported that 50% of Princeton students (47 of 93) and 56% of University of Michigan students (164 of 293) gave the wrong answer. "Clearly, these respondents offered a response without checking it."
Check it the System 2 way: if the ball costs x, the bat costs x + 1, so 2x + 1 = 1.10 and x = 0.05. The ball costs 5 cents. Frederick later published a three-item Cognitive Reflection Test built from puzzles of this kind, a measure of the ability or disposition to "resist reporting the first response that comes to mind" (Frederick, 2005).
What applies to exams
Exam questions often contain bat-and-ball traps: a number that splits neatly, a problem that resembles one you have solved, an answer option that matches your first guess. Common examples:
Using v = u + at when acceleration changes with time.
Taking a ratio the wrong way up (T₁/T₂ instead of T₂/T₁).
Missing "not" or "incorrect" in the question.
Adding vectors as plain numbers.
These are the places where a fast answer feels right and the slow check never runs.
What doesn't apply, or didn't hold up
Making text hard to read does not switch on careful thinking. A 2007 study reported that degraded fonts improved reasoning. When researchers later pooled the best-known experiment of this kind with 16 attempts to replicate it, they found "no effect on solution rates" (Meyer and colleagues, 2015).
"Never change your first answer" is a myth. A 2005 paper by Kruger, Wirtz and Miller noted that virtually all research on the question finds most answer changes are from wrong to right, and people who change answers usually improve their scores. The authors argue the belief survives because changing a right answer to a wrong one leads to more regret and is remembered better (Kruger, Wirtz and Miller, 2005). Change an answer when you have a reason, not just a feeling. If your exam has negative marking, see when guessing is worth it.
A System 2 checkpoint routine
Use three triggers to decide when to check, and three checks to run.
Triggers (any one is enough):
The answer came to you instantly.
The problem looks like one you have done before.
The numbers worked out suspiciously neatly.
Checks (pick the fastest that fits):
Substitute back. Put your answer into the original condition, as with 5 cents + $1.05 = $1.10.
Units and dimensions. Our 30-second dimensional analysis check shows how.
Extreme case. Set a mass to zero or an angle to 90° and see if the answer behaves sensibly.
Practise the routine during mock tests, not just on exam day, so it runs without much effort. In the last minutes of a paper, use our priority order for checking answers. After each mock, sort your wrong answers into "didn't know" and "didn't check".
When the same kind of slip keeps coming back in one topic, the Fermi Problem Library has worked problems with a step-by-step solver that explains the reasoning rather than printing an answer, so you can compare your method one step at a time.
Next mock, mark every question where a trigger fired, and see how many of your errors sit on those questions.
