If you've heard "root cause analysis" and pictured a whiteboard full of fishbone diagrams and engineering jargon, that's a reasonable assumption. It's a method that comes out of Six Sigma, hospitals, aerospace — serious institutional problem-solving. It sounds like the last thing you'd hand to a fifth grader.
But the core of it is actually one of the simplest ideas in problem-solving: before you fix something, find out why it broke. That's it. Everything else is just structure around that idea, and the structure scales down to a 10-year-old just fine.
What it is at its most basic
Root cause analysis starts with a refusal to accept the surface explanation. When something goes wrong repeatedly, there's a reason it keeps happening — and that reason almost never lives on the surface where you can see it.
A kid who keeps getting detentions for being late to class isn't fundamentally a "late kid." Something is producing the lateness, and until that something gets identified and addressed, the detentions will keep coming. The detention is the symptom. The cause is somewhere earlier in the chain.
The method is built around following that chain backward until you find where it actually starts. Not where it became visible, and not where it became inconvenient — where it started.
What it looks like when a kid does it
Here's a real-scale example. A student keeps forgetting to turn in homework. Not occasionally — consistently, across multiple classes, week after week.
The obvious fix is to remind them more. The parent leaves notes, the teacher sends emails, maybe there's a planner that gets checked and then forgotten. The homework still doesn't make it in.
Root cause analysis asks a different question: not "how do we remind them better" but "why does this keep happening despite reminders?"
Walk the chain:
- The homework doesn't get turned in. Why? Because it's not in the backpack when they get to class.
- Why isn't it in the backpack? Because it was left on the desk at home.
- Why was it left on the desk? Because packing the backpack happens in the morning when there's no time to think clearly.
- Why is there no time? Because they're waking up with fifteen minutes to get out the door.
Now you have something to actually fix. Packing the backpack the night before, with a checklist they run themselves, breaks the chain at the right place. The reminder notes were addressing a symptom three steps downstream from the actual cause — which is why they weren't working.
A 10-year-old can walk through that chain. It takes about five minutes and a few honest questions. No fishbone diagram required.
The questions that do the work
The practical tool is a sequence of "why" questions, asked without judgment and without jumping to solutions. The goal of each question is to move one step closer to the source.
The questions sound like this:
- What actually happened? Get specific — not "I did badly" but "I lost points on problems 7 through 12."
- When does this happen, and when doesn't it? The contrast is where the cause usually hides. If the problem only shows up on Tuesdays, that's a Tuesday-specific cause.
- What changed right before it started? New teacher, new schedule, new seating arrangement, a conflict with a friend — context shifts that precede a problem are almost always relevant.
- If we fixed the most obvious thing, would the problem come back? This is the test for whether you've found the real cause or just a plausible one.
The answers to those questions don't require expertise. They require honesty and a little patience, which most kids can manage when they understand what they're looking for.
Why this is different from "think harder"
Most of the advice kids get about academic and personal problems amounts to trying harder, caring more, or being more organized. That advice isn't wrong exactly, but it doesn't give anyone a specific thing to do. Telling a kid to "be more organized" without giving them a method for identifying what's causing the disorganization is the equivalent of telling someone with a slow car to "go faster."
Root cause analysis gives them a specific thing to do. It's a sequence of steps, not a character trait, which means it can be learned and practiced regardless of how naturally organized or focused a kid happens to be.
The other thing it does is shift the framing. When a problem keeps coming back, it's easy for a kid to conclude that they're just bad at whatever it is — homework, punctuality, keeping track of their things. Root cause analysis reframes the question: the problem isn't who you are, it's a system that isn't working yet. And systems can be fixed.
How the SOLVED method packages this
The six-step SOLVED method is root cause analysis adapted for the scale and vocabulary of a middle schooler. It runs through: stating the problem precisely, observing the pattern, listing possible causes, verifying which cause is actually responsible, executing a targeted fix, and documenting what worked so it transfers to the next problem.
Each step is a question or an action that a 10-year-old can actually take, with examples drawn from the kinds of problems that show up in real kid life — grades, friendships, chores, habits. The method doesn't require a parent to know the answer, which is part of the point. It's designed to be handed over, not administered.
SOLVED: The Kid's Guide to Fixing Anything That's Broken, Late, Lost, or Failing teaches the six-step root cause method to problem-solvers ages 10 to 14. A private tutor costs $40–$80 an hour. This teaches the method behind the answers — once, for the price of lunch. Get the free Starter Kit at solved360.com — Chapter 1 and the Problem Statement Builder, free.