Skip to content
Computing · CONCEPTUAL · Ages 7–9

Data and Information for Computers

What data is: information that computers use — numbers, words, pictures, sounds; everything a computer knows comes from data that people give it

Lesson: Data and Information — What Computers Actually Know

Subject: Computing · Domain: Artificial Intelligence · Age band: 7–9 (adapted for gifted 5–6) · Type: Conceptual Centrality: Foundational · Taxonomy ID: mt_kH1DzOPsXG Standards: None specified (domain is emerging in K–12 frameworks) Tailored for: Gifted 5y9m, IQ 125–130+, asynchronous — strong verbal/math, developmentally 5

Start here. Your son likely already senses that phones and tablets "know things." This lesson reframes that intuition: computers don't know — they're given. That single shift is the whole point. If he can already articulate "computers only have what people put in," skip to Stretch.


Why this matters

This is the bedrock under everything that follows in AI and computing — patterns, machine learning, recommendation systems, privacy. None of it clicks unless your son first grasps that a computer is, at its core, a container for data that someone chose to give it.

This matters beyond computing too. It's the seed of media literacy: where did this information come from? A five-year-old who starts asking "who gave the computer this?" is asking the right question about every screen he'll encounter for the next eighty years.

For an asynchronous child, the trap is procedural mimicry — he can say "computers use data" without really feeling what that means. The goal isn't the definition; it's the felt sense that computers are passive receivers, not knowers.

Learning objective

Your son will understand that everything a computer "knows" — numbers, words, pictures, sounds — is data that people created and gave it, and that without that data, the computer knows nothing.

You'll know he's there when he can say something like: "A computer only has what someone put in it. If nobody gave it the data, it doesn't know."

Before you sit down together

Materials

  • A smartphone or tablet — the device he already sees daily; concrete anchor
  • 2–3 printed family photos (or pulled up on screen) — images are data; this makes it visible
  • Sticky notes or index cards (6–8) — to physically represent "pieces of data"
  • Crayons or markers — for the encoding extension
  • Optional: a photo zoomed way in so individual pixels are visible — powerful for Stretch

You probably already have all of this. The point isn't fancy materials — it's making "data" something he can hold and move.

Best time of day for this lesson

Some parents find mid-morning — after breakfast energy has settled but before the post-lunch dip — works well for conceptual work. His brain is freshest when his body is fed and rested.

You might avoid: - Right before a meal (attention drifts to hunger) - Late afternoon (executive function fatigue — especially in gifted kids who've been holding it together all day) - Right after passive screen time (hard to shift from watching to thinking)

If he's wound up or tired, this isn't the lesson. Come back tomorrow.


Activity: "What Does the Phone Know?"

A 15–20 minute exploration in four phases. Move at his pace — if he's lit up, linger; if he's glazed, cut and return later.

Phase 1 — Introduce (3–4 minutes)

Start with the phone or tablet in front of you both.

Parent: "I want to show you something most people don't think about. This phone — what does it know?"

Let him answer. He may say "everything" or "Siri knows the weather" or "it knows my games." That's perfect — it's the starting intuition you're about to gently complicate.

Parent: "Here's the secret: the phone doesn't actually know anything. It's like a really fast, really obedient box. Everything it has — the weather, your games, the photos — somebody had to give it that. We call that data."

Write DATA on a sticky note. Put it on the table.

Parent: "Data just means information someone gave the computer. Numbers, words, pictures, sounds — all data."

Phase 2 — Explore (6–8 minutes)

Make data tangible. Pull out the family photos.

Parent: "Is this picture data?"

Let him puzzle. The right answer is yes — but let him sit with it. Then:

Parent: "It is. Someone — maybe you or me — took this photo, and the phone turned it into data and stored it. The phone didn't make the picture. We gave it the picture."

Hand him a sticky note and marker.

Parent: "Can you think of three things you've given a phone or tablet today? Things you typed, or said, or took a picture of?"

He might name: a search, a photo, a voice command, a game score, a message to Grandma. Each one — write it on a sticky note. Line them up.

Parent: "Look at all this. Every one of these is a piece of data you created. The phone didn't know any of this until you made it."

Phase 3 — Apply (5–6 minutes)

Now flip the question. This is where the concept deepens.

Parent: "Here's a harder question. What does the phone know that nobody ever gave it?"

Let him struggle — that's productive. The answer is: nothing.

If he says "but it knows math!" — lovely opening:

Parent: "Someone had to teach it the rules of math. A programmer wrote those rules and gave them to the phone as — what?"

Let him land on "data."

Parent: "Right. Even the phone's ability to do math is data someone gave it."

Phase 4 — Wrap-up (2–3 minutes)

Parent: "So if someone asks you what a computer knows, what's the answer?"

Let him articulate it in his own words. You're listening for the core insight: the computer only knows what it was given.

Parent: "And here's the big idea for next time: because computers only know what they're given, the quality of what they're given matters a lot. We'll come back to that."


Kid-response scripts

He says... What's happening You might try...
"But Siri does know things!" He's conflating the appearance of knowing with actual knowledge — sharp observation "Great point. Let's test that. Ask Siri something that just happened today." When it fails: "See — it only knows what someone already gave it."
"This is easy / boring." He's already past the surface — don't make him sit through it Jump straight to Stretch. The pixel/binary exploration is where his brain will actually engage.
"What about robots? Do they know things?" He's generalizing — excellent thinking "Same rule. A robot only knows what its programmers gave it. Even a robot that looks alive is running on data someone chose."
"Where does the data live?" He's curious about storage/hardware — a rich tangent "Inside the phone, on tiny chips. It's all stored as numbers — even the pictures. Want to see how that works?" → Stretch 1
"Can a computer make up its own data?" He's brushing against AI generation/hallucination — profound "It can combine data in new ways. But it can't make something from nothing. Everything starts with data someone gave it."
"So the computer is kind of dumb?" Overcorrecting — from "knows everything" to "knows nothing" "Not dumb — incredibly fast and precise. But it needs us. A calculator with no numbers typed in does nothing."
"I want to go play." He's spent Let him go. You planted the seed. Come back to Stretch tomorrow.

Common misconceptions to watch for

What you see What's actually going on How to gently address
He says "the computer thinks" Animism — natural for his age, even in bright kids Don't correct directly. Ask: "What does it think with? Where does the thinking happen?" Guide him to: it follows instructions on data.
He believes data = only numbers Narrow encoding of the word Expand: "Data can be words, pictures, sounds, even the rules of a game. Numbers are one kind." Show the photo again.
He assumes the computer "figures out" answers on its own Missing the instruction-following layer (prerequisite!) Reconnect to Step-by-Step Instructions: "Remember how computers follow steps? Those steps were written by a person. The steps are data too."
He thinks deleted data is gone forever Early understanding of permanence You don't need to resolve this today. It's actually the setup for the Privacy lesson later. Note it and move on.

Stretch (where the real lesson lives for your son)

If the main lesson lands in five minutes — which it may — here's where his brain will engage. Pick one or two. Each runs about five minutes.

Stretch 1: "How does a picture become a number?"

Pull up a photo. Zoom in as far as you can.

Parent: "You know this picture is data. But the phone can only store numbers. So how does a picture become numbers?"

Let him think. Then introduce pixels — tiny colored squares. Each pixel has a number that tells the phone what color to show.

Parent: "Every tiny square in this picture has a number. Millions of numbers. That's the data."

If you printed a zoomed-in photo, hand it to him and let him see the grid. This is a genuine "aha" for gifted kids — the bridge between the visual world and the numerical world.

Stretch 2: Invent your own code

Parent: "If the phone stores everything as numbers, could we make up our own number code for something?"

Have him invent: maybe A=1, B=2, C=3. Write his name in numbers. This is encoding — the foundation of how all computer data works.

Parent: "You just did what computers do. You took information and turned it into numbers. That's encoding."

Stretch 3: "What if we gave the phone the wrong data?"

Parent: "The phone only knows what it's given. So what happens if someone gives it wrong data?"

This opens a rich conversation: wrong directions, wrong photos, wrong facts. The computer doesn't know the difference — it trusts what it's given.

Parent: "This is why who gives the computer data — and whether that data is true — matters so much. We'll come back to this."

Stretch 4: The "empty phone" thought experiment

Parent: "Imagine a brand-new phone. Nobody has ever used it. No photos, no apps, nothing typed. What does it know?"

Let him sit with it. The answer: almost nothing — only what the factory programmers put in.

Parent: "Now imagine you never touch it for a year. Does it learn anything on its own?"

No. This drives home the passivity of the computer — it's a container, not a learner (yet — that's machine learning, later).


Quick mastery check (60 seconds)

Ask these three prompts. You're listening for the concept, not exact wording.

  • [ ] "What is data?" → Looking for: information someone gives a computer (numbers, words, pictures, sounds)
  • [ ] "Can you name three pieces of data you made today?" → Looking for: photo, message, search, voice command, game input, etc.
  • [ ] "Does the computer know anything nobody ever gave it?" → Looking for: "No" with some reasoning

If he nails all three, he's got the concept. Move on — don't belabor it.

Formal mastery check

From the taxonomy evidence strings, your son should be able to:

  • Define data as information stored on a computer — numbers, text, images, sounds
  • Give at least three examples of data he creates every day (photos, messages, search queries)
  • Explain that a computer only knows what it is given — no knowledge of its own

The dataset's assessment prompt:

Could your son explain what "data" means and give examples of data he creates every time he uses a phone or computer?

For a gifted 5y9m, the bar isn't rote recall — it's whether he can explain it to someone else. If he can teach the concept to a stuffed animal or a younger sibling, he owns it.


Vocabulary to use naturally

Drop these into conversation — don't define them explicitly unless he asks. Gifted kids absorb context.

  • Data — information given to a computer
  • Input — what goes in (he'll hear this in every computing lesson ahead)
  • Represent — how one thing stands for another (a number can represent a color)
  • Encode — turning information into a form the computer can store
  • Pixel — the tiny colored squares that make up a digital image
  • Digitize — turning something real (a photo, a sound) into data

What comes next

This lesson is a hard prerequisite for four downstream topics. Once your son owns "computers only know what they're given," the following become possible:

  1. AI Data Collection and Privacy — now he can ask: who is giving the computer data, and what kind of data? This is where personal data and privacy enter the picture.
  2. Patterns and Classification — computers find patterns in data. No data, no patterns. This is the bridge to how AI "learns."
  3. Machine Learning Basics — training a machine means giving it lots of data. He can't understand training without understanding data first.
  4. Recommendation Systems and Filter Bubbles — why does YouTube suggest certain videos? Because of data about what he clicked. This becomes personal fast.

You might preview any of these with a single sentence: "Remember how the computer only knows what it's given? Next time we'll look at what happens when it's given data about you."


If this lesson didn't land

Some days, even the best lesson flops. That's information, not failure. Consider:

  • Try a different manipulative. If sticky notes didn't click, build a "data pile" with LEGO bricks — each brick is one piece of data he's given a device. Physical and concrete.
  • Shift the time of day. If you tried late afternoon, try morning. Attention is a physical resource, even for gifted kids.
  • Shorten everything. Do only Phase 1 and Phase 4. Plant the seed and step away. Some concepts need time to germinate.
  • Skip and return. If he's not connecting, drop it for a week. Come back when he's been using a device more — the real-world hook may land better.
  • Check the prerequisite. If he's fuzzy on "computers follow step-by-step instructions," shore that up first. Without that foundation, data feels arbitrary.

Source

Taxonomy ID: mt_kH1DzOPsXG Dataset: Computing / Artificial Intelligence domain Standards: None specified (emerging K–12 area) Prerequisites: AI in Daily Life (soft) · Step-by-Step Instructions (hard) Generated by: Parent-facing lesson planner, tailored for gifted asynchronous learner (5y9m, IQ 125–130+)