What Parents Can Learn from The Explosive Child
It is the third meltdown before breakfast, this time over a sock seam, and a parent stands in the hallway holding a shoe, trying to remember calm-parenting advice from a podcast two weeks ago. The consequence chart worked for a while, then stopped. The reward chart worked for a while, then stopped. Every approach that works cleanly on other people's kids fizzles within a month here, and the parent now dreads ordinary transitions, socks, screens, homework, the way some dread a stretch of highway. Nothing feels like defiance exactly, but it doesn't feel like anything else either. What is actually happening, and why does punishing it only make it worse?
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Meltdowns are a missing skill, not manipulation
Ross W. Greene's central claim is direct: a child having frequent, intense meltdowns is usually missing a specific skill, flexibility, frustration tolerance, or words to express a need, not choosing to manipulate. This doesn't mean the meltdown is acceptable, or that nothing needs to change. It means the first question shifts from how do I stop this to what is actually hard for my child right now. If conventional discipline hasn't worked, that doesn't mean you failed; the tool didn't match the problem.
Mid-meltdown, in public, this reframe is hardest to hold onto exactly when you need it most.
Once things calm down, ask what skill your child seemed to be missing in that moment.
Find the specific unsolved problem behind the pattern
Not every meltdown is the same meltdown wearing a different outfit. Greene's second insight asks you to look past "he has tantrums" toward something specific: transitions off screens, a homework subject, mornings before school. These are unsolved problems, and each can be worked on separately rather than treated as one giant behavior issue. Naming the pattern turns an overwhelming situation into a shorter, workable list, and lets you notice progress on one front even while another remains unsolved.
When exhausted, every meltdown can blur into one crisis instead of distinct, nameable problems.
Write down the last five meltdowns and note what happened right before each.
Solve problems with your child, not just to your child
Collaborative Problem Solving means bringing your child into the conversation about a specific unsolved problem, asking what makes it hard, and building a solution together rather than announcing a consequence alone. This is a principle worth carrying into everyday moments, not a protocol to run solo if your child's explosive behavior is frequent or severe, where a professional should help guide the process. Used well, in calm moments rather than mid-meltdown, it treats your child as someone with useful information about their own struggle.
Trying to collaborate mid-meltdown usually backfires; timing matters as much as the method.
Pick one recurring problem and raise it during a calm moment, not during or after an episode.
Change here is gradual, one problem at a time
This approach rarely produces overnight transformation, and expecting one sets you up to feel it failed after a hard week. Skills build gradually, and unsolved problems get resolved one at a time, meaning fewer and less intense meltdowns over months, not instant compliance tomorrow. Parents who tried faster fixes may find this pace frustrating, but the slower trajectory is the actual mechanism, not a disappointing substitute for one.
These ideas can pull against each other on an ordinary hard day. You may see the skill gap clearly but not know the unsolved problem behind it, or know the problem but lack energy for a collaborative talk after a long day. When that happens, it's enough to hold the first idea, this is a missing skill, not defiance, and let the rest wait. Partial progress on one cluster still counts.
Name one thing, honestly
- Which recurring flashpoint in your house would you describe differently if you assumed a missing skill instead of defiance? - Where have you blamed yourself for a conventional approach that simply did not fit this problem? - What would change if you tackled one unsolved problem this month instead of trying to fix everything at once?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Pick one recurring problem and raise it during a calm moment, not during or after an episode.