Week 5: The Software Bugs of the Mind
Thought Bugs: Catching the Tricky Stories Your Brain Tells
For the last four weeks, you have been learning to read the body. This week, you look at the stories your brain tells.
Sometimes the story is helpful. Sometimes the story has a thought bug in it.
The grown-up toolbox phrase is cognitive distortion. Kid version: thought bug.
Thought bugs are not signs of a broken brain. Lots of brains do this. The skill is learning to notice the bug before you treat it like a fact.
Caught a thought that feels like a fact? Run a quick story check: What do I know for sure? What else could be true? What would I tell a friend? A thought bug is worth catching before you treat it like the truth. (More in Thought Bugs and Story Checks.)
This week's idea in kid language: "Sometimes your brain tells a story that feels true but might not be true. Those are thought bugs."
- This week gives names to patterns students already have.
- Lead with thought bugs. Offer cognitive distortion as the toolbox term.
- Do not moralize. These are common brain shortcuts, not personality defects.
- Be especially careful not to use thought bugs to dismiss a real problem.
- Continue the Telemetry Log. Start logging the story alongside the signal.
Week at a Glance
| Prep time | ~10 minutes |
| Materials | Telemetry Log, paper, pencil, sticky notes, a printed or hand-drawn "Bug Catalog" (you'll make one in Session 1) |
| Key vocabulary | thought bug, cognitive distortion, disaster brain, guessing what they think, always/never brain |
| Difficulty | Moderate |
Facilitator Preparation
- Have the Telemetry Log accessible.
- Have sticky notes handy — they're useful for the Bug Catalog.
- Think about your own examples ahead of time. Sharing your own real cognitive distortions makes the lesson land much better than abstract examples.
- Note: the four distortions we focus on this week (catastrophizing, mind-reading, personalization, all-or-nothing) are common patterns described in cognitive-behavioral frameworks. There are many more — these four are enough to start.
This week can feel like a plot twist in a good way. Many kids assume every thought their brain says is true.
Make it playful. Use bug cards, silly names, cartoons, lunch-table examples, sibling examples, sports examples, and group-chat examples.
Avoid one trap: do not use this lesson to dismiss real concerns. If a situation is painful, the feeling may be real even when the brain story is adding extra drama.
For Younger Learners (Ages 8–9)
Simplest version of the concept: "Sometimes your brain tells you a tricky story that is not fully true. Today we are learning what those tricky stories look like."
What to shorten or skip:
- Pick 2 bugs, not 4, if needed.
- Focus on spotting bugs, not on long explanations.
Adapting the activities:
- Use comic strips and thought bubbles.
- Give the bugs playful names and faces.
- Let the student sort examples into bug cards.
Journal alternative: Draw a bug card with a thought bubble and one safer replacement thought.
What success looks like: The student can name at least one thought bug and match it to a real or fictional example.
Guided Session 1
Meet the Thought Bugs
Learning Goal
By the end of this session, the student can:
- explain that a thought bug is a brain story that bends away from the facts
- describe four common thought bugs using kid-friendly names
- match each bug to a concrete example
Activities
1. Signal and Story
Explain:
"A body signal is one thing. The story your brain adds is another thing. Thought bugs happen in the story part."
Draw two columns:
| What happened | What my brain said |
|---|---|
| Friend did not text back yet | "She must be mad at me" |
| Stomach feels fluttery | "I am going to mess everything up" |
| Teacher sighed | "I did something wrong" |
Say:
"Sometimes the story is right. Sometimes it is a buggy guess."
2. Bug Card Lineup
Walk through the four main thought bugs. Use one sticky note or card for each.
| Kid Name | Toolbox Name | Example |
|---|---|---|
| Disaster Brain | catastrophizing | "I forgot one homework page. My whole week is ruined." |
| Guessing What They Think | mind-reading | "He did not wave at recess. He must hate me." |
| Making It About Me | personalization | "Mom looks stressed. It must be because of me." |
| Always/Never Brain | all-or-nothing thinking | "I messed up once. I always ruin everything." |
Use concrete examples from:
- lunch tables
- siblings
- sports
- homework
- class embarrassment
- group chats
Not every painful thought is a bug. Sometimes negative feelings point to a real problem.
Examples:
- "This group chat is getting mean" may be useful signal.
- "I feel nervous before the presentation" may be accurate data about pressure.
- "I don't like how that adult is talking to me" may be a sign that a boundary or adult help is needed.
Debugging means checking evidence and separating facts from exaggeration. It does not mean forcing positivity or pretending everything is fine.
3. The Most Important Rule
Write this in big letters:
A thought is not automatically a fact.
Have the student say it out loud.
Guided Session 2
Thought Bug Hunt
Learning Goal
By the end of this session, the student can:
- identify their own most common thought bug
- catch a thought bug in a real or recent example
- use one checking question, such as "Is that definitely true?"
Activities
1. My Top Thought Bug
Ask:
"Which bug sounds most like your brain on a hard day?"
Add it to the log:
My most common thought bug is ___.
This is not a label. It is a clue about what to watch for.
2. The Fact Check
Teach a simple move:
- Notice the thought.
- Ask: Is that definitely true?
Try it with a recent example:
- Friend sat somewhere else at lunch.
- Group chat got quiet.
- Teacher sounded short.
- Sibling laughed.
Ask:
- What did your brain say?
- What do you actually know?
- What might be another story?
3. Three Other Stories
Pick one worried thought and brainstorm three other possible stories.
Example:
"My friend did not sit with me. She does not like me anymore."
Other stories:
- she got pulled into another conversation
- she thought I was sitting somewhere else
- she was having her own hard day
The point is not to force a happy ending. The point is to remember that one first story is not always the whole truth.
Independent Practice
Goal
Catch at least three thought bugs this week. Name them.
Activities
1. The Thought Bug Hunt
When you notice a bug, write down or say:
- the thought
- which bug it looks like
- one fact-check question
- one other possible story
You do not have to make the thought disappear. You just have to name it.
Minimum viable version: Catch one thought bug this week and name it.
2. My Top Hit
At the end of the week, count which bug showed up most. That is your top hit - the one to watch for next week.
All bug-hunting activities are individual. No partner needed.
Telemetry Log
Add a new section to your Telemetry Log this week:
My Top Thought Bug: ___
Bugs I caught this week:
- Thought: ___ / Bug type: ___ / Was it a fact? ___
- Thought: ___ / Bug type: ___ / Was it a fact? ___
- Thought: ___ / Bug type: ___ / Was it a fact? ___
Another possible story: ___
Sentence starters for younger learners:
- "My brain told me ___, but actually ___."
- "The bug I run the most is ___."
Low-writing options: bug cards, checkboxes, circling a bug face, or saying the answer out loud while an adult writes it down.
Reflection Questions
- Which bug was easiest to spot?
- Did naming the bug change the feeling, even a little?
- Have you noticed these bugs in book characters, shows, siblings, or friends?
Check for Understanding
After this week, check whether the learner can:
- Define thought bug: "What is a thought bug?" (Looking for: a brain story that bends away from the facts.)
- Name at least two bugs: "Tell me about two thought bugs we learned." (Looking for any two with rough definitions.)
- Use the check: "If you have a worried thought, what question can you ask?" (Looking for: "Is that definitely true?" or a similar fact-check.)
If the learner can do at least 2 of these, they are ready for Week 6.
Related Tools
- Use the Thought Bug Debugger in Student Tools and Printables for fictional or low-stakes examples.
- Use the Assessment and Reflection Guide if you want to assess tool use without grading disclosure.
Pause and Notice
Ask:
"What happened when you named a thought bug this week?"
Sometimes the feeling shrinks. Sometimes it stays. Either way, the student has done something important: they created a little gap between the feeling and the story.
This week's takeaway: Thought bugs are normal. Noticing them is a skill, and this week starts that skill.
Spiral Review
- From Week 1: "Signals are the raw data. Stories are what your brain wraps around them. Same signal, different stories possible."
- From Week 3: "Cognitive distortions are extra loud during a hijack. When the panic brain takes over, the worst-case story usually wins."
- From Week 4: "The story your brain tells is part of your telemetry. Log it alongside the signal."
Stick with two bugs: Disaster Brain and Guessing What They Think. Use silly comic examples.
Have the older learner add two extra thought bugs to their bug catalog and create their own examples.
thought bug, cognitive distortion (toolbox phrase), Disaster Brain, Guessing What They Think, Making It About Me, Always/Never Brain