Fast and slow thinking

You will be able to describe the two modes of thinking in Kahneman's Thinking, Fast and Slow and when each misleads.

Try this before reading on. A kopi and a slice of kaya toast cost S$1.10 together. The toast costs S$1.00 more than the kopi. How much is the kopi?

Most people hear "ten cents" in their head almost immediately. It feels right. It is wrong. If the kopi were ten cents, the toast would be S$1.10 and the total S$1.20. The kopi is five cents, the toast S$1.05, and together they make S$1.10. The prices are silly, but the puzzle is a local version of one Daniel Kahneman uses, with a bat and a ball, in Thinking, Fast and Slow. What it shows is not that people are bad at arithmetic. It shows that a quick answer arrives first, feels confident, and often goes unchecked.

This module is about the patterns behind that kind of mistake. It starts with Kahneman's account of how they happen.

Two ways of thinking

Kahneman describes the mind as if it had two systems. He is clear that these are a way of talking, not two physical parts of the brain, but the picture is useful.

System 1 is fast, automatic and effortless. It reads faces, finishes familiar sentences, drives a car on an empty road and tells you "ten cents" before you have decided to think about the kopi. It works by association and pattern, and for familiar situations it is usually right. An experienced nurse who senses a patient is getting worse, or a seasoned accountant who feels that a figure looks off, is drawing on System 1 trained by years of practice.

System 2 is slow, deliberate and effortful. It is what you use to work out S$1.10 minus S$1.00 divided by two, fill in a tax form or compare two insurance plans line by line. It can check System 1's answers, but checking takes effort, and System 2 is, in Kahneman's word, lazy. Most of the time it accepts whatever System 1 offers without looking closely.

That is where the trouble starts. System 1 does not flag its own guesses as guesses. The answer "ten cents" arrives feeling just as solid as the answer to "what is two plus two". Unless something prompts System 2 to step in, the fast answer becomes your answer.

What you see is all there is

Kahneman gave one of System 1's habits a memorable name: "what you see is all there is". System 1 builds the most coherent story it can from the information in front of it, and it does not ask what is missing. The less you know, the easier it is to build a neat story, so confidence can rise as information falls.

Mei, a project manager at an IT services firm, sees it in hiring. A candidate gives a fluent, confident interview with a couple of impressive stories. By the end, the panel feels sure he is excellent. Nobody has checked his references, asked how his past projects actually ended or tested the skill the role needs most. The story they built from forty-five minutes of conversation feels complete because the missing pieces never came up.

You can see the same pattern in the earlier modules. A single success story, a chart with a cropped axis or a report with no base rate all give you a tidy picture, and System 1 runs with it. Asking "what is not here?" is a System 2 question. It does not come naturally, which is why the course keeps asking you to make it a habit.

Knowing is not enough

Here is the uncomfortable part. Learning about these biases does not make you immune to them. Kahneman himself wrote that decades of studying them had done little to improve his own intuitions. You can read this lesson, understand it perfectly and still hear "ten cents" next time a similar puzzle comes along.

The reason is that System 1 works whether or not you are paying attention. You cannot switch it off, and in the moment, a biased judgement feels exactly like a good one. Trying harder to notice is not a reliable defence.

What works better is process. Kahneman's own advice is that organisations are better placed than individuals to catch these errors, because they can build checks into how decisions are made. For you, that means small, routine steps that force System 2 to look at the decisions that matter. Writing your estimate before you hear others, asking for the base rate, checking how similar projects turned out. The next two lessons cover specific biases, and lesson 5.4 turns them into a short checklist you run before important decisions.

When to slow down

You cannot and should not run every decision through System 2. Choosing lunch, replying to a routine email or picking a route home are fine on autopilot. Slowing down is worth it when three things come together: the stakes are high, the situation is unfamiliar or you get little feedback on whether you were right, and you notice a strong, quick feeling about the answer.

That last signal is useful. A quick, confident judgement about something important and unfamiliar, such as a candidate, a big purchase or a new supplier, is exactly when System 1 is most likely to be filling gaps with a story.

Mei's panel would have done well to pause at the end of the interview and ask what they still did not know. Your own day is full of fast calls like theirs, most of them harmless, and the activity below asks you to catch a few as they happen.

Note three decisions you made quickly today and mark which, if any, deserved slower thinking.

Course

Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).