DAX Foundation

Meta DAX › Samples

Interviewing a grandparent about a small town

History · Ages 10-12

An illustrative example made with a simulated family — not a real family’s record. A way, never the way.

Guide: Rosa · Learner: Luca · Age band: 10–12 · Subject: History

Where the learner was stuck

Luca, who is twelve, could pass a quiz on dates and names but experienced history as a wall of facts with no one behind them. Asked what any of it had to do with a real person, he shrugged — it was just stuff that was already over, printed in a book, memorised for the test and then gone. The idea that history is made of ordinary people's days, that someone alive today remembers a version of the past firsthand, had never quite landed. He was not uninterested; he simply had never met history as something a person could tell you about over a cup of tea.

The approach (built through what they love)

Luca does love the family's own stories, and will happily sit and listen to an older relative remember things. So this session makes that the history lesson. The plan is a single real interview with a grandparent, kept fictional and generic here, about one small town they knew. Three questions carry it: what did the town look like back then, one job they held, and one change they watched happen over the years. Luca prepares the questions, asks them, listens, and takes rough notes. Afterward, the raw answers become the first page of a local history written in a real person's voice — not a list of dates, but what one person saw. History stops being a book and becomes a conversation he was part of.

For the guide: the shape of a session

Help Luca write his three questions before the interview, and keep them open — "what did the main street look like?" draws a story where "how many shops were there?" draws a number. Agree a signal for "ask the next one" so Rosa can sit in without taking over. During the interview, Luca leads and the grandparent talks; Rosa's whole job is to stay out of it unless the thread drops. Afterward, sit with the notes and help Luca turn three spoken answers into three short written passages, keeping the grandparent's own phrasing wherever it is vivid. Keep it to the three questions — a first interview that goes deep on three beats a scattershot twenty. Stop while there is still a story Luca wants to write down.

What only a person can do

Rosa can read the room during the interview — notice when a question has opened something the grandparent wants to say more about, and quietly let the silence run instead of rushing Luca to the next question. She can tell when Luca is genuinely curious versus just working through his list, and nudge him to follow the live thread. She can judge which memories are the grandparent's to share and which to leave, a decision no page could make for a family. And afterward she can hear which plain spoken line — "the whole street smelled of bread on a Tuesday" — is the one worth keeping exactly as it was said, and help Luca build the passage around it rather than flattening it into a fact.

Where the learner leads

This whole session runs on Luca being the one who asks. He chooses the three questions, he conducts the interview, he decides which answers struck him enough to write down first. The grandparent is the expert on the town, but Luca is the one drawing the history out and shaping it — the historian's actual work. When he reads his finished page back and realises he has written something that did not exist in any book, because he made it from a real person's memory, the point of the subject arrives on its own. The guide sets it up and steps back; the learner does the history.

The game on the learner's side

Between the interview and the writing, the game helps Luca turn spoken memories into a history. It shows one of the grandparent's answers and asks what kind of source it is — a firsthand memory, a guess, or something they heard from someone else — because a historian has to know. A wrong choice explains the difference rather than just marking it ("that is something they were told, not something they saw — still useful, but you would write it differently"). Then it offers three ways to open the written passage and asks which keeps the person's own voice rather than turning it into a textbook sentence. Three levels: level one sorts memory from fact, level two keeps the speaker's voice while tidying a sentence, level three asks Luca to place one remembered change on a simple before-and-after timeline. It steps up after three right in a row and eases after a miss, and every slip it notes is about handling a source, so Rosa knows what to pick up next time.

When to seek an evaluation

Finding history dry and disconnected is ordinary, and for most children it dissolves the moment the past becomes a real person talking — which is the whole point of this session. But if, across many subjects and many months, a learner cannot hold a sequence of events in order, loses the thread of a story told aloud and cannot say what came before what, or tires sharply whenever a task asks him to connect one thing to another rather than recall a single fact, it may be worth describing what you see to someone whose work is how young people learn. A family doctor or a learning specialist can observe and tell you what they notice. You do not need a label to ask, and what you learn is yours to use as you choose.

A way, never the way

Interviewing a grandparent is one way into history, chosen because this learner loves the family's own stories. Another child would get there through old photographs of one street, objects from a kitchen drawer, or a song that was popular once. The thing worth keeping is the move — history as a real person's firsthand account, drawn out by the learner and handled like a source — not the particular grandparent or the particular town. Keep the interview fictional, generic, and the family's to share or not. Use what fits your learner; leave the rest.

The companion sidecar for this package

This package carries a companion.json sidecar: the machine-readable file a cognitive companion reads alongside the package, in the metadax-companion shape. It is published in the repo at companion/examples/history-grandparent-interview.companion.json. The sidecar states the single next step for guide and learner, the reach band for this learner, the behavioural signals a companion may watch (each naming the inference it must never become), the moves the companion may offer and their ceilings — and, required and non-empty, the work reserved for the human guide, each with a reason it stays with a person. It names capabilities, never products, and everything it describes degrades to a once-a-day bundle. It is a sidecar, read with the package, never a profile of a child. A way, never the way.