Rehearsing the Conversation Before the Blowup Happens
And how Assertiveness Training sharpens Collaborative Problem Solving in return.
Collaborative Problem Solving starts from the idea that a child's repeated outbursts, meltdowns, refusals, are almost never simple defiance, they are a signal that some specific demand is colliding with a skill the child does not yet have, an unsolved problem, and the fix is for the adult and child to name that problem together and build a solution neither one is forcing on the other. Assertiveness training teaches a different but related skill: stating your own need or limit directly and respectfully, neither swallowing it to keep the peace nor steamrolling the other person to get your way, and it builds that skill through rehearsal, practicing the actual words out loud before the real moment arrives. The two meet at the exact point Collaborative Problem Solving asks the most of an adult: the step where you have to state your own concern clearly, without lecturing or threatening, in the middle of a conversation that is already emotionally loaded. Assertiveness training's rehearsal is built for precisely that kind of moment, and practicing it in advance is what keeps an adult's honest concern from turning into a demand the moment things get tense.
What each one is actually for
Collaborative Problem Solving
Collaborative Problem Solving, developed by the psychologist Ross Greene, replaces punishment-and-reward discipline with a specific three-step conversation, sometimes called Plan B, that happens after things have calmed down, not during the outburst itself. First, the adult asks genuinely curious questions to understand the child's side, what's up when I ask you to stop the game and come to dinner, gathering real information instead of assuming the answer. Second, the adult states their own concern plainly, I need you to eat before you're starving and cranky at bedtime, without turning it into a lecture. Third, the two of them brainstorm together until they land on a solution that actually addresses both concerns, maybe a five-minute warning before dinner every night, rather than the adult simply announcing a consequence. The whole method rests on a specific premise: children do well if they can, and a repeated outburst usually means some skill, managing a transition, tolerating frustration, is still lagging behind what a situation demands of them.
Assertiveness Training
Assertiveness training treats the ability to state a need or a boundary clearly as a skill built through practice, not a personality trait some people simply have and others lack. It sits between two failure modes: passive communication, where a person's actual need goes unstated and gets silently absorbed until resentment builds, and aggressive communication, where the need gets stated in a way that blames, threatens, or overrides the other person. The core tool is the I-statement, a simple structure, I feel frustrated when the dishes sit for days, and I need us to split that task differently, that names the feeling, the trigger, and the actual request without accusation built in. The training part is not optional: people rehearse these statements out loud, often in role-play with a therapist, coach, or practice partner, working from low-stakes situations up to the harder real ones, because a sentence that sounds fine in your head frequently comes out clipped, apologetic, or sharp the first time you try to say it under real pressure.
What you get out of pairing them
Collaborative Problem Solving's payoff is durability: a solution the child helped build tends to actually get followed, because it addresses a real obstacle instead of just suppressing the behavior that obstacle was causing, which is why punishment-based approaches to the same outburst so often produce the identical outburst again the following week. Assertiveness training's payoff is that your actual need gets heard the first time, in a form the other person can act on, instead of arriving too late as blame, too early as a swallowed resentment, or too sharp as an ultimatum. Put together, what you get in a hard conversation with a child is an adult concern that lands as information rather than as a threat, which is exactly the ingredient Collaborative Problem Solving needs from the adult's side of the table and exactly the thing that rehearsal is built to make reliable under pressure.
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 Assertiveness Training 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.
-
Graded exposure reduces avoidance
randomised trials
Repeatedly approaching a feared or avoided stimulus or action within a controlled, tolerable structure reduces the fear and avoidance response it triggers.
-
Rehearsal builds skill fluency
plausible mechanism
Practicing a scripted response such as an I-statement in a low-stakes simulated setting builds automatic fluency that is available under the pressure of a real interaction.
Where they actually meet
Both practices refuse the same shortcut: one side simply winning. Collaborative Problem Solving refuses to let the adult's authority alone settle what happens, insisting the child's actual obstacle gets named and built into the fix. Assertiveness training refuses to let either swallowing your need or overriding someone else's settle a disagreement, insisting your own concern gets named clearly enough to be worked with. Neither is asking anyone to be less honest about what they want. Both are asking that the honest version get built into a solution jointly, rather than delivered as a verdict from whoever has more power or more willingness to escalate.
The principle underneath both
A resolution reached by one side dominating, a punishment handed down, a demand pushed through, or by one side disappearing, a swallowed need, a suppressed complaint, has not actually resolved the mismatch that caused the friction. It has only hidden it, and a hidden mismatch resurfaces later, usually in a worse form: the same outburst next week, the resentment that finally erupts over something small. A solution holds only when it is built from both people's actual, honestly stated constraints, which means someone has to state theirs clearly enough for it to be usable, and someone has to actually listen to the other's rather than assuming it.
What that makes the real goal
Once the target is durability rather than a quick end to a specific fight, the actual work in both practices is getting real constraints onto the table, plainly and without blame, from both people, and then building something that accounts for both rather than overriding one. That is a more specific and more teachable target than 'communicate better' or 'be a calmer parent': it is the skill of stating your own side clearly enough that it can be worked with, paired with the discipline of actually asking for and using the other person's side instead of assuming you already know it.
Other practices that serve the same goal
Nonviolent Communication pursues an almost identical target through its own four-part structure, stating an observation, a feeling, a need, and a request, specifically designed to express a need without embedding blame in the sentence, and it has a body of mostly observational and practitioner evidence behind it rather than large randomized trials. Interest-based negotiation, the approach behind books like Getting to Yes, separates a stated position, I want you to stop doing that, from the underlying interest driving it, I need to not be interrupted in meetings, and then generates options that satisfy the interest rather than just the position, with support mainly from negotiation research and practitioner case study rather than clinical trials. Motivational interviewing, used heavily in health behavior change, gets a person to state their own reasons for changing rather than having a clinician impose the reason, and carries strong randomized-trial support specifically for that mechanism. None of these three shares a common origin with Collaborative Problem Solving or assertiveness training; each independently landed on naming the real constraint honestly as the thing that has to happen before a durable solution can exist.
Using Collaborative Problem Solving to enhance Assertiveness Training
Assertiveness training gets you to a clean, well-formed statement of your own need, but it says less about what happens the moment the other person's response is not simply agreement, especially when that response is itself a reaction to some unstated problem of their own. Borrow Collaborative Problem Solving's core assumption, that difficult pushback usually signals an unsolved problem on the other side rather than simple opposition, and use it the moment your assertive statement gets a defensive or resistant response. Instead of repeating your I-statement louder or backing off entirely, ask the same kind of genuinely curious question Plan B opens with: 'what's making that hard for you?' A coworker who bristles at your direct request to stop being copied on every email might be worried about being blamed later if something slips through unnoticed, an obstacle a slightly different version of your original request can actually solve. Treating their resistance as information rather than as proof your assertiveness failed is what turns a stated boundary into an actual working agreement.
Using Assertiveness Training to enhance Collaborative Problem Solving
The step of Plan B where the adult states their own concern is, in practice, the step that goes wrong most often, because a concern that has been building through a hard week tends to come out as a lecture, a comparison to your sibling, or a thinly veiled threat, none of which is what Collaborative Problem Solving is actually asking for. Before a planned Plan B conversation, especially about a recurring issue, write your concern out as a single I-statement in advance, and say it out loud, alone or to a partner, at least once before you sit down with the child: 'I feel worried when homework isn't done by bedtime, because I need you to get enough sleep for school.' Rehearsing the sentence separately from the actual conversation is what keeps it short, calm, and free of the accusatory edge that creeps in when you are composing it live, under the stress of a child who is already frustrated. The rehearsed version is also easier to actually remember and say cleanly in the moment, which matters because a concern that comes out as three run-on sentences of frustration is much harder for a child to actually work with than one clean statement.
The nightly homework fight, rehearsed at the kitchen counter alone first
It is Sunday evening, calm, no fight happening right now, and you are standing at the kitchen counter thinking about the homework battle that has played out four nights running. Under the old pattern, tomorrow's version starts with you finding the backpack still zipped at eight-fifteen, and everything you say from that point on comes out sharp, already halfway to a threat about screen time. Tonight, instead, you say the sentence out loud to the empty kitchen first: 'I feel anxious when homework isn't started by seven, because I need you to get to bed on time and not be exhausted for school.' It sounds stiff the first time. You say it again, plainer. The next evening, when you actually sit down with your kid, the sentence comes out close to how you practiced it, calm, specific, no comparison to anyone else. Your kid, instead of the usual flat 'I don't know' to why the backpack sits untouched, actually says something: the math worksheet has a problem type nobody explained in class, and starting it feels like starting a fight they already know they'll lose. You did not see that coming, and you would not have heard it at all if your own opening line had come out as an accusation.
When this is worth reaching for
The same fight keeps coming back every few days — homework, screen time, the chores that never get done — and each time you open your mouth to state your own limit, it comes out as a lecture instead of a request. There is room to prepare here: a calm moment before the next round, not a crisis argued in real time, which is exactly what assertiveness rehearsal needs and exactly what Plan B gives it — a chance to practice the adult's honest concern out loud before the actual conversation happens.
Where this does not apply
If a child's behavior involves a safety risk in the moment, running out into traffic, hitting a sibling, the response has to be immediate physical intervention, not a calm, rehearsed conversation that happens later; Collaborative Problem Solving's Plan B is explicitly for after things have settled, not during a crisis. And if what looks like defiance is actually a developmental or clinical issue outside a parent's ability to assess, a significant language delay, an undiagnosed learning difference, both the collaborative conversation and the rehearsed I-statement are working on the wrong layer of the problem, and an evaluation by a qualified professional should come first.
What the evidence does and does not support
Collaborative Problem Solving has been studied mainly in observational and quasi-experimental research in schools and inpatient psychiatric settings, generally showing reduced behavioral incidents compared with punishment-based approaches, though it has fewer large randomized controlled trials than some competing behavioral parenting programs. Assertiveness training's core technique, rehearsing a scripted response before using it in real situations, has mechanistic support from skill-acquisition research generally rather than trials specific to parent-child concern statements. Nobody has studied rehearsing an I-statement specifically before a Plan B conversation as its own tested intervention; this page's suggestion combines two separately supported ideas, it is not a validated protocol.
Practice this with IX Coach
The two practices on their own
Other pairings with these practices
- 168 Hours Time Audit and Assertiveness Training
A time log shows exactly which yeses are draining your week. It can't make the next no easier to say — here's what does that job.
- 90-Second Rule and Assertiveness Training
One practice waits out a surge of emotion; the other rehearses the words to say next. Together, you speak from steadiness instead of the spike.
- Action Planning (Implementation Intentions) and Assertiveness Training
Knowing what you should say and saying it in the moment are two separate skills. Here's the planning-plus-rehearsal fix, and when it won't be enough.
- Attention Management and Assertiveness Training
A protected work block only survives contact with a real interruption if you've already decided, and rehearsed, exactly what you'll say.
- Behavior Design (Environment Design) and Assertiveness Training
Assertiveness training builds the script; environment design removes the friction that keeps you from ever saying it out loud.
- Calm Company Design and Assertiveness Training
Calm company design pre-builds quiet into how a team works. Assertiveness training pre-builds a direct response into a person. The same logic, twice.
- Collaborative Problem Solving and 168 Hours Time Audit
A time log gives a CPS conversation actual evidence instead of impressions. Where the two fit, and where a log turns into surveillance instead.
- Collaborative Problem Solving and 25/5 Rule (Two-List Strategy)
A method for finding a child's hidden reason and a method for ruthlessly cutting a goal list share one move: naming what you're actually solving for.
- Collaborative Problem Solving and 5-4-3-2-1 Grounding
A child mid-meltdown can't do Plan B's give-and-take. 5-4-3-2-1 grounding may be the missing step that gets them there first.
- Collaborative Problem Solving and 90-Second Rule
A joint diagnosis can't happen while someone's still flooded. One reading of why the 90-second wait has to come before Collaborative Problem Solving.
- Collaborative Problem Solving and Acceptance and Commitment Therapy (ACT)
One practice catches a child's outburst before it's punished; the other catches the adult's own snap judgment about it. Here's how they meet.
- Collaborative Problem Solving and Accountability Partners
Collaborative Problem Solving builds a plan a kid agreed to. Accountability partnerships add the follow-up that keeps a good plan from quietly dying.
The principles underneath both
- externalizing makes pattern visible
Putting an internal pattern into an external, structured form makes it visible and available for examination instead of remaining implicit and merely enacted. Shared by 47 practices in the corpus — here in 168 Hours Time Audit.
- parts have positive intent
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. Shared by 3 practices in the corpus — here in Internal Family Systems (IFS).
- small wins compound
Repeating a small consistent action accumulates over time into a result too large to produce in a single step. Shared by 37 practices in the corpus — here in Agile Results (Getting Results the Agile Way).
- graded exposure reduces avoidance
Repeatedly approaching a feared or avoided stimulus or action within a controlled, tolerable structure reduces the fear and avoidance response it triggers. Shared by 22 practices in the corpus — here in Boundaries (Saying No Practice).