AIQ
AIQ
Part of the AI in Transportation lesson guide. Teaching a different grade? 🔧 Builder (8–10) · 💻 Hacker (11–14) · ⚡ Architect (15–18)
Gather students on the rug or in a circle where everyone can see you. This age group runs on your energy more than your words, so lean into the excitement of cars and robots.
"Boys and girls, raise your hand if you've ever ridden in a car! [Let them wave hands, maybe ask one or two what kind of car.] Now here's something amazing — did you know some cars can drive ALL BY THEMSELVES? No driver touching the wheel!"
Pause for the gasps, then lean in like you're sharing a secret.
"Cars that drive themselves! 🚗 How does a car know where to go without a driver? It has SPECIAL EYES made of cameras and lasers!"
That's the app's own opening line for this age band, and it works well said out loud almost exactly as written — the all-caps "SPECIAL EYES" is meant to be said with big, wide-eyed emphasis. Follow it with a quick physical bit: hold your hands up like binoculars over your own eyes.
"A self-driving car doesn't have eyes like you and me. Instead it has cameras — like a camera that takes your picture — all around it, so it can look every direction at once! And it has something even cooler called lasers, that bounce off everything nearby to figure out exactly how far away things are, like a bat using its ears in the dark!"
Expected reaction: students pretending to be cars with camera-eyes, maybe some car noises. Let it happen for a few seconds — it primes them for the activity.
One more warm-up beat that lands well with this age group: ask, "Do YOU have super senses like a self-driving car?" and let a few students answer. Point out that our eyes are actually amazing — they see color, movement, and depth all at once, without any wires or batteries — but they can't see in total darkness or through fog the way a laser can. This gently plants the idea that the car isn't "better" than a person, just different, which matters for the honest, no-scary-robots tone this whole lesson should keep for five- to seven-year-olds.
The in-app lesson for this age band moves through three scenes — Self-Driving, Traffic, and Future Travel — each showing four things and asking "does this use AI or not?" Walk through the idea live before handing over devices, using the same four things per scene so the app feels familiar rather than brand new.
Hold up (or draw) a simple car shape on the board.
"This car has cameras all around it, like a hundred tiny eyes! And it shoots out invisible laser beams to measure how far away everything is — the road, other cars, even a squirrel! Its brain — that's the AI part — has to decide super fast: should I stop? Should I turn? It decides that thousands of times every single second!"
Then hold up a real compass or draw one.
"But THIS — a compass — does NOT use AI. It just points north because of magnets in the ground. It never changes its mind, never decides anything. It just points the same way, always."
Expected response: kids pointing fingers like a compass, or making "beep boop" camera sounds for the car. Ask "which one is thinking, the car or the compass?" — nearly everyone will say the car, which is the concept you want them to land on.
A good follow-up if time allows: ask "does the compass ever get it wrong, or ever surprise you?" Most will say no — it just always points the same direction. Then ask "does the self-driving car's brain ever have to think hard, or make a tricky choice?" Guide them toward yes — like if a ball rolls into the street, the car's brain has to decide fast what to do, while the compass would just keep quietly pointing north no matter what happened around it.
"Have you seen a stop light change from red to green? Some stop lights have a little computer brain! It watches how many cars are waiting and says 'okay, let THIS street go first, there are more cars here!' That's a smart traffic light using AI. But a plain stop sign? It just stands there. It can't watch anything or decide anything — it's just a metal sign!"
Ask two volunteers to be "smart light" and "stop sign" — the "smart light" volunteer looks both ways and shouts "more cars here, go!" while the "stop sign" volunteer just stands still holding up a hand. This makes the contrast physical and memorable for five- to seven-year-olds.
"Some robots deliver packages! They roll along the sidewalk all by themselves, using cameras to make sure they don't bump into people or trash cans. There are also big smart trains that can even drive themselves along their tracks, and flying taxis that might one day zoom through the sky! But you know what doesn't need any AI brain at all? A regular bicycle! A bike doesn't think — YOU are the smart part, pedaling and steering and deciding where to go!"
This is a nice moment to affirm that not needing AI isn't a bad thing — bikes are simply a different, human-powered kind of transportation, and that's something to celebrate, not a losing comparison.
If your students have ridden in a tricycle or jeepney, this is a natural moment to bring it up: "Does a tricycle driver have a computer brain helping them drive, or is it just the driver deciding everything?" (Just the driver — no AI.) This connects the lesson to something most Filipino students see every single day, and reinforces that "not using AI" describes an enormous amount of everyday transportation, not just old-fashioned bicycles. Some students may mention "self-driving" toys or games they've seen — it's fine to say "some of those are real and being tested right now, and some are just pretend for now," without going deeper into which is which at this age.
Now hand out devices and let students tap through the three scenes themselves. Circulate and ask "does this one have a brain, or not?" as they go, pointing at whichever item is on their screen.
If you have a few extra minutes before or after the app portion, try a quick group game: call out familiar things one at a time — "a jeepney," "a traffic light with a countdown timer," "a bicycle," "a phone map that tells you the fastest way home" — and have students stand up if they think it "has a brain that decides things" and stay seated if it doesn't. This works especially well with things students see every day in the Philippines, like a tricycle (no brain — the driver decides everything) versus a ride-hailing app suggesting the quickest route (yes, a computer brain helped pick that route).
Keep circling back to one simple test the whole lesson hangs on, and say it often enough that students start saying it back to you unprompted: "Does it notice what's happening around it, and change what it does because of that? If yes, it probably has a computer brain helping it. If it always does the exact same thing no matter what, it doesn't." That one sentence is doing almost all of the conceptual work in this lesson, for every scene.
Keep this short and playful for this age band — five minutes of talking is plenty before attention drifts. Sit in a circle if you can, so it feels like a conversation rather than a quiz.
There are no wrong answers here — the goal is simply to get students saying the ideas out loud in their own words, since that's what makes a five-year-old's understanding stick, far more than passively listening does.
Close with: "Today you learned that some cars, lights, and robots have a little computer brain that helps them see and decide things — cameras for eyes, lasers to measure distance, and quick thinking to keep everyone safe. But remember — a compass, a stop sign, and a bicycle don't need any of that. They're simple, and that's just fine!" Consider ending with a call-and-response: you say "Camera-eyes!" and students mime holding binoculars to their eyes; you say "Laser-eyes!" and they mime bouncing a beam off something with their fingers; you say "No brain needed!" and they shrug and shake their head. Repeating the three ideas as a physical action, right before you close the lesson, is one of the simplest ways to make the ideas stick for this age group.
Extension activity: Give each student a piece of paper with a simple road drawn on it (a straight line with a few turns) and have them draw "camera eyes" all around a car shape wherever they think it needs to look — front, back, sides. Then ask a few students to explain out loud why their car needs an eye pointing that direction ("so it can see the school bus behind it," "so it doesn't hit the fence"). This turns the abstract idea of 360° sensing into something they've physically drawn and can explain in their own words. For a class that finishes quickly, have them add one more drawing: a little robot delivery box with wheels, and ask them to draw where ITS eyes should point too — most will realize it mostly needs to look forward and down, since it's watching the sidewalk in front of it rather than looking all around like a car does, which is a nice, gentle preview of the idea that different vehicles need different kinds of "seeing" for the job they do.