What Entrepreneurs Can Learn from The Explosive Child
A founder who debugs failed launches for a living stands in her kitchen at seven, watching her eight-year-old scream and throw a shoe because breakfast arrived in the wrong bowl. She runs postmortems on blown fundraises, always asking what's broken before prescribing a fix. Faced with the fourth meltdown this week, her instincts default to something older: dig in, hold the line, win the standoff. The sticker chart on the fridge hasn't moved in months. At work she treats a recurring failure as a signal to investigate, not punish. Why has she stopped asking that at home?
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 a hostile takeover
In a company, this sounds obvious: a team missing the same deadline usually lacks a specific capability, not the desire to succeed. Ross W. Greene applies the same logic to children: frequent, intense meltdowns usually mean a child lacks a skill, such as flexibility or frustration tolerance, not that they are choosing to defy you. A founder used to separating systems problems from people problems should grasp this quickly on paper. The harder part is home, where authority feels most tempting exactly when patience is lowest.
Running on four hours of sleep, a founder can know this and still hear a slammed door as insubordination.
Before responding, name the missing skill, the way you'd name a stalled deal's bottleneck.
The recurring flashpoint is the real problem, not the outburst
Founders know a vague complaint like "the product feels slow" is useless until you isolate the trigger. Greene's second insight asks the same of parents: stop treating every explosion as one blob called bad behavior, and name the specific, recurring situation, a transition, homework, a sibling exchange, that sets it off. Named precisely, the unsolved problem can be addressed directly instead of reacting to each episode as a fresh crisis, the same specificity a founder already demands elsewhere in the business.
Naming the trigger can feel like writing a spec instead of staying present with a struggling kid.
List two or three situations that reliably precede a meltdown, and work on one.
Solve it with them, not to them
A founder negotiating with a cofounder or investor knows an agreement imposed on one party rarely survives contact with reality. Collaborative Problem Solving applies that principle at home: instead of announcing a consequence unilaterally, a parent invites the child into naming the problem and shaping a workable solution together. This is a general principle worth borrowing, not a protocol to run solo when explosive behavior is frequent or severe, where collaboration should happen alongside professional guidance. It treats the child as a stakeholder, not someone managed toward compliance.
A founder used to closing deals fast may rush the child's input to reach a decision.
Ask what makes the flashpoint hard before offering your idea.
This is a slow release, not a fast patch
Founders are trained to prize the fast fix, the patch that ships tonight. This approach does not work that way. Skills develop gradually, and unsolved problems get resolved one at a time, meaning fewer and less intense meltdowns over months, not overnight compliance. Treating an early setback as proof the approach failed is the mistake of killing a promising product after one bad week of metrics. The gains are real, cumulative, and visible mostly in hindsight.
A founder's bias toward speed can collide with all three ideas at once. Wanting to resolve the unsolved problem in one sitting, the way you'd close a ticket, can override the reframe's patience and turn collaboration into a lecture. When that happens, shrink the ambition: pick one flashpoint, hold the skill-gap lens for that situation only, and let the conversation stay unhurried, even without a resolution today.
Name one thing, honestly
- Which recurring moment at home would you diagnose the way you'd diagnose a stalled deal? - Where have you demanded instant compliance from your child you'd never expect from a struggling teammate? - What changes if you treat one flashpoint as a shared problem rather than a rule to enforce?
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 what makes the flashpoint hard before offering your idea.