If you asked me which step of the SOLVED method matters most, I would not pick the one about finding the root cause, even though that is the one people find most interesting. I would pick the first one: state the problem right. It is the step kids rush, and it is the step adults rush too.
It is so easy to rush it after you get a complaint. You form an opinion about it in the first ten minutes, and spend the next two weeks proving that opinion right. More often than not, you solved a problem that was not the one you actually had.
What "state the problem right" means
A good problem statement says what is happening, when, where, and how often, without including a cause or a blame. That sounds simple. In practice it is the hardest discipline in the whole process, because our brains want to skip straight to explanations.
Compare two ways a kid might describe the same situation:
- "My brother is always messing up my stuff."
- "Twice this week, my charger was missing from my desk when I got home from school."
The first one has a villain and a conclusion already built in. The second one has facts. Only the second one leaves room to discover that the charger keeps ending up in the kitchen because that is where the only free outlet is.
Why everything depends on it
Every later step works on whatever the first step hands it. If the problem statement already contains a guess about the cause, the observations get filtered through that guess, the root cause search goes looking for proof, and the fix could be aimed at the wrong target. The process still runs. It just runs on bad input.
Engineers have an old phrase for this, garbage in, garbage out, and it applies to thinking as much as to computers. A clear statement at the start is the cheapest quality control you will ever do.
How to help a kid slow down
A few prompts make a real difference. When your child describes a problem, try asking:
- What exactly happened, in a way a stranger could picture?
- When did it happen, and has it happened before?
- Can you say it without saying whose fault it is?
- How would we know if it stopped happening?
That last question quietly sets up the evaluate step later, because a problem you can describe clearly is a problem you can check. Picture a kid who learns to ask it every time. That kid is going to be very hard to fool with a fix that only looks like it worked.
It feels slow, but it is faster
Kids will tell you this step is boring, and they have a point. It is less fun than guessing. But a few extra minutes here routinely saves hours later, because you stop fixing things that were never broken. I make an effort to complete this right every time I do it, and I have been doing this for a long time.
Stating problems at different ages
Younger kids need more support with this step, and that is normal. A seven-year-old might only get as far as "my shoes are hard to find in the morning," which is a perfectly good start. By ten or eleven, most kids can add when it happens and how often. By the early teens, they can usually leave the blame out entirely if someone reminds them to.
Whatever the age, resist the urge to rewrite the statement for them. A clumsy problem statement your kid wrote teaches more than a clean one you wrote, because the struggle to say it clearly is the skill.
A quick test for any problem statement
Here is a check I still use on myself. Read the statement back and ask whether it could be true no matter what the cause turns out to be. "The charger was missing twice this week" passes, because it stays true whether the cause is a sibling, a pet, or an outlet. "My brother takes my charger" fails, because it has already decided. If the statement only works for one cause, it has a guess hiding in it.
That one test catches most of the mistakes I see, in kids and in professionals.
Practicing the first step
The SOLVED Complete Bundle includes the kids' book, which teaches all six steps with practice problems, and the companion for the adult coaching them. To practice just this step, the free worksheet at https://solved360.com/pages/free starts with a problem statement on a real situation from your child's week. It is a good place to see how much the first step changes.