Your kid hits a wall, turns around, and asks you what to do. You tell them, it works, and everyone moves on with the afternoon. That exchange feels like good parenting, and most of the time it is.
But run it a few hundred times and you've taught something you never intended: when you're stuck, the move is to find someone who already knows the answer.
I don't think that's a discipline problem or a motivation problem. I think it's a handoff that never happened.
Why "just figure it out" backfires
Once you notice the pattern, the instinct is to stop answering — push it back, let them sit in it a while. That approach fails for a reason worth understanding.
Struggling without a method isn't practice. It's just being stuck for longer. A kid who has no framework for approaching an unfamiliar problem won't invent one because you declined to help. They'll guess until something sticks, or they'll conclude they're bad at this and stop trying. Neither outcome is what you were going for.
Independence isn't the absence of help. It's having a method they can run when you're not standing there.
So the goal isn't to answer less. It's to hand them something first. Answering less comes after that, and it comes naturally.
Answer the question they're actually asking
When a kid says "what do I do," they're asking one of two very different questions. Either they don't know what's wrong, or they know exactly what's wrong and can't figure out how to fix it.
Almost every parent answers the second one. Almost every kid is asking the first.
The correction is smaller than you'd expect. Instead of telling them what to do, ask what they think is actually going wrong. That single question moves the work from your side of the table to theirs, and it's the move everything else depends on. It also feels unhelpful in the moment, which is exactly why most of us skip it.
Make them state the problem out loud
"My science grade is bad" isn't a problem statement. It's a complaint.
"I lost points on the last three lab writeups, all in the conclusion section" is a problem statement. It has edges, it has a pattern, and it gives you somewhere specific to look.
Kids default to the complaint version because that's honestly how the frustration feels from the inside. Your job is to keep asking narrowing questions until the fog resolves into something you can actually work with: When does it happen? When does it not happen? What's different about those two situations?
That last question does most of the heavy lifting. The gap between when a problem shows up and when it doesn't is almost always where the cause is hiding.
A kid who can state a problem clearly has already done most of the solving. That's why the Problem Statement Builder is the first tool in the SOLVED method rather than the fourth — everything downstream depends on getting this part right.
Let them be wrong about the cause
This is the hard one, and I still catch myself getting it wrong.
Your kid is going to name a cause that isn't the cause. You'll see it immediately, and the urge to correct them is enormous — you're right, they're wrong, and fixing it takes about four seconds.
Don't. Ask how you could check whether that's really it.
Testing a wrong theory teaches something that being handed the right answer never does: that theories get verified rather than assumed. A kid who tests three wrong causes before landing on the real one has learned the actual skill. A kid who was told the right cause has learned that you're smart, which is a different lesson entirely.
It costs you time in the moment. What you get back is a kid who doesn't need you for this next time.
Say what worked before moving on
Most problem-solving ends the second the problem disappears. Everyone exhales and the afternoon resumes.
That's where the learning leaks out. The fix worked, but nobody said why it worked, so it doesn't transfer to the next situation.
Thirty seconds is enough to close that gap. What actually fixed it, and where else would that work? Two questions, and a one-time solution turns into something they can reuse.
What this looks like when it lands
It isn't a kid who never asks for help. It's a kid whose questions change shape.
You stop hearing "what do I do" and start hearing "I think the problem is this, because of that — does that sound right to you?" That isn't dependence. That's someone running a method and checking their work, which is what the rest of us do too.
The handoff is finished when they own the process and you've become the sounding board instead of the answer key. It's a different relationship, and a better one.
Where the method comes from
Those four moves are the front half of a six-step system I adapted from Six Sigma root cause analysis — the same structured approach engineers and hospitals use on problems that keep recurring. Scaled down to kid-sized problems, it works identically. State it clearly, watch for the pattern, list what might be causing it, verify which one actually is, fix that, and write down what worked.
None of it requires you to know the answer, which is the entire point. The method runs whether or not the adult in the room has any idea what's wrong, and that's what makes it something you can genuinely hand over.
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.