AIQ AIQ
How Computers Read · Lesson 2.1.3

Teaching "How Computers Read" to Explorer mode (ages 5–7)

Part of the How Computers Read lesson guide. Teaching a different grade? 🔧 Builder (8–10) · 💻 Hacker (11–14) · ⚡ Architect (15–18)

Hook & Warm-Up

Hold up a picture book, or point to any writing in the room — a poster, the classroom word wall, a cereal box. Ask the class to read a word out loud together, all at once, like a cheer. Then say, with a big surprised voice, cupping your hand to your ear as if you've just heard something shocking:

"You can read these words! But can a computer? 📖 Nope! Computers see words as NUMBERS, not letters. Weird, right? Let's find out how!"

Let that sit for a second — "weird" is exactly the reaction you want. Ask: "If I showed a computer the word CAT, do you think it sees C-A-T, like you do?" Take a few guesses; some students will confidently say yes, which is fine — that's the exact assumption today is going to gently overturn. Then say: "Nope — a computer turns every word into secret numbers first, before it can do anything with it at all! It's a little bit like a computer only speaks a secret spy language, and every word we say has to get translated into that spy language of numbers first."

Bring it to life with a tiny demonstration: write the letter "A" on the board, then next to it write a random number like "7." Say: "Pretend to the computer, A means 7. Every letter and every word gets its own number, kind of like a secret code. Today we're going to be computers for a little while, and turn some words into secret number-code ourselves."

Keep the energy playful rather than technical — the goal at this age is simply: words become numbers before a computer can use them, and that's a strange, fun fact worth remembering, not a mechanism they need to explain back to you in detail.

Main Activity

Open the lesson together on the shared screen. It walks through three little scenes, and you'll retell each one as a simple story rather than reading the on-screen text word for word. Throughout, keep coming back to one running phrase students can chant with you: "words become numbers!"

Scene 1 — Words as Numbers 🔤. Say: "A computer can't read C-A-T. So first, it chops the word into little pieces — like breaking a cracker in half — and turns each piece into a secret number. Every single word in every single book gets its own secret number code!" Then play the "close words" game: say two words that mean almost the same thing, like happy and joyful, and ask "do you think these get NUMBER codes that are close together, like neighbors on a street, or far apart, like different countries?" (Answer: close together — the lesson's own line is "similar words get similar numbers.") Then try a pair that means very different things, like happy and rock, and ask again (answer: far apart, like different countries). Do one more round with sad and unhappy (close together) versus sad and banana (far apart) so the pattern really sticks before moving on. If a student asks how a computer "knows" which numbers to pick, keep it simple: "It practiced with a HUGE pile of books and sentences, and figured out on its own which words show up in similar spots — nobody told it the answer directly."

Scene 2 — Understanding Text 💬. Say: "Once words are secret numbers, a computer can start noticing things about them, kind of like a detective looking for clues." Give two very concrete examples students will recognize from home: "If your mom's or dad's phone finishes typing a word for them before they're done — like they type 'goo' and it guesses 'good morning' — that's because it learned which number-patterns usually come next, from watching TONS and TONS of typing from lots of people." And: "If an email says 'YOU WON A FREE PRIZE CLICK NOW,' a smart helper can often tell that's junk mail (called spam), because it's seen that exact kind of number-pattern many, many times before in real junk mail people have flagged."

Scene 3 — Language AI 🌐. Say: "Some smart helpers can even change one language into another — like turning 'kumusta' into 'hello' — by comparing the secret numbers for words in both languages! It's found that the number for 'kumusta' and the number for 'hello' are close together, like matching puzzle pieces." Add: "And a chatbot, like a computer you can type questions to, writes its answer one little word-piece at a time, always guessing 'what number usually comes next?' — over and over, super fast, until the whole answer is written." If a student asks how a chatbot can write a whole paragraph so fast, say: "It's doing that guess-the-next-piece trick many, many times every single second — way faster than you or I could ever write!"

Finish with the practice round together as a simple "AI or not AI" point-and-shout — hold up a picture or say the item, and have the whole class shout "AI!" or "not AI!" together: 🤖 a chatbot (AI — it guesses your words), 📖 a paper book (not AI — the words never change, no matter how many times you read it), 🌍 a translate app (AI — it compares number-codes between languages), ✏️ a pencil writing (not AI — it's just you moving your hand), 📝 phone autocomplete (AI — it guesses the next word), 📨 a mailed letter (not AI — someone just carries it to your house).

Before moving to the quiz, do a thirty-second "check for understanding" recap with the whole class chanting together: hold up one finger and say "Computers turn words into...?" and let them shout "NUMBERS!" Hold up a second finger and say "Words that mean the same thing get numbers that are...?" and let them shout "CLOSE TOGETHER!" This tiny call-and-response takes almost no time but makes sure the two big ideas of the lesson are locked in before the quiz starts.

Discussion

Quiz Walkthrough

Computers see words as... (🔢 Numbers! / 🎨 Colors / 🎵 Music / 👃 Smells)
🔢 Numbers! A computer has no way to see letters the way we do — the very first thing it does with any word is turn it into a secret number code. If a student picks "Colors" or "Music," gently point out those are fun guesses but a computer doesn't have eyes or ears the way we do — it only ever works with numbers, no matter what it's given.
Your phone predicts words by... (Learning what words go together / Asking you / Reading your mind / Making completely random guesses)
Learning what words go together. It's watched huge numbers of real sentences before, so it has a good guess about which word usually comes next — it's not magic, and it's not random. "Reading your mind" is a fun wrong answer to talk through: ask the class "does your phone actually know what you're thinking, or is it just really good at guessing from patterns?"
Which uses reading A.I.? (🔦 Flashlight / 💬 Chatbot / 🪑 Chair / 🚲 Bicycle)
💬 Chatbot. A flashlight, a chair, and a bicycle all do one fixed job and never change, no matter how many times you use them. A chatbot reads your typed words as numbers and guesses a reply, word by word — it's the only one on the list that's actually learning and guessing.
Can A.I. understand stories like you? (No — it just matches patterns in numbers / Yes / Only with pictures / Only short ones)
No — it just matches patterns in numbers. Even when an answer sounds nice and friendly, the computer isn't feeling or understanding the story the way you do when you read or hear one — it's comparing number-patterns it has seen many times before. This is worth saying slowly and repeating; it's one of the most important ideas in the whole lesson, and it comes back again and again in later AIQ lessons.

Wrap-Up & Extension

Close with: "Every time you type on a phone or talk to a smart helper, remember — it turned your words into secret numbers first! You know a secret about computers that a lot of grown-ups don't even think about. Next time someone's phone finishes their sentence for them, you can tell them exactly why!"

Extension activity — "Make Your Own Secret Code": Give each student (or pair) a short list of 5 simple words (cat, dog, happy, sad, run). Have them invent their own made-up number for each word, with one rule: words that mean similar things (happy/glad) should get numbers that are close together, and words that mean very different things (cat/sad) should get numbers far apart. Let a few students share their codes and explain their choices out loud — ask "why did you pick numbers that are close together for those two?" to make sure the reasoning, not just the number, comes out.

If there's extra time, add a second round: give the class one brand-new word they invent together (a silly made-up word like "flooberish") and ask them to decide, as a group, which of the five original words it should sit closest to in number-space, and why. This turns the abstract "similar words get similar numbers" idea into something they physically built and argued about themselves, and easily stretches the 10–15 minute core lesson into a full 30–40 minute class period.

If time is shorter, a simpler backup extension is a "spy words" hunt: for the last five minutes, walk (or have students walk) around the room pointing at anything with writing on it — a poster, a book spine, a name tag — and asking "if a computer looked at this, would it see letters, or would it first have to change this into numbers?" The answer is always "numbers first," but repeating it against real objects in the room, rather than just the screen, helps the idea stick past the end of the lesson.

← Lesson overview ← How Computers Hear (Explorer) Sensors and Data (Explorer) →