🔎 Spotting the Odd One Out
How a computer notices that something does not look right.
🔥 Warm Up — 2 minutes
Read out a list: samosa 20, chai 10, bus 15, aeroplane 40,000, pencil 5. Ask which one jumped out, and why.
“You just did what a bank computer does all day.”
🤖 The Activity — 15 minutes
Write out a week of pretend spending for an imaginary person — ten small everyday amounts. Then add three odd ones somewhere in the middle: something huge, something at 3 in the morning, something in a country they have never visited.
Your child is the detective. Which ones look wrong, and why? The why matters more than the which.
Then the twist that matters: invent a perfectly innocent reason for each odd one. The huge one was a school trip. The 3am one was a birthday call abroad.
🧩 The Twist — 5 minutes
Ask: “If the computer blocks the card every time something looks odd, what happens to the person on the school trip?”
They get stuck, with no money, far from home. So a good system usually asks rather than blocks — a message, a question, a code — and only stops things when it is really sure.
Detective Badge
Learned that suspicious is not the same as guilty
Parent Notes — tap to expand
▼Anomaly detection as pattern comparison, and the real cost of a false alarm — that blocking a legitimate person is a harm too, not a safe default.
- What is the cost of the computer being wrong in each direction?
- How would you check, without blocking the person completely?
- What makes something ‘normal’ for one person and odd for another?
Children reach for “block it” instantly. Getting them to feel the cost of the false alarm is the actual lesson, and it transfers well beyond money.
Good moment to explain, plainly, that a real bank will sometimes send a message asking if a payment was really you — and that the answer is always to check with a parent first, never to tap a link in the message.