Week 15: Diagnosing a Recurring Social Problem
Pick One Problem That Keeps Happening — Capstone Week 1
You have learned to notice body clues, catch thought bugs, read trust, set boundaries, and slow down before reacting. Now you use those tools on one real problem that keeps happening.
The capstone is a four-week loop:
- Week 15: pick one repeating problem and figure out why it keeps happening
- Week 16: make a clear plan for what you will do
- Week 17: try the plan in real life and track what happens
- Week 18: look back, improve the plan, and share what you learned
This week is about choosing well. You are not fixing your whole life. You are picking one problem that keeps happening and getting specific enough to understand it.
Looking closely at a problem that keeps happening can stir up frustration or embarrassment. If it does, that is a signal — not a reason to quit. Name the feeling, take a slow breath, and remember that asking for help is a skill: "I'm stuck on this and don't know how to explain it yet" is a complete, useful sentence. (More in Asking for Help Without Exploding.)
A problem is easier to solve once you can say it clearly. Try: "The problem is ___, and it keeps happening when ___." Naming the friction in plain words is the first communication move toward fixing it. (More on the Communication Skills page.)
This week's idea in kid language: "Pick one problem that keeps happening. Figure out the real reason underneath it."
- The big idea: start a four-week project by picking one repeat problem the learner can safely work on.
- Lead with pick one problem that keeps happening. Offer friction point and root cause as toolbox terms.
- Help the learner choose a project that is small, safe, and partly under their control.
- A bad project choice makes the next three weeks harder, so spend time here.
Facilitator approval is required before a student moves forward with a project.
Approve a project only if it is low-stakes, focused on the student's own behavior, communication, environment, or preparation, and easy to stop if it creates distress.
Do not approve projects about controlling someone else, exposing private information, testing another person's loyalty, revenge, surveillance, unsafe secrets, abuse, unsafe dares, adult conflict, or situations that need immediate adult help.
If the student's real-life examples are too hot, too private, or too painful, switch to a fictional situation or a lower-stakes version.
Week at a Glance
| Prep time | ~15 minutes |
| Materials | Telemetry Log, paper, pencil, large piece of paper for the diagnostic, optional: sticky notes |
| Key vocabulary | repeat problem, real reason, 5 Whys, baseline, pattern |
| Difficulty | Moderate to Advanced |
Facilitator Preparation
- Have the Telemetry Log accessible.
- Help the student narrow down what to pick. Brainstorm 3–5 candidates BEFORE picking.
- A good friction point: happens regularly (at least weekly), is at least partly within the student's control, focuses on the student's own choices, communication, environment, or preparation, isn't a crisis, and isn't about a single person who's clearly being abusive.
- Bad picks: "world peace" (too big), "my brother is annoying sometimes" (too vague), "I had a fight with Sarah last week" (one-time), "my parents are getting divorced" (too big, not the student's to fix).
Treat the learner like a partner working on a real project.
Your main job is to help them choose a problem that is the right size: not too big, not too vague, and not someone else's job to fix.
For Younger Learners (Ages 8–9)
Simplest version of the concept: "Pick one thing that keeps happening. We are going to figure out the real reason."
What to shorten or skip:
- Use 3 Whys instead of 5.
- Use "real reason" more than "root cause."
Adapting the activities:
- Use small, everyday problems.
- Turn it into detective work.
Journal alternative: Draw the problem in three panels.
What success looks like: The student picks one specific repeat problem and can name one reason it may keep happening.
Guided Session 1
Picking the Right Problem
Name the social friction before solving it: "The part that isn't working between us is ___." A clear problem statement keeps one awkward moment from turning into a whole story. (More on the Problem Solving Skills page.)
Learning Goal
By the end of this session, the student can:
- describe what makes a good project problem
- generate 3 to 5 candidate problems from their own life
- pick one and write a clear baseline description
Activities
1. What Makes a Good Project?
Explain the criteria:
A good project problem for this capstone is:
- Recurring. It happens regularly — at least weekly, ideally more often.
- Partly in your control. Something where YOU could potentially change something, not just wait for someone else to.
- Not a crisis. Not something that needs adult intervention right now.
- Specific. "I have a hard time with my sister" is too vague. "My sister and I fight every morning before school" is specific.
- Real to you. Something that actually bugs you. Not a problem you think you "should" pick.
Use this quick sort:
| Good project for this capstone | Not a good project for this capstone |
|---|---|
| I keep forgetting my homework folder. | I want my brother to stop being annoying forever. |
| I get snappy every day before dinner. | I want to prove who my real friends are. |
| I freeze during group work. | I want to fix my parents' conflict. |
| I avoid asking for help in math even when I need it. | I want to catch someone lying to me. |
2. The Brainstorm
Have the student list 3–5 candidate friction points. Don't pick yet — just generate.
Examples:
- I keep getting into the same fight with my brother before dinner.
- I always feel anxious right before lunch at school.
- I freeze when I have to do group projects.
- I keep ending up doing all the work in my friend group.
- I get into trouble with my mom every time she asks about my homework.
- I lose my temper at recess almost every day.
- I avoid one specific classmate who used to be my friend.
List them on paper. Do not choose yet.
3. The Choice
For each candidate, ask:
- Is it recurring (yes/no)?
- Is part of it in your control (yes/no)?
- Could you actually try something different next week (yes/no)?
The candidate that gets three yeses is a good fit. If multiple qualify, choose the one the learner is most curious about, not the one with the most pain.
Write this in the Telemetry Log as your Capstone Problem.
Guided Session 2
The Why Ladder
Learning Goal
By the end of this session, the student can:
- run the 5 Whys diagnostic on their chosen problem
- distinguish between the surface problem and the deeper reason
- describe at least one mismatch underneath the problem
Activities
1. The 5 Whys Tool
Explain:
"The 5 Whys is a diagnostic tool engineers use to find the real cause of a problem. You start with the surface complaint, then you ask 'why?' five times. By the time you've asked five whys, you usually find the real cause underneath the surface — which is often something completely different than what you started with."
This is not a magic number. Sometimes the real answer shows up after three whys, sometimes later. The point is to keep going past the first answer.
2. Running the Diagnostic
Take the student's friction point and walk through it:
Example walkthrough:
Friction Point: "I keep getting into a fight with my brother before dinner."
Why does it happen?
"Because he keeps taking my stuff without asking."
Why does that bother me so much?
"Because I've already had a long day and I just want him to leave me alone."
Why am I worn out by then?
"Because right before dinner is when I'm hungriest and most tired."
Why does being hungry and tired make this worse?
"Because my battery is low — I have less patience and small things feel bigger."
Why don't I prevent that?
"Because I haven't been eating my afternoon snack lately."
Root cause candidate: The fights happen when my brother does something annoying AND my capacity is low because I skipped a snack.
This is a totally different diagnosis than "my brother is annoying." Now the fix isn't "make my brother stop" — it's "eat the afternoon snack so I have capacity when he does his thing."
This is the whole point of the Why Ladder. The first answer is rarely the full answer.
3. Name the Mismatch
Once you've done the 5 Whys, see if you can name the system mismatch at the root:
- Different goals at the same time? ("I want quiet. He wants attention.")
- Different information? ("She didn't know I was already upset before she said that.")
- Different constraints? ("My parents have stress I don't see.")
- A degraded mode issue? ("Both of us are running on low capacity at the same time of day.")
Most repeat problems have 1 or 2 underlying mismatches. Name them. They become the targets for next week's plan.
Age-Banded Emotional and Social Learning Goals
- Ages 8-9: Keep the project small, concrete, and supported. Use 3 Whys, drawing, stickers, or one short sentence instead of deeper analysis.
- Ages 10-12: Use the full routine to describe a repeat problem, identify clues, and explain one realistic next step.
- Ages 11-13 optional extension: Add guided analysis of peer pressure, exclusion, group identity, online interaction, reputation, or a more detailed audience for the final project.
Social Problem-Solving Moves
- Pause before reacting.
- Name the problem without blaming.
- Name what each person might feel or need.
- Think of two possible choices.
- Choose a safe and respectful next step.
- Repair harm if needed.
- Reflect on what could work better next time.
Learner sentence frames:
- "I felt ___ when ___."
- "I need ___."
- "I think the problem is ___."
- "One fair solution could be ___."
- "Can we try ___?"
- "I'm sorry for ___. Next time I will ___."
- "I need help solving this."
The goal is not to force children to apologize before they understand what happened. The goal is to help them notice impact, take responsibility when appropriate, and practice repair.
Independent Practice
Goal
Establish a baseline. Watch the problem this week without trying to fix it yet.
Activities
1. The Baseline Tracker
Before you can fix a problem, you need to know how often it happens. For one week, just observe your friction point. Don't try to change it. Track:
| Date | Did it happen? | How bad (1–10) | What was happening before? | What was my capacity? |
|---|---|---|---|---|
| Mon | ||||
| Tue | ||||
| Wed | ||||
| Thu | ||||
| Fri | ||||
| Sat | ||||
| Sun |
By the end of the week, you have a baseline. That means you know how often the problem happens right now.
Minimum viable version: yes/no each day plus a face, color, sticker, or tally mark.
2. The Pattern Watch
While tracking, watch for patterns. Look for:
- Time of day it usually happens
- People involved
- What's usually happening just before
- Body state (capacity, hunger, sleep)
- Specific trigger words or situations
Patterns become extremely visible when you watch for them on purpose.
The baseline tracker is fully solo. You're observing your own life — no partner required.
Telemetry Log
Add a new section to your Telemetry Log called Capstone Project:
My repeat problem (specific, one sentence): ___
Why this one (what makes it the right pick): ___
5 Whys results:
Root cause(s): ___
System mismatch underneath: ___
Baseline tracking (the week of):
- Times it happened: ___
- Average severity (1–10): ___
- Patterns I noticed: ___
Hypotheses for the protocol next week: ___
Sentence starters for younger learners:
- "The thing that keeps happening is ___."
- "The real reason is probably ___."
- "It usually happens when ___."
Low-writing options: draw the pattern, use stickers by day, or say answers aloud.
Reflection Questions
- Did the Why Ladder take you somewhere you did not expect?
- What is hard about just watching the problem without fixing it yet?
- What pattern did you notice?
Check for Understanding
After this week, check whether the learner can:
- Name the project clearly: "What problem are you working on for the next four weeks?"
- Distinguish surface from deeper reason: "What did you think was causing it at first, and what might really be underneath it?"
- Read the pattern: "When does this usually happen?"
If the learner can do at least 2 of these, they are ready for Week 16.
Related Tools
- Use the Social System 5 Whys in Student Tools and Printables to keep the diagnostic specific and low-stakes.
- Use the Facilitator Safety Guide before approving a capstone project.
Pause and Notice
Ask:
"Did the problem look different by the time you got to the bottom of the why ladder?"
That shift matters. Once the learner can name the deeper reason, the next step becomes much clearer.
This week's takeaway: Many repeat problems have a reason underneath them. Naming that reason is the start of fixing it.
Spiral Review
- From Week 2: "Capacity is often part of the root cause. If your battery is low when the friction happens, no protocol will work until you address the capacity issue."
- From Week 6: "The story your brain tells about the friction point may be part of what makes it recurring. Run the audit on it — what's the input vs. the output?"
- From Week 14: "If another person is involved, run the three diagnostic questions on them too. What might they be operating under that you don't see?"
Use 3 Whys instead of 5. Keep the project small and concrete. Use tally marks, stickers, or faces for the tracker.
Have the older learner write a short problem statement naming the repeat problem, the pattern, the deeper reason, and the mismatch underneath it.
repeat problem, real reason, 5 Whys, baseline, pattern