Week 6: When the Brain Constructs Bad Stories
Story Maker: What Happened vs. What My Brain Said
Last week you learned about thought bugs. This week you learn why they happen so fast.
Your brain is a story maker. It sees a clue, then quickly makes a guess about what the clue means.
Examples:
- a friend walks past you
- a teacher sighs
- a parent says "later"
- the group chat goes quiet
Your brain often makes a story right away: "They are mad," "I did something wrong," or "I am being left out."
Sometimes that first story is right. Sometimes it is just a guess. This week you practice separating what happened from what my brain said. The formal toolbox name you will use later is Input/Output Audit.
This week's idea in kid language: "Your brain is always making stories about what things mean. Sometimes the first story is right. Sometimes it is just a guess."
- The big idea: the brain is constantly making stories, even when it feels like the story is obvious.
- Lead with story maker and What Happened / What My Brain Said.
- Use camera facts, thought bubbles, and picture cards.
- Students may use fictional, book, show, or low-stakes examples.
- The goal is not to stop the story maker. The goal is to notice it.
Week at a Glance
| Prep time | ~15 minutes |
| Materials | Telemetry Log, paper, pencil, a few short video clips or photos (optional — see Session 1), a partner if available |
| Key vocabulary | story maker, camera facts, brain story, input/output audit |
| Difficulty | Moderate |
Facilitator Preparation
- Optional but useful: find 1–2 short, ambiguous video clips or photos online — something where you can't tell exactly what's happening. (Two people having a conversation with no sound. A person sitting alone on a bench. A pet making an unclear face.)
- Have the Telemetry Log accessible.
- Identify one low-stakes recent moment from the student's life that involved guessing what something meant. Fictional examples are also fine.
This week is a big idea, so keep it concrete.
Use photos, picture cards, lunch-table moments, group-chat pauses, and sibling examples. Do not let it turn into a debate about whether the student is wrong. The point is simpler: your first story is still a story, and stories can be checked.
For Younger Learners (Ages 8–9)
Simplest version of the concept: "Your brain is a story maker. Sometimes the first story is right, and sometimes it is just a guess."
What to shorten or skip:
- Skip most formal terms.
- Use "What happened?" and "What did my brain say?"
Adapting the activities:
- Use picture cards and thought bubbles.
- Make a game out of finding three possible stories.
- Use fictional characters if needed.
Journal alternative: Draw a camera and a thought bubble. Put facts in the camera and guesses in the bubble.
What success looks like: The student can name one first story and one other possible story about the same event.
Guided Session 1
Story Maker Game
Learning Goal
By the end of this session, the student can:
- describe the brain as a story maker that guesses what things mean
- give more than one possible story about the same event
- understand that the first story can feel true even when it is only a guess
Activities
1. The Picture Card Test
Show an ambiguous photo or describe a scene:
- your friend walks past in the hallway and does not say hi
- a teacher sighs while looking at papers
- a person in a picture has their head in their hands
- a text says "ok" and nothing else
Ask:
"What is the first story your brain tells?"
Then ask:
"What are three other possible stories?"
This can turn into a game. The goal is not the perfect answer. The goal is to feel how quickly the brain fills in blanks.
2. The 50/50 Story Test
Take a recent moment and find:
- the first story
- one equally possible other story
Example:
- Situation: friend did not text back for two days
- First story: she is mad at me
- Other story: she is busy, forgot, lost her phone, or is having her own hard week
Say:
"The brain picks a story fast. It does not automatically know the truth."
3. Why the Story Maker Exists
Explain:
"The story maker helps humans predict things and get ready. That is useful. The tricky part is that it often forgets to say, 'This is only a guess.'"
Your job is not to turn the story maker off. Your job is to notice when it starts making guesses.
Guided Session 2
What Happened / What My Brain Said
Learning Goal
By the end of this session, the student can:
- separate camera facts from brain stories
- describe the difference between what happened and what they guessed it meant
- preview the Detective Check, also called the Input/Output Audit
Activities
1. Camera Facts and Thought Bubbles
Take a piece of paper and make two columns:
| What happened? | What did my brain say? |
|---|
Say:
"The left side is what a camera could see or hear. The right side is the story your brain added."
2. The Separation Drill
Take a recent low-stakes moment and fill in the two columns.
Example:
| What happened? | What did my brain say? |
|---|---|
| Parent said, "We'll talk later" | They are furious |
| Parent walked away | I am in huge trouble |
| Parent sounded short | I must have messed everything up |
Notice how short the facts are and how long the brain story gets.
That is normal. The brain can build a huge story from a tiny clue.
3. Preview the Detective Check
Tell the student:
"Soon you will learn a tool called the Input/Output Audit. Kid version: The Detective Check. It helps you sort camera facts from brain stories and choose a safe next move."
This sets up the next part of the unit.
Independent Practice
Goal
Catch your story maker in action and practice separating facts from story.
Activities
1. The Daily Detective Check
When something pings your feelings this week, write down:
| What happened? | What did my brain say? |
|---|---|
You do not have to fix the story yet. Just notice the gap.
Minimum viable version: Do this once this week.
2. Three Possible Stories
Pick one moment this week and list three possible stories about it.
Examples:
- friend walked past me
- teacher sighed
- parent said "later"
- group chat got quiet
Fictional examples count.
If you don't have a partner, do the Daily Input/Output Drill alone. The drill works perfectly with just you and the log.
Telemetry Log
Add a new entry style this week — the Input/Output style:
Trigger: ___
What happened? (camera facts):
What did my brain say? (thought bubble):
The bug from Week 5 (if any): ___ (catastrophizing / mind-reading / personalization / all-or-nothing)
An alternative story: ___
Sentence starters for younger learners:
- "What actually happened was ___."
- "But my brain said ___."
- "Another possible story is ___."
Low-writing options: camera and thought-bubble drawings, picture cards, checkboxes, or oral answers.
Reflection Questions
- Was there a moment this week when the camera facts were small but the brain story was huge?
- Which kind of situation makes your story maker loudest?
- What does your body feel like when your story maker gets going fast?
Check for Understanding
After this week, check whether the learner can:
- Name the story maker: "What is the story maker?" (Looking for: the brain part that guesses what things mean.)
- Separate fact from story: "Tell me a recent moment. What happened, and what did your brain say?" (Looking for concrete facts and a separate interpretation.)
- Offer another story: "Your friend ignored you at lunch. First story: 'She is mad.' What is another story?" (Looking for any reasonable alternative.)
If the learner can do at least 2 of these, they are ready for Week 7.
Related Tools
- Use the Input/Output Audit in Student Tools and Printables to sort camera facts from brain-generated story.
- Use Week 8: Separating Signal from Narrative Noise as the next-step formal tool once students can already name input vs. output.
Pause and Notice
Ask:
"What is it like to see the camera facts and the brain story side by side?"
For many kids, the surprise is this: the camera facts are often small, but the brain story is huge.
That does not make the feeling fake. It just shows where the extra intensity may be coming from.
This week's takeaway: The brain does not only see. It interprets. Naming the interpretation is the first step in checking it.
Spiral Review
- From Week 3: "During a hijack, the story generator runs especially loud and biased toward worst-case stories. That's why post-hijack regret is so common."
- From Week 5: "The four bugs from last week — catastrophizing, mind-reading, personalization, all-or-nothing — are the most common outputs the story generator produces. Use them as labels when you spot one."
Stick with picture cards and thought bubbles. The key idea is enough: "My brain makes up stories fast, and I can check them."
Have the older learner notice their story maker once a day for a week and record the first story plus two alternative stories.
story maker, camera facts, brain story, Input/Output Audit (toolbox phrase)