AIQ
AIQ
Part of the How Computers Think lesson guide. Teaching a different grade? 🌈 Explorer (5–7) · 💻 Hacker (11–14) · ⚡ Architect (15–18)
Open with a straight face and a dramatic pause before "secret":
"Here's a secret: computers don't actually THINK. They follow instructions — really, really fast. But the way they process information is totally different from your brain!"
Ask the class to predict: "If a computer isn't thinking, what IS it doing all day?" Take two or three guesses without confirming or correcting yet — you'll answer it properly in the activity. Then write four words on the board that the lesson will keep coming back to: Brain, Computer, Speed, Instructions. Tell them: "By the end of today you'll be able to say exactly what a computer is fast at, and exactly what it's bad at — and it might surprise you."
Axiom (the Builder-mode mascot) frames the lesson in-app the same way — as a "secret" being revealed rather than a fact being delivered. It's worth matching that energy in your own delivery: this age group responds well to being let in on something that sounds counterintuitive, and "computers don't actually think" reliably produces a few surprised or skeptical faces worth building the rest of the lesson around.
Builder mode gets the full three-scene version of the lesson, with Axiom guiding them through in the app. Use the scenes as checkpoints for your own explanation and questions as students move through each one.
Explain that a computer only ever knows ON and OFF — like a light switch — and that we call ON "1" and
OFF "0." This is called binary. Show them the fun fact from the app: the letter A is stored
as 01000001. Ask: "If one letter takes 8 of those on/off switches, how many switches do you
think it takes to store this whole sentence?" (A lot — that's the point.) Then connect it to photos: a
digital photo is really millions of tiny colored dots called pixels, and each one is stored
as numbers, not as a "picture" the way the computer experiences it. Mention that a phone has billions
of tiny switches (transistors) doing this switching, which is what makes it possible to do so much so fast.
A useful visual: hold up your phone and say, "Every single thing this screen has ever shown you — every
photo, every game, every video — was, underneath, nothing but 1s and 0s being rearranged at incredible
speed. The 'picture' only exists once the screen lights up the right pixels in the right colors; before
that, inside the chip, it was just numbers." A concrete way to test whether this has landed: ask the class,
"If I zoom WAY into a photo until it looks blurry and blocky, what am I actually looking at?" Guide them
toward "the individual pixels, each one just a number for a color," rather than "the picture getting worse."
Zooming into any photo on a classroom device and showing the blocky squares up close makes this concrete
rather than abstract, and most students find it genuinely surprising the first time they really look.
Contrast the numbers directly: a computer can do about a billion calculations a second; a human brain does roughly ten simple math calculations a second. But flip it — ask the class to recognize a classmate's face from across the room. "That took you maybe a tenth of a second. It took AI researchers decades to get computers to do that reliably." Then do the imagination check: "Picture a purple elephant flying a spaceship." Everyone can do it instantly; a computer can only work with images and ideas it's already been given. Finish with emotions: a computer can be trained to notice a smile in a photo, but it does not actually feel happy — there's a real difference between detecting an emotion and having one. If a student pushes back with "but my phone knows when I'm sad because of my voice," that's a great moment to draw the line precisely: the phone can be trained to notice patterns in a voice that usually go along with sadness (a slower pace, a quieter tone) — matching a pattern is not the same thing as feeling the sadness itself, any more than a thermometer "feels" hot when it reads a high number.
Walk through the cycle with a concrete example the class already knows, like typing a message on a phone: typing the letters is the input, the phone checking spelling and getting the message ready is the process, and the message appearing on the screen (and arriving on a friend's phone) is the output. Emphasize that this loop repeats constantly, millions of times a second, and it's the pattern behind every app, game, and website they've ever used — including the very app they're using right now.
Have the class supply a second example on their own before moving on — a game controller button press (input), the game engine deciding what happens next (process), and a character jumping on screen (output); or a search box (input), the search engine looking through its results (process), and the list of links that appears (output). Having students generate their own example, rather than only hearing yours, is what makes the pattern stick rather than just being a phrase they memorized.
Run the lesson's own sorting game as a quick class round before the quiz. Read out each pair and have students vote with a thumbs-up (computer) or thumbs-down (brain): "billions of calculations a second" (computer), "understanding a hug" (brain), "storing a photo as pixels and numbers" (computer), "daydreaming in class" (brain), "following input → process → output" (computer), "real feelings" (brain). Most students will get these quickly by now — use any disagreement as a chance to ask "why do you think that?" rather than just giving the answer, since defending the reasoning is where the real learning happens.
Where Builders tend to get stuck: a few students will insist that fast pattern-matching (like a spam filter, or a game character that "knows" to chase you) counts as understanding, because it reacts appropriately. That's a fair intuition to take seriously rather than dismiss — the honest answer is that reacting correctly and understanding are hard to tell apart from the outside, which is exactly why this lesson focuses on what's happening underneath (fixed instructions on 1s and 0s) rather than on how convincing the outside behavior looks.
These work well as a think-pair-share: give students thirty seconds to think alone, thirty seconds to compare with a partner, then open it up to the whole class. That structure gets more honest answers than cold-calling, especially on the questions that ask students to admit uncertainty.
Students take this in the app individually or in pairs, with the options shuffled so it's worth walking through the reasoning rather than the exact wording of each choice — the ideas below are what to reinforce regardless of how the options are ordered on a given student's screen.
Close by returning to the board words: "Computer and Brain are both amazing, but at totally different things. Computers win on Speed and following Instructions exactly. Your brain wins on imagination, emotion, and understanding meaning. Keep that in mind every time you use an app this week — is it being fast, or is it actually understanding you?"
Extension activity — "Write your name in binary": Give each student a simple A–Z to 8-bit binary reference chart (or have them look up just the first letter of their name). Have them write the binary code for their initials on an index card, then trade cards with a partner and try to decode each other's initials back into letters. Finish by asking: "Now imagine doing that for every letter in a whole book — that's genuinely what's happening inside every device you own, just billions of times faster than we just did it by hand."
If there's extra time: have pairs list three apps or devices they used this morning and, for each one, name the Input, the Process, and the Output — brushing their teeth with an electric toothbrush timer, a school bell schedule, a rice cooker that clicks off. Not every example needs a computer inside it; the point is to notice how often this three-step shape shows up.