What Leaders/Managers Can Learn from The Explosive Child
A regional manager who runs performance conversations for underperforming employees sits across from her ten-year-old, staring at an unfinished math worksheet and silent refusal. At work, when someone repeatedly misses a deadline, she asks what's in the way and coaches the missing skill. At home, facing the same worksheet for the fifth night running, she reaches instead for a warning: no screens until it's done. The approach that built her reputation as a fair boss has vanished. Why does it disappear the moment the person across the table is hers?
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
A meltdown signals a missing skill, not insubordination
Any manager who has run a real performance conversation knows the difference between someone who won't do something and someone who can't yet do it. Ross W. Greene applies that distinction to explosive behavior: a child's frequent, intense meltdown usually signals a missing skill, flexibility, frustration tolerance, expressing needs under stress, not defiance aimed at you. Managers already resist labeling a struggling employee lazy before checking for a skill gap. The same discipline at home changes what a meltdown means before you respond.
The calm, diagnostic instinct you use at work evaporates fast when the person struggling is your own child at eleven at night.
Before reacting, ask the question you'd ask about a struggling report: what skill is missing here.
Find the specific recurring trigger, not the general complaint
A manager who tells HR "this employee has an attitude problem" gets nowhere; the useful version names the specific meeting or task causing friction. Greene's second cluster asks the same precision of parents: instead of treating every outburst as one behavior problem, identify the specific, recurring situation, a transition, a homework subject, that reliably sets it off. Once named, address that one unsolved problem directly, the way you'd build a coaching plan around one weak skill rather than a vague warning covering everything.
It's tempting to lump every meltdown into one label, tired, difficult, strong-willed, the same shortcut managers take with a hard employee.
Write down the last three meltdowns and look for the one situation they share.
Solve the problem with the child, not to the child
Good managers know a solution imposed on a struggling employee rarely sticks; the best coaching conversations build the plan together. Collaborative Problem Solving carries this into parenting: rather than announcing a consequence unilaterally, the parent invites the child to identify why the situation is hard and shape a solution both can live with. This is worth adopting as a general stance, not a full clinical script to run alone when behavior is severe or persistent; there, a professional should guide the collaboration itself.
Managers used to steering a conversation toward a predetermined outcome can turn collaborative into a review in disguise.
Ask your child what makes the moment hard before you say what you think should happen.
Progress here looks like a coaching arc, not a single fix
Managers know a real skill gap rarely closes after one feedback conversation; it closes gradually, through repeated coaching over a quarter. The same is true at home: as one unsolved problem gets addressed, meltdowns tend to ease in frequency and intensity over time, not overnight, while other unsolved problems remain to work through later. Judging the approach by one rough evening is like judging a coaching plan by its second day.
A manager's instinct to solve things efficiently can undercut all three ideas at once. Wanting to name the skill gap, find the trigger, and reach a solution in one conversation mirrors a rushed one-on-one that leaves someone feeling managed, not heard. When time is short, pick one flashpoint and one skill, set the rest aside, and let the conversation move at the child's pace, not the meeting's.
Name one thing, honestly
- Which meltdown pattern would you diagnose immediately if it happened on your team instead of at your table? - Where do you extend patience to a struggling employee that you withhold from your own child? - What changes if you treat tonight's flashpoint as a coaching problem instead of a compliance issue?
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
Ask your child what makes the moment hard before you say what you think should happen.