Teaching the Story

Why this matters

In the Universal Core, "Why Stories Win" makes a case to adults: a specific person in a specific scene moves a room in a way a statistic never will. Your job here is different. You're not persuading anyone today. You're growing the part of a young person who will, one day, be the one at the podium, in the meeting, or at the kitchen table making the case for something that matters to them — years before they'll need it, the way you'd teach a kid to swim before the day they actually fall in the lake.

The skill underneath "story wins" isn't charisma. It's a specific, learnable move: taking something that actually happened to a real person and shaping it so another person can feel it. Most adults never got taught this on purpose — they pick up a garbled version from group projects and cover letters, vague and hedge-everything, and wonder years later why nobody listens to them in a school board meeting. You get to teach it straight, early, and correctly.

What you're growing

Two things, and they're not the same thing.

The difference between a story and an argument. An argument says you should believe X because of reasons 1, 2, 3. A story says here is what happened to someone, in order, and now you understand something you didn't before. Kids default to argument mode early — "that's not fair because Sarah got two cookies and I only got one" is already an argument. The harder, more valuable move: don't tell me why it's unfair, tell me what happened. Let the listener arrive at "that's not fair" on their own, because you showed them the scene.

The four load-bearing pieces of a true story: a real, specific person (for a kid, usually "me," a friend, or a pet — a name, not a category); a turn — the moment something changed, went wrong, or got noticed; one concrete, sensory detail that puts the listener in the room (not "I was sad," but the thing that made you sad — the broken toy, the empty chair, the rained-out game); and an ending that lands somewhere, even if it's just "and that's why I don't trust the vending machine anymore."

This is the same skeleton as the adult Story Map — Hook, Character, Conflict, Turn, Resolution — built with age-appropriate scaffolding. You are not teaching your five-year-old the word "resolution." You're teaching them that a story which just stops isn't finished yet.

Early (~5–9)

The activity: "Tell me about a time it wasn't fair."

This is the whole exercise at this age, and it works because unfairness is a young child's native emotional language — felt acutely and constantly, usually about siblings, bedtime, or dessert portions.

Sit down, no distractions, and ask: "Tell me about a time something wasn't fair — not right now, something that already happened." Let them talk. Don't correct the facts, don't relitigate the sibling dispute, don't explain why it actually was fair. Your job is to ask the questions that pull out the missing pieces of a story: Who was there? (Character — a name, not "someone.") What happened right before the unfair part? (sets the scene.) What was the unfair part, exactly? (Conflict/Turn, one sentence.) What did it feel like? — if they say "bad" or "mad," push once for the concrete detail underneath the feelings-word. What happened after? (an ending — even "I went to my room" counts.)

At this age, you're not asking for polish. You're asking for the shape: someone, something happened, it mattered, then something else happened. Rotate topics every week or two ("a time you were proud," "a time you were scared") once fairness is well-worn. The goal by age nine is a kid who, unprompted, tells you what happened instead of just how they feel about it.

Middle (~10–13)

The activity: a local-issue story.

By this age a kid has opinions about something real in their world — a park that got closed, a rule at a co-op or activity, a friend who got treated badly, a local business that shut down. Pick one they actually care about; borrowed outrage doesn't build the skill.

Walk them through the Story Map explicitly now — you can use the words. Hook: "What's the one sentence that would make someone want to hear more?" (Not "I want to talk about the park." More like "The only park in walking distance from our house is closed for the summer.") Character: "Who does this actually affect — you, a specific friend? Name them." Conflict: "What's happening that shouldn't be happening, in one sentence?" Turn: "Was there a moment something changed — you found something out, someone said no, someone made a decision?" Resolution: "What do you think should happen? One specific thing, not a feeling."

Have them write it, four to six sentences, then read it out loud to you — to you only, no audience required. Time it if they're willing; under a minute is a good early target, close to what a real public comment allows. Ask one question afterward: "What's the part where I felt the most like I was actually there?" That's the detail worth keeping; cut whatever around it doesn't earn its place.

Older (~14–18)

The activity: an op-ed or a piece of testimony.

At this age the story can carry more weight and structure — a written op-ed for a real or hypothetical local paper, or testimony as if for a public hearing (city council, school board, a rule change at work). The Story Map is now the whole scaffold, not a set of questions you ask out loud — hand them the framework and let them build it themselves, then review it together.

Ask for a full draft: Hook, Character, Conflict, Turn, Resolution, each field genuinely one sentence on the first pass (the discipline of compression is what makes the final piece sharp). Then let it expand into 300–500 words. Check two things beyond the Story Map's own fields: is the story doing more work than the adjectives? — teen first drafts often lean on intensity ("this is absolutely unacceptable") instead of specificity; push for the one detail that makes the point without it. And is the resolution an actual ask, not a complaint? "This should change" isn't an ending. "The school board should extend the library's after-school hours by one evening a week" is.

Read it aloud together, with a timer if it's meant for testimony — three minutes is the real-world constraint most public comment periods impose, and building to that limit now is training for later. If it's an op-ed, read it aloud anyway; things that don't sound right out loud usually aren't right on the page either.

How to facilitate

Model it first. Before you ask a kid — any age — to tell a true story, tell them one of yours. Not a lecture, an actual story with a real turn and a real ending, ideally about something small and honest (a time you were embarrassed, a time you were wrong). Kids calibrate what's expected by what they've heard, not by what they've been told.

Ask, don't supply. Your questions should pull the story out of them — "who was there," "what happened next," "what did that feel like" — not hand them the sentences. A story you wrote for your kid teaches them nothing about building one themselves.

What not to do: don't correct the facts of a dispute mid-exercise (separate that conversation out loud, as noted above); don't demand polish from a five-year-old or treat a rough middle-schooler draft as finished; don't let a story wander into a lecture about what they should think about the issue — your job is the shape and truth of the story, not the conclusion it points to.

The floor, every time

Everything here teaches how to build and tell a true story — never which story is right to believe, never which side of an issue to land on. A kid who builds a story about a park closure and a kid who builds one about a rule they think should stay exactly as it is are both doing the same skill correctly. If you notice yourself steering the content of the story rather than its craft — nudging toward the conclusion you want instead of the true account of what happened — stop and hand the wheel back. Skill, not side. Same guardrail this platform holds everywhere else.