When your kid fixes a problem and it comes right back, the instinct is to blame follow-through. They didn't stick with it. They forgot. They stopped trying.
That's usually the wrong diagnosis.
The more likely explanation: they found one cause, fixed it, and stopped. But there were two more roots they never touched.
One fix, half a solution
Root cause analysis, the "keep asking why" approach, is one of the most useful things you can teach a kid. But most introductions to it leave out a critical detail: a single why chain finds a single root cause. Real problems often have more than one.
Take a common example. A kid is consistently late turning in homework. They run the why chain:
- Why was it late? I forgot it was due.
- Why? I didn't write it down.
- Why? I rushed out of class.
Fix: write assignments down before leaving class. Reasonable. And for a week or two, it works.
Then the problem comes back.
Because there was a second root they never found: they also don't have a reliable block of time to actually do the homework. The first fix addressed the forgetting problem. The scheduling problem was still there, untouched.
The branch point
Most problems have what engineers call a branch point, a place where the same symptom has two or more independent causes. Fix only one branch, and the other keeps producing the same result.
This is why solutions that make sense, get implemented, and seem to work still produce recurring problems. It's not a failure of follow-through. It's incomplete diagnosis.
The question to ask after running the first why chain isn't "did we find the cause?" It's "is that the only cause?"
How to teach kids to catch this
Once your kid runs a why chain and arrives at a root, go back to the original problem and ask: Is there anything else that could cause this, separately from what we just found?
If yes, run a second chain. Keep going until you've mapped every independent path to the same symptom.
When you address all the roots, the problem stops coming back. When you address only some of them, it partially improves, which is easy to mistake for a real fix until it recurs two weeks later.
Why this matters for kids specifically
Adults learn this pattern from years of trial and error. They start to notice when a problem returns and recognize they probably missed something.
Kids don't have that pattern recognition yet. Without someone teaching it explicitly, a recurring problem reads as personal failure: they tried, it didn't work, they're bad at this. That's the wrong conclusion, and it compounds.
Teaching a kid that "there might be another cause" reframes the recurrence as a diagnostic opportunity rather than evidence they can't solve problems. That one shift changes how they respond when a fix doesn't fully hold.
The SOLVED method builds this in
The SOLVED method doesn't assume a single root. It teaches kids to look for branches, to ask whether the why chain they've run is the only path to the symptom, or just the most obvious one.
That's a skill most adults never learned formally. Your kid can have it before middle school.
The free starter kit at solved360.com includes Chapter 1 and the Problem Statement Builder, enough to work through a real problem today.