Using Collaborative Problem Solving to enhance RAIN meditation

What each one is actually for

Collaborative Problem Solving

Collaborative Problem Solving starts from a specific claim: a kid who blows up over homework, or shuts down every time a plan changes, isn't choosing that reaction out of defiance — they're hitting a gap between what's being demanded of them in that moment and a skill they don't yet reliably have, whether that's shifting flexibly when a plan changes, tolerating frustration, or putting a need into words instead of acting it out. The practice itself is done later, once the outburst has passed and both people are calm, never in the heat of it: you name the specific recurring situation in plain, blame-free language — 'starting math homework right after school seems really hard' — then get curious together about what's actually getting in the way, from the kid's side first and then yours, and only after that do you build a solution jointly, one you both had a hand in and that's realistic enough to actually survive contact with a Tuesday afternoon.

RAIN meditation

RAIN gives you four things to do, in order, while a feeling is actually happening rather than after you've already acted on it or shut it down. Recognize means naming plainly what's here — silently saying 'there's panic' or 'there's rage' rather than just being swept along inside it without noticing it has a shape and a name. Allow means letting that feeling stay present for a few seconds without immediately trying to make it stop, argue with it, or perform being fine — the hardest step, because every instinct in a strong feeling pushes toward ending it fast. Investigate turns gentle attention toward it: where do I actually feel this in my body, what does it seem to want. Nurture, last, asks you to respond to whatever you found the way you'd respond to a scared friend, often with an actual hand on your own chest or arm. Run start to finish, it takes well under two minutes and turns a feeling that was running you into something you can look at instead.

What you get out of pairing them

Collaborative Problem Solving buys you an end to a specific, exhausting loop: guessing at consequences for a behavior that was never actually about defiance, watching the consequence do nothing because it never touched the real problem, and escalating to a bigger consequence next time. Once you name the actual unsolved problem and build a solution the kid helped invent, you get a fix that holds, because nobody has to be coerced into following a plan they made themselves. RAIN buys you the thing that has to exist before any of that is possible at all: a body calm enough to be curious about someone else's experience rather than braced to win, escape, or shut the conversation down. Most Collaborative Problem Solving conversations that fail don't fail at the negotiating step — they fail before they start, because one person is still flooded and the whole thing turns into round two of the original blowup wearing a calmer voice. RAIN is the specific two minutes that keeps that from happening.

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 RAIN meditation rests on

• Interoceptive attention randomised trials
  Directing sustained attention to internal bodily sensations increases awareness of the body's state and changes how that state is experienced.
• Acceptance reduces struggle randomised trials
  Allowing an internal experience to be present without resisting or acting on it reduces the psychological struggle that resistance would otherwise intensify.
• Affect labeling reduces arousal randomised trials
  Putting an emotion into words reduces the physiological and psychological intensity it would otherwise carry while unexamined.
• Subject becomes object clinical practice
  Observing a thought, emotion, or part of oneself from a distance turns it into an object of attention rather than the assumed identity of the one experiencing it.

Where they actually meet

Both practices refuse to argue with the story that the surface behavior seems to be telling. Collaborative Problem Solving refuses 'he's just defiant' and insists on asking what's actually hard about the moment instead. RAIN refuses 'I shouldn't be feeling this' and insists on asking what's actually here instead. Each one takes something that looked like a verdict — on a child's character, on your own fitness to stay calm — and turns it back into a question with a findable answer.

The principle underneath both

Neither the outburst nor the wave of feeling is evidence about who anyone is. A recurring meltdown is a mismatch between a demand and a skill, not proof a kid is bad; a surge of fury or panic is a passing state with a shape you can examine, not proof about your character either. Both practices work only because they hold that line — the moment either one slides into treating the behavior or the feeling as a verdict on identity, the actual problem stops being visible and there's nothing left to solve.

What that makes the real goal

What both are actually reaching for is the same place: a moment where the difficult thing sitting in front of you, whether it's a recurring blowup or a surge of fury, has become workable material you can look at and respond to on purpose, rather than a crisis that's driving you or a character flaw you're stuck defending against. Get to that place and a real conversation becomes possible; stay short of it and every conversation is really just the original outburst continuing in a different room.

Other practices that serve the same goal

Nonviolent Communication, a structured way of separating what happened from a judgment about the person, and stating the feeling and the underlying need plainly instead of the accusation, reaches the same separation-from-verdict that both Collaborative Problem Solving and RAIN are built on, and has decades of use in mediation and family conflict work. Internal Family Systems treats a reaction — a part, in its language — as carrying its own protective logic rather than being the whole of who someone is, which is close kin to the claim that a behavior has positive intent, and its structured 'unburdening' work has begun accumulating trial evidence of its own, including in trauma-adjacent conditions. Cognitive defusion, the skill at the center of Acceptance and Commitment Therapy, reaches RAIN's half of the objective from a different angle — noticing a thought or feeling as an event passing through rather than a fact to obey — with a substantial randomized-trial base behind it.

A tradition that already does this

Thich Nhat Hanh's peace-treaty practice, used in some couples and family mediation traditions descended from his teaching, already builds in exactly this order: a required period of calming breath before either person is allowed to raise a grievance, on the explicit reasoning that a grievance raised from an agitated state cannot be heard as information and will only be heard as attack. The insistence on getting calm first, as a precondition rather than a nice-to-have, predates either of these two named practices.

Using Collaborative Problem Solving to enhance RAIN

RAIN on its own can settle a feeling and then just stop there — you feel better, but nothing about the recurring situation that keeps producing the feeling has actually changed, so the same wave shows up again tomorrow at the same time. Use the calm RAIN just bought you as the doorway into the Collaborative Problem Solving conversation rather than the end point: the moment Nurture has done its work and the body has come down, say out loud what the unsolved problem underneath the wave actually was — 'transitions in the morning are the hard part, not you being bad at mornings' — and stay in the room long enough to get curious about it together. Skipping this step is the single most common way both practices get used side by side and neither one ends up changing anything: RAIN keeps the peace in the moment, but the moment keeps coming back because nobody used the calm it created for anything.

Using RAIN to enhance Collaborative Problem Solving

The exact place a Collaborative Problem Solving conversation usually derails is the second step, getting curious about what's getting in the way, because that's precisely where an adult's own irritation tends to spike back up — the kid says something that sounds like an excuse, or nothing coherent at all, and the calm, curious voice slips into the old frustrated one. Build a private pass of RAIN into that exact moment: the instant you feel your own chest tighten mid-conversation, silently recognize it — 'there's my own impatience showing up' — allow it a few seconds without acting on it, notice where it's sitting in your body, and offer yourself the same steadiness you're trying to model. It takes under a minute and it happens without the child even noticing, and it's usually the only thing standing between a conversation that stays collaborative and one that quietly turns back into the adult delivering a verdict.

4:45 on a Tuesday, math homework, again

It's 4:45 on a Tuesday and your nine-year-old has just thrown a pencil across the room rather than start the math worksheet, the third time this month. Your own jaw is tight before you've said a word. You step into the hallway for ninety seconds and run RAIN on yourself: recognize the heat rising in your chest as anger mixed with dread about another fight, allow it to sit there without deciding yet what to do about it, notice it's sitting mostly in your shoulders and jaw, and put a hand on your own chest the way you'd put one on his shoulder if he were the one upset. By the time you walk back in, your voice has come down from where it was. You don't start with the worksheet. You sit down and say, plainly, 'starting math right when you get home seems like the hardest part, not the math itself.' He shrugs, then admits he's still thinking about a bad moment at recess and can't switch gears that fast. The solution you land on together — ten minutes of nothing, a snack, then math — is not one you would have thought of on your own, and it's one he doesn't fight starting the next three days running.

When this is worth reaching for

Same trigger, same outburst, on something close to a schedule — and every attempt at Collaborative Problem Solving's curious first question dies before it starts, because whoever is trying to ask it is still flooded from what just happened. At that point the obstacle isn't the child's reactivity; it's the adult's own nervous system, and no amount of wanting to be curious gets around a body that hasn't come back down yet.

Where this does not apply

Skip the RAIN step for a genuine one-off event with no pattern behind it — a single bad afternoon doesn't need a calming ritual and a formal problem-solving conversation, it needs an apology and moving on. And neither practice belongs in a moment of real physical risk, where a child or anyone else might hurt themselves or another person; that calls for an immediate safety response, not a two-minute meditation followed by a talk. Persistent, severe behavioral escalation is also a signal to bring in a clinician trained in this specific model rather than running it alone from a description on a page.

What the evidence does and does not support

Collaborative Problem Solving has substantial clinical and program-evaluation support — documented reductions in restraint and seclusion use in schools and residential settings that adopted it — built mostly on quasi-experimental and observational designs rather than randomized controlled trials. RAIN's individual components each carry stronger trial evidence from the broader mindfulness research base: directed attention to bodily sensation, allowing rather than suppressing an emotion, and putting a feeling into words are each separately supported by randomized studies. RAIN as a packaged four-step sequence, and using it specifically as a preparatory step before a Collaborative Problem Solving conversation, has not itself been tested; this page connects two practices with their own separate evidence, not a finding about running them together.