Why the Same Blowup Keeps Happening After You've "Fixed" It

What each one is actually for

Collaborative Problem Solving

Collaborative Problem Solving works one specific unsolved problem at a time, and the word specific is carrying most of the weight in that sentence. Ross Greene, the psychologist who developed the method, found that adults naturally describe the trouble at a size nothing can be done with — he's disrespectful, she never listens, bedtime is a nightmare — and that a problem stated that large has no solution attached to it, only a verdict. So the first discipline is shrinking it until it names one situation, one time of day, one expectation: not homework in general but starting homework in the twenty minutes after school, on the days there was no snack ready. The premise is that the behavior at that one spot is a skill coming up short against a demand rather than defiance, and the conversation runs in a calm moment in three moves — find out what is hard about that exact spot and listen to the real answer, state your own concern plainly, then build a plan for that spot together. The plan is kept deliberately small enough to actually happen, because a solution the person had a hand in building and can realistically pull off tomorrow is what changes the next repetition. An ambitious one nobody executes changes nothing, and quietly teaches both of you that these conversations do not work.

Tiny Habits

Tiny Habits, developed by behavior scientist BJ Fogg, starts from the opposite direction: instead of asking why someone lacks the motivation to keep a new habit, it asks whether the habit was ever sized to succeed in the first place. The method is to attach a version of the behavior so small it barely counts — two push-ups, one sentence in a journal, flossing a single tooth — to a moment that already reliably happens in your day, like right after you brush your teeth. The second half is not optional: the instant you do the tiny version, you deliberately generate a real feeling of success — a fist pump, saying "yes!" out loud, a genuine little rush — because that feeling, not the behavior itself, is what the brain uses to decide whether to repeat something tomorrow without being asked.

What you get out of pairing them

The payoff of Collaborative Problem Solving shows up the first time a solution actually holds past one good day, because a solution the child helped build is a solution the child understands and has some stake in — an imposed consequence stops tonight's outburst but leaves tomorrow's collision fully intact, since the actual obstacle at 4pm was never named, only punished. Naming it specifically — "the first ten minutes of homework are the hard part because I don't know where to start" — turns an unpredictable recurring fight into a solvable, bounded problem, which is a very different thing to live with than a character you're worried your kid has. Tiny Habits' payoff is quieter but just as real: it removes the need to talk yourself into the behavior every single day, because a habit that's been repeated enough times with a real feeling attached to it starts running closer to automatic, the way you don't negotiate with yourself about brushing your teeth. Both payoffs are really the same relief from two different angles — not needing to re-fight, from scratch, a battle that keeps recurring because the actual mechanism behind it was never addressed.

What Collaborative Problem Solving rests on

• Externalizing makes pattern visible randomised trials
  Putting an internal pattern into an external, structured form makes it visible and available for examination instead of remaining implicit and merely enacted.
• Parts have positive intent clinical practice
  A behavior that looks like misbehavior is usually a mistaken strategy aimed at meeting a legitimate underlying need rather than an expression of badness itself.
• Collaborative solution generation increases buy in observational studies
  Jointly generating a solution with the person who has the problem produces more durable follow-through than an imposed solution.

What Tiny Habits rests on

• Small wins compound randomised trials
  Repeating a small consistent action accumulates over time into a result too large to produce in a single step.
• Positive emotion wires in habit faster than repetition plausible mechanism
  An immediate authentic feeling of success after a behavior wires the habit in more effectively than repetition alone or reliance on willpower.
• Tiny behavior size lowers activation barrier observational studies
  Shrinking the target behavior to a very small size lowers the barrier to starting it bypassing dependence on motivation.

Where they actually meet

Set the two side by side and the overlap isn't in the subject matter — one is about a child's outburst, the other about an adult's flossing — it's in where each one refuses to stop looking. Collaborative Problem Solving refuses to accept "he's just defiant" as an explanation and keeps digging until it finds the actual expectation the child can't currently meet. Tiny Habits refuses to accept "I just don't have the willpower" as an explanation and keeps shrinking the ask until it finds a size the person can't fail at. Both are declining the easy, character-based story about why something keeps going wrong, and both replace it with a specific, fixable mechanism: a named obstacle in one case, a mis-sized behavior in the other.

The principle underneath both

A repeated failure that looks like a motivation problem or a character problem is usually neither, and it stops looking that way the moment you get specific enough about it. Ross Greene's line for this, in the child's case, is that kids do well if they can — the outburst isn't chosen, it's what happens when a real demand outruns a real skill, and the fix is finding out which skill and which demand. BJ Fogg's version, for a habit, is that behavior change is easier when you make the behavior tiny — the failure to floss isn't a discipline gap, it's that flossing all your teeth every night was never a realistically sized ask for a tired brain, and the fix is a size that survives a bad day. Once the failure has a specific named cause instead of a vague character verdict attached to it, there's finally something concrete to change.

What that makes the real goal

If replacing a vague, blame-shaped story with a specific, fixable one is what actually moves the needle, then the goal either practice is working toward is the same: get precise enough about what is actually failing — a skill gap at a particular moment, a behavior sized wrong for a particular kind of day — that the fix stops depending on someone simply trying harder next time. That target holds whether the recurring failure belongs to a seven-year-old at homework time or a forty-year-old with a gym membership; the work is diagnosis before prescription, in both cases, rather than a bigger consequence or a bigger goal.

Other practices that serve the same goal

Nonviolent Communication, a framework developed by psychologist Marshall Rosenberg for naming an unmet need underneath a reaction without turning it into blame, chases the same target Collaborative Problem Solving does — it just applies the move to any relationship, not specifically a child's outburst, and it has its own body of clinical and observational support for reducing defensiveness in a hard conversation. On the habit side, implementation intentions — psychologist Peter Gollwitzer's research on writing a specific "when X happens, I will do Y" plan in advance — serve a closely related objective to Tiny Habits' anchor-and-tiny-behavior structure, and they carry solid randomized-trial support of their own for closing the gap between intending something and actually doing it. Applied Behavior Analysis, an older clinical field built around figuring out the specific function a behavior serves before trying to change it, is worth naming here too: it independently arrived at both halves of this page's move — diagnose the real function of the behavior, then reinforce the replacement with something the person actually feels — for populations where guessing at motive gets it wrong most often.

A tradition that already does this

Positive Behavior Support, a framework that grew directly out of Applied Behavior Analysis and is now standard practice in a lot of special-education classrooms, already does close to exactly what this page is describing as a combination: a trained observer first works out the specific function a disruptive behavior is serving for a particular student — escape, attention, a sensory need — the same diagnostic move Collaborative Problem Solving makes conversationally with the child instead of about them, and then it teaches and reinforces a replacement behavior using small, immediate, genuine reinforcement the moment the replacement occurs — the same shaping-by-authentic-reward move Tiny Habits uses for an adult's flossing. Nobody built Positive Behavior Support by reading Ross Greene and BJ Fogg side by side; the two research lineages arrived at the same combined shape independently, which is some evidence the shape itself is doing real work rather than being a coincidence of these two specific books.

Diagnosing Why a Tiny Habit Still Isn't Sticking

Tiny Habits assumes that once a behavior is small enough, it will happen — and most of the time that's true, but when a tiny habit still keeps not happening after a couple of weeks, the standard advice is just to shrink it further, and sometimes that isn't the actual obstacle. This is where Collaborative Problem Solving's core move transfers cleanly, even without a second person in the room: instead of assuming laziness, sit down the way you'd sit down with a kid who keeps melting down at the same moment, and ask the same kind of specific, curious question of yourself — not "why can't I stick to this" but "what's actually going on, specifically, at the moment right after I brush my teeth, that makes two push-ups hard." Sometimes the honest answer is a real obstacle Tiny Habits' framework doesn't have a slot for — the anchor moment is rushed because you're already running late, or a partner is standing right there and it feels awkward. Naming that specific obstacle, the way you'd name a specific homework obstacle with a kid, often produces a fix Tiny Habits' general advice wouldn't have found: move the anchor, not the behavior.

Making the Agreed-On Fix Survive Past Tuesday

A Collaborative Problem Solving conversation ends with a plan both people built together — say, the child starts homework with the easiest subject first, for five minutes, before anything else — and that plan is genuinely better than an imposed one because the child helped make it. But a plan is still just an intention until something makes it happen automatically enough to survive a tired Tuesday, and this is exactly the gap Tiny Habits is built to close. Attach the new plan to something that already reliably happens — right after backpacks come off, right when the timer for screen time ends — and, critically, make the first five minutes something that gets a real, immediate, specific celebration the moment it's done: not a vague "good job" but something the child can feel, on the spot, every single time, for as long as it takes to stop needing it. The collaborative conversation supplied a plan the child actually believes in; the anchor-and-celebration structure is what stops that plan from quietly evaporating by Thursday the way good intentions from a calm conversation usually do.

Tuesday, 4:05pm, Homework Still Unopened

You've had the calm conversation. Two weeks ago, at a moment when nobody was upset, you sat down with your daughter and asked what actually happens at 4pm, and she told you, a little surprised to be asked: she doesn't know which problem to start with, and staring at the whole worksheet at once makes her want to leave the room. Together you built the plan — she opens the folder, does the first problem only, and then decides whether to keep going. It's Tuesday, and the plan is sitting on the table, unopened, same as the worksheet used to. Instead of treating this as proof the plan failed, you treat it as a sizing problem: the plan asked her to remember, unprompted, to open the folder — there was no anchor. So tonight you try it differently: the folder comes out the second her backpack hits the floor, before anything else happens, and when she does the first problem — just the one, nothing more required — you both actually notice it out loud, a real "there it is" instead of a passing nod. The plan she helped build didn't change. What changed is that it now has a specific moment to live in and a specific feeling attached to the instant it happens.

When this is worth reaching for

A recurring problem has already survived one round of consequences, or one round of good intentions, and neither touched it — which usually means the real obstacle was never actually named, only reacted to. It fits especially well when the person involved — a kid, or you — genuinely wants things to go differently and keeps failing anyway, because that combination points away from a motivation problem and toward a specific, findable gap: an unmet skill demand on one side, an ask sized wrong with no attached feeling on the other.

Where this does not apply

If the recurring behavior is genuinely dangerous, or involves another person being harmed, a calm collaborative conversation is not the first move — safety comes first, and Collaborative Problem Solving itself is explicit that some situations need an adult to simply impose a boundary rather than negotiate one. And if a habit is failing for a reason that has nothing to do with sizing or reward — a genuine scheduling conflict, a medical issue, a task that actually does require real skill-building rather than repetition — shrinking it and celebrating it will not fix what's actually broken; some problems need a skill taught or a schedule changed, not a smaller version cheered on.

What the evidence does and does not support

Collaborative Problem Solving has real outcome research behind it, mostly from clinical and school settings with kids who have significant behavioral challenges, showing reductions in explosive incidents when adults switch from imposed consequences to the collaborative conversation — that evidence is clinical and observational rather than a large body of randomized trials. The piece about a behavior needing to be tiny to survive comes from behavior-design research and has decent mechanistic backing for why small asks succeed more often, though the specific claim that a deliberate feeling of success wires a habit in faster than plain repetition rests more on theory about how reward and habit formation interact than on a large trial base of its own. Nobody has run a study that puts the two together — a collaborative diagnostic conversation followed by an anchored, celebrated tiny version of the resulting plan — so the case here is that each half is separately reasonable, not that the combination itself has been measured.