Tell
INTERPRETATION — *correlation-not-causation posture* (data shows patterns; humans interpret; confidence not certainty). The data-pipeline primitive of *recognizing that the data shows patterns but humans bring the meaning.*
Listen along — Tell
Loading audio…
Press play to listen along. The line being read lights up as you go.
Show full transcript
Loading transcript…
Chapter 4 — Tell and the Interpretation-Card
Tell was a small heron-tween. She had long legs and soft grey-and-white feathers. Her eyes were steady and kind. She always wore a small wooden card around her neck. It hung from a simple cord.
The card was small and smooth. It had two sides. On one side, in neat block letters, it said: CORRELATION. On the other side, it said: CAUSATION. Below those words, a big, clear symbol stood out: ≠. That meant “not equal.”
The card was Tell’s special helper. It reminded her of something important. It also helped her teach. When a kid said, “This data shows that X makes Y happen,” Tell would hold up her card. She would gently flip it over. The card seemed to ask: Which side are you on? Can you really tell?
Tell’s main job was to teach about interpretation. This is a big word. It just means knowing the difference between what numbers show and what you think they mean. Most kids, when they first look at numbers, mix these two things up. They say, “The numbers prove X makes Y happen!” But that’s almost always wrong.
Numbers show patterns. They show when two things move together. This is called correlation. For example, variable X and variable Y might go up at the same time. But the numbers don’t show why they move together. They don’t show what is making them move.
To find out what causes something, you need more. You need a good guess about how it works. You might need to do an experiment. The numbers alone won’t tell you the cause.
Tell was very clear about this. “Correlation is what the numbers show,” she would say. “Causation is what we add. Don’t mix them up!” She loved to use an example. “Ice cream sales go up when more people drown. But ice cream doesn’t cause drowning!” The kids would always gasp. “Both things happen more in summer weather. The hot weather is the real cause. But the numbers for ice cream and drowning don’t show that.”
Tell also taught that we can’t always be 100% sure. Data analysis rarely gives us a perfect answer. It gives us a good guess. It shows what might happen most of the time. It shows what is likely.
The skill she taught was called honest hedging. This means saying what the evidence really supports. You show how sure you are. You don’t pretend to be certain when you’re not.
Tell grew up in a small village. Her family had a special job there. They were the market-observers. They were herons who watched the village market every day. Then they told the village council what they saw. They reported on trade, gossip, and how people felt.
This job needed careful thinking. They had to know what they saw and what they guessed. The council stopped trusting observers who mixed these up. But they relied on observers who were careful. For example, one observer might say, “Three farmers complained about the rain today. This might mean they expect a poor harvest.” That was good. It was better than saying, “The harvest will be poor.”
Tell learned this by age six. She understood that interpretation was its own craft. Being honest about what you knew, and what you didn’t, built trust.
When she was twenty-two, Tell walked to the DataForge academy. Datum, the head of the academy, asked her a question. “What is interpretation?” Datum asked.
Tell thought for a moment. “It’s knowing correlation from causation,” she said. “Numbers show patterns. Humans add meaning. We can be confident, but not certain.”
She went on. “The data doesn’t say what makes what happen. It shows what moves together. Causation comes from ideas, how things work, and experiments. And interpretation is honest hedging. You claim what the evidence supports. Nothing more.”
Datum smiled. “You are appointed,” Datum said.
In her workshop, Tell started every first lesson the same way. She held up her interpretation-card. She flipped it slowly. CORRELATION showed first. Then CAUSATION. Then CORRELATION again. Then CAUSATION.
She looked at the kids. “I am Tell,” she said. “The data skill I teach is interpretation. Remember this: correlation is what the numbers show. Causation is what we add. Don’t mix them up. And always claim confidence, not certainty.”
She taught them a few simple steps for interpretation:
- What patterns do the numbers show? List the connections you see. Be honest about them.
- What might be causing those patterns? Think of possible reasons why things move together.
- What else could explain it? Maybe something else is at play. Could it be a coincidence? Is there a hidden reason?
- Keep correlation and causation separate. When you write about your findings, say, “The numbers show that X goes with Y.” Don’t say, “X makes Y happen.”
- Show how sure you are. Use words like “There is some evidence that…” or “The numbers suggest…” or “I’m pretty sure that…”
- Know what the numbers can’t show. What information is missing? What people aren’t included? What time is not covered?
- Know the difference between describing, predicting, and prescribing. Describing is saying what is. Predicting is saying what might be. Prescribing is saying what should be. Each one needs different proof.
- Tell when the numbers don’t help. Sometimes the numbers are unclear. It’s okay to say, “The evidence is mixed.” Don’t make the numbers say what you want them to say.
Tell was very clear. “Sometimes a kid wants the numbers to prove something,” she said. “Even grown-ups in the news do this. But that’s just a wish. It’s not a real finding.”
She paused. “The numbers show patterns. Patterns are evidence. Evidence is not proof. Confidence, not certainty. That’s how we do it.”
When students asked Tell if interpretation was hard, she always gave the same answer.
“It is not hard,” she would say. “It is honest hedging. Correlation is what the numbers show. Causation is what we add. Confidence, not certainty.”
The interpretation-card swung gently on its cord. Another set of numbers waited. They were ready to be understood.
The DataForge ensemble
Tell is part of DataForge's distributed-narrative cast. Each character embodies a different curricular primitive; together they teach the full subject.
-
Catch
Data collection — who-what-why-when posture (every dataset has a collector + purpose + omissions)
-
Tidy
Data cleaning — preparation-with-integrity posture (every cleaning choice changes meaning; document the choices)
-
Graph
Data visualization — shape-of-the-story posture (which chart tells the truth, not the loudest one)
-
Guard
Data ethics — bias-privacy-harm-consent posture (who benefits, who's harmed, who decided; structurally present in every kit from kit 6)