AIQ
AIQ
Part of the Who's Responsible? lesson guide. Teaching a different grade? 🔧 Builder (8–10) · 💻 Hacker (11–14) · ⚡ Architect (15–18)
This is a genuinely tricky topic even for grown-ups, so at this age the goal is much smaller than "understand accountability law" — it's simply "notice that blame can be complicated, and that's okay to wonder about." Keep your tone curious and a little mysterious, like you're posing a fun riddle rather than a scary problem.
Gather the class and say, slowly and with a puzzled face: "If a toy robot car bumps into something, whose fault is it? 🤔 Is it the car's fault? The fault of the person who BUILT the car? Or the fault of the person who was riding inside it? Hmmm... this is a REALLY tricky question, and even grown-ups aren't totally sure!"
Do a quick physical warm-up to make it concrete: push a toy car (or a ball, if you don't have one) gently across a table so it bumps into a cup or a small object. Ask: "Whose fault was it that the cup got bumped — the car, or the person who pushed it?" Most children will say "the person who pushed it," which is a great, correct answer for a simple push. Then say: "Right! But what if the car could drive itself, with NO person pushing it? Then who's fault would it be?" Let a few guesses happen — "the car," "the person who made it," "nobody" — and don't correct any of them. Say: "Those are all really good guesses! Today we're going to think about that puzzle together."
A note for this age band: avoid any language like "wrong answer" during this warm-up. Every guess here is a reasonable one, because — genuinely — even adults, judges, and lawmakers are still figuring this exact question out. That's a wonderful, honest thing to tell a five-to-seven-year-old: "this is so tricky that even grown-up rule-makers are still working on it!"
A gentle note before you start: because this lesson is about mistakes and "whose fault" something is, a few children may connect it, quietly or out loud, to a time THEY got blamed for something — a broken toy, a sibling's accident, a classroom mishap. If that comes up, acknowledge it warmly and briefly ("that sounds like it was tricky to figure out too!") before steering back to robots. The lesson is meant to build curiosity about a fun puzzle, not to reopen a child's own memory of getting in trouble — keep the tone light throughout.
Explorer mode moves through the lesson as three little "scenes," each with a handful of pictures and a simple fact attached. Treat each one as a show-and-tell: point at the picture, say the fact in a warm, simple voice, and ask a quick question before moving to the next. Skip any numbers or country names — those are for older students. This lesson earns the "Justice Seeker" badge, so you can frame the whole activity as "today we're being justice seekers, trying to solve a tricky puzzle."
Scene 1 — The Blame Problem. Show a picture of a car (or draw a simple one on the board). Say: "Remember our puzzle? If a self-driving car — a car that drives ALL BY ITSELF, with no driver — bumps into something, who's fault is that? Is it simple, or is it tricky?" Nod along and say: "It's tricky! It might be a little bit the car maker's fault, a little bit the fault of whoever's watching it, and sometimes nobody's totally sure. That's why we need JUSTICE SEEKERS like you to think carefully about these puzzles!" Then show a picture of a scale (like the kind that balances) and say: "This is called a 'scale of justice' — it's a symbol that means fairness. Being fair means really trying to figure out what happened before deciding whose fault something is, instead of just guessing fast."
Scene 2 — Transparency (the "explaining" scene). Say: "Some robot helpers are like a mystery box — even the people who BUILT them can't always explain exactly why the robot picked one answer instead of another! That's called a 'black box' — not because it's really a black box, just because it's a mystery." Then say: "So smart people are working really hard to build robot helpers that CAN explain themselves — like a robot that says 'I picked this answer because of THIS reason!' instead of just staying quiet." Ask: "Which robot do you think is more fair — one that explains its answer, or one that stays a mystery?"
Scene 3 — Rules & Laws. Say: "Because robot helpers can make mistakes, grown-ups all around the world are writing RULES for how robots should act — like classroom rules, but for computers! Some countries have made strict rules, some are still writing theirs, and grown-ups everywhere are trying to agree on rules that keep everybody safe." Close the activity by asking: "So if robot rules are still being written, whose job is it to keep thinking carefully and asking good questions about robots?" — guide them toward "everybody's job, even ours!"
Expect a child to ask something like "so is it ever the robot's fault?" A good, honest answer for this age: "A robot can't really be 'in trouble' the way a person can, because it doesn't choose things the way you do — so when something goes wrong, we always look for the PEOPLE behind the robot: who built it, who's using it, who's supposed to be watching it." This plants the seed for the more precise ideas older students will learn without overclaiming anything at this age.
You can make Scene 2 more physical and memorable with a quick game: whisper a simple instruction into one child's ear (like "hop twice"), then have that child act it out without explaining why. Ask the class: "Do you know WHY they hopped twice?" They'll say no. Then whisper it again, but this time have the child say it out loud before acting: "I'm hopping twice because the teacher told me to!" Ask: "Which one helped you understand better — the silent hop, or the explained hop?" This gives them a hands-on feel for the difference between a mystery decision and an explained one, which is exactly what Scene 2 is about.
Timing note: at a relaxed pace with a class of 20–25, including the optional hopping game, this runs about 10–12 minutes. If attention starts to drift during Scene 3, it's fine to shorten the "rules around the world" part to one sentence and move straight to the discussion or quiz — the important idea to protect is Scene 1's "it can be tricky, and that's okay to think about."
Three or four questions is plenty at this age — watch the room and skip ahead if energy fades.
Do this quiz together as a group, out loud — this age benefits from talking it through rather than answering silently. For each answer choice that isn't correct, it can help to briefly say why it's silly rather than skipping past it, since this age enjoys hearing why something doesn't fit.
Close with: "Today you were Justice Seekers! You learned that when something goes wrong with a robot helper, it can be tricky to know whose fault it is — and that's why grown-ups are still writing rules to keep robots safe and fair. Great detective work!"
A quick call-and-response to lock in the idea: you say "Is it always easy to know whose fault it is when a robot makes a mistake?" and the class shouts back "No, it's tricky!"; you say "So what should a good robot helper always be able to do?" and the class shouts back "Explain why!"
Extension activity (10–15 minutes): Hand out paper and crayons and have each child draw "a fair robot helper" — one that always explains its answers. Ask each child to describe one thing their robot explains and why that makes it fair. If a drawing shows a robot that "just knows everything and never has to explain," gently ask, "but how would we know if it made a mistake?" to nudge the idea back toward explaining and checking.
A simple alternative: act out a tiny "whose fault is it?" puppet show using a toy car and a toy figure. Bump the car into a block, then ask the class to help decide together — was it the car, the person who built it, or the person riding in it? Let them vote by raising hands for each option, then remind them: "See? Even you had different guesses — that's how tricky this puzzle really is, even for grown-ups!"
If you have a few extra minutes and want to send the idea home with families, suggest each child ask a parent or older sibling that evening: "Have you ever used something with a computer helper inside it — like a phone that unlocks by looking at your face, or an app that picks a video for you?" The next day, spend two or three minutes letting volunteers share what they found out. This gently extends the lesson's "notice the computer helpers around you" idea beyond the classroom without requiring any homework sheet or written work, which fits this age band far better than a take-home worksheet would.