Using Collaborative Problem Solving to enhance Learned Optimism
And how Learned Optimism sharpens Collaborative Problem Solving in return.
Collaborative Problem Solving, developed by psychologist Ross Greene, is built on a specific claim: a child's outburst, a meltdown, a refusal, a shutdown, is a sign that some expectation is outstripping a skill the child does not yet reliably have, not a sign of defiance, and the fix is for the adult and child to sit down together, name the actual unsolved problem behind the specific moment it keeps happening, and build a plan neither of them could have written alone. The ABCDE method, from Martin Seligman's research on learned optimism, is a five-step way of catching and revising a pessimistic explanation right after something goes wrong: notice the Adversity, the setback itself; notice the Belief you automatically formed about why it happened; notice the Consequence, the feeling and urge that belief produced; Dispute the belief the way you would dispute a claim a lawyer made against you, with actual evidence; and notice the Energization, the shift in how you feel once a more accurate belief replaces the pessimistic one. The link between them is not obvious from the names, but it is direct: Collaborative Problem Solving only works if the adult has already revised a specific pessimistic belief about the child, "he's doing this on purpose," into a more accurate one, and the ABCDE method is a precise, repeatable way to do that revision instead of hoping it happens by itself.
What each one is actually for
Collaborative Problem Solving
Collaborative Problem Solving rests on a single reframe Ross Greene states directly: kids do well if they can, not kids do well if they want to. When a child repeatedly melts down over a specific, identifiable situation, getting dressed in the morning, transitioning off a screen, a worksheet with too many steps, the model treats that as evidence of a specific skill gap or unsolved problem rather than a character flaw or a bid for attention, and it addresses it through a structured three-part conversation: the adult first reflects the child's own concern back accurately ("you really don't want to stop the game right when it's over"), then states the adult's own concern plainly ("and I need us out the door by eight"), and finally invites the child to help build a plan that could actually work for both concerns at once, rather than the adult simply deciding and enforcing one. You can picture the whole conversation happening at a kitchen table, both people talking, neither one lecturing.
Learned Optimism
The ABCDE method gives you a fixed sequence to run right after something goes wrong, built specifically to catch a pessimistic explanation before it hardens into a mood or a decision. Adversity is simply naming the actual setback, plainly, without embellishment. Belief is noticing the automatic explanation your mind supplied for why it happened, often instantly and without your really choosing it, something like "I always mess this up." Consequence is noticing what that belief did to you, the flatness, the urge to give up, the anger. Disputation is where the real work happens: you argue against your own automatic belief the way a good lawyer would argue against a weak accusation, using actual evidence, not just repeating a nicer-sounding belief instead. Energization is simply noticing what shifts, usually a measurable lift in mood or motivation, once a more accurate belief has actually replaced the automatic one.
What you get out of pairing them
Collaborative Problem Solving asks a lot of an adult in a hard moment, curiosity instead of judgment, toward a child who has just, for the third time this week, thrown something or screamed or shut down, and that curiosity is extremely difficult to produce on command if the adult's own automatic belief in that moment is some version of "he's doing this on purpose" or "nothing I try ever works with her." The ABCDE method gives that adult a specific, few-minutes procedure for actually revising that belief with real evidence, rather than just being told to be more patient, which is advice almost nobody can follow while genuinely believing the pessimistic story underneath their frustration. And Collaborative Problem Solving, in turn, gives ABCDE's Disputation step something it usually lacks when practiced solo: an external, jointly built process for actually testing a belief against evidence, sitting down with the very person the belief is about and finding out, together, what is actually going on, rather than disputing a belief alone in your own head with only your own evidence to work from.
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 Learned Optimism rests on
-
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.
-
Explanatory style shapes resilience
randomised trials
The habitual way a person explains negative events shapes their vulnerability to giving up and to low mood.
-
Disputation updates automatic belief
clinical practice
Actively arguing against a pessimistic automatic belief the way one would dispute another person's claim changes the emotion and behavior that follow it.
-
Energization follows cognitive reframe
practitioner report
Successfully disputing a negative belief produces a measurable shift in energy and motivation immediately afterward.
Where they actually meet
A first, snap explanation for why something bad just happened gets rejected in both cases, replaced instead with a more specific, examined account before either practice lets a decision get made. Collaborative Problem Solving refuses the snap explanation "he's misbehaving" and replaces it with a specific unsolved problem, arrived at jointly, that can actually be worked on. The ABCDE method refuses the snap explanation "I always fail at this" and replaces it with a disputed, evidence-checked belief that can actually be trusted. Different subject, a child's behavior in one case, your own automatic thought in the other, but the identical refusal: do not act on the first, global, unexamined story a hard moment hands you.
The principle underneath both
A global, trait-level verdict, "he's just like this," "I'm just bad at this," delivered right after something goes wrong, forecloses the specific investigation that would actually let anyone do something useful about it, while a narrow, examined, evidence-based account of what actually happened this time leaves room to act. Neither model says this in so many words, but it is what both are actually protecting against. Both practices work by deliberately slowing down at the exact moment a global verdict wants to form, and insisting on specificity instead, what actually happened, right here, this time, before letting any verdict about a whole person, child or self, stand.
What that makes the real goal
If a premature global verdict is what blocks useful action, the real goal shared by both practices is replacing that verdict with a specific, checkable account of an actual mechanism, this particular expectation outstripping this particular skill, this particular setback triggering this particular automatic thought, before deciding what happens next. Framed this way the objective is not really about parenting or about optimism specifically; it is about refusing to let a hard moment write a permanent story about a person, and insisting instead on a story specific enough to actually test.
Other practices that serve the same goal
Functional Behavior Assessment, a standard tool in applied behavior analysis and special education, pursues the identical objective for a child's challenging behavior through a different structure: instead of a joint conversation, a trained observer tracks what happens right before and right after the behavior across many instances to identify its actual function, escape from a hard task, attention, a sensory need, and this antecedent-behavior-consequence approach has a substantial observational and quasi-experimental evidence base within behavior-analytic research. Attribution retraining, the broader research tradition Seligman's own work on learned optimism grew out of, pursues the same objective for a person's own explanatory habits through classroom and workplace interventions that teach people to reassign the cause of a setback from a global, permanent trait to a specific, changeable one, and this broader body of research carries stronger experimental support than the ABCDE method's own specific five-letter packaging.
A tradition that already does this
Collaborative Problem Solving already performs a version of ABCDE's Disputation step at its own foundation, even without using that name. Ross Greene's central instruction to adults, replace the belief kids do well if they want to with kids do well if they can, is structurally identical to Disputation: it takes a pessimistic, blame-assigning automatic belief about why the behavior is happening, names it plainly, and argues against it using the actual evidence of where and when the behavior occurs, before any collaborative conversation with the child is allowed to start. The two methods arrived at the same move independently, one built for parents and teachers facing a child's meltdown, the other built for anyone facing their own after a setback, which is itself a sign the move belongs to neither field alone.
Using Collaborative Problem Solving to make Disputation less lonely
ABCDE's Disputation step asks you to argue against your own automatic belief using real evidence, but done entirely alone, inside your own head, it is easy to just quietly agree with yourself and call it evidence. Borrow Collaborative Problem Solving's actual structure for the Disputation step itself, whether the belief is about a child's behavior or your own: instead of disputing it solo, sit down with someone who has direct knowledge of the situation, a co-parent, a colleague, even the person the belief is about, if that is appropriate, and walk through it the way a Collaborative Problem Solving conversation runs, stating the belief plainly, asking what they have actually noticed, comparing that against specific instances rather than an overall impression. A belief tested against someone else's independent observations is considerably harder to quietly rubber-stamp than one tested only against your own memory of events.
Using the ABCDE method to get the adult ready for a Collaborative Problem Solving conversation
Collaborative Problem Solving fails most often before the actual conversation even starts, in the adult's own head, in the minutes after another outburst when a pessimistic belief like "he does this deliberately" or "nothing I try ever works" has already formed and is already shaping a tense, closed voice the child will pick up on immediately. Run the ABCDE sequence first, on paper if that helps: name the Adversity plainly, this specific outburst, at this specific moment; name the automatic Belief, written out exactly as it sounds in your head, not softened; notice the Consequence, the anger or hopelessness it produced; Dispute it with actual evidence, does this outburst actually cluster around a specific trigger, transitions, a particular subject, rather than happening randomly, which would undercut "on purpose"; and notice the Energization, whatever shift in your own state follows. Only once that shift has actually happened are you in a state to run the real conversation with anything like genuine curiosity instead of a performance of it.
4:15pm, the backpack thrown across the room, again
It is 4:15 on a Tuesday and your son has just thrown his backpack across the room rather than starting his homework, the third time this week, and the thought that arrives before you have even decided to think it is "he's doing this to get out of work, he knows exactly what he's doing." You feel your jaw tighten and you are one sentence away from a consequence you will regret announcing. Instead, you stop, actually stop, and run it: Adversity, backpack thrown, third time this week, right at homework start. Belief, written honestly, "he's manipulating me, he doesn't actually struggle, he just doesn't want to." Consequence, that hot, righteous anger, the urge to punish rather than understand. Disputation: all three times this week were at homework start, specifically math homework, not reading, not chores; if this were pure manipulation you would expect it randomly, not clustered around one specific subject, which looks a lot more like a skill gap around math than a deliberate choice. Energization: the anger is still there, but underneath it now is something closer to curiosity. You sit down, not across from him like a judge but next to him, and you ask what actually happens in his head right when he opens the math folder. The conversation that follows is short, and it is the first one all week that is not a fight.
When this is worth reaching for
The gap is between a Collaborative Problem Solving conversation being technically scheduled and it actually going well: the adult already knows the model in theory but keeps noticing their own frustration or blame taking over before the conversation even starts. It is most useful run as a quick, private step immediately before a planned or spontaneous CPS conversation, not as a lengthy separate exercise done well after the moment has passed and the adult has already reacted.
Where this does not apply
If a child's behavior involves a genuine safety risk to themselves or others in the moment, this is not the moment for either a disputation exercise or a collaborative conversation; safety comes first, and the reflective work described here belongs to the calmer follow-up conversation, not the crisis itself. And the ABCDE method is not well suited to disputing a belief that turns out, on honest evidence, to be accurate, if a pattern really is a deliberate, chosen behavior in a specific case, forcing a more charitable belief onto real evidence is not disputation, it is self-deception, and Collaborative Problem Solving's own model still expects consequences to exist alongside the collaborative conversation, not instead of it.
What the evidence does and does not support
Learned Optimism's explanatory-style research, that a habitually pessimistic way of explaining setbacks predicts lower resilience and higher risk of low mood, has randomized-trial support, and the broader attribution-retraining tradition it grew from has been tested experimentally across school and workplace settings. Collaborative Problem Solving has observational and clinical support, including studies in school and juvenile-justice settings showing reduced behavioral incidents, but weaker controlled-trial evidence than the explanatory-style research behind ABCDE, and its core claim, that most challenging behavior reflects a lagging skill rather than a choice, is a clinical framework rather than a directly measured finding for every individual case. No study has tested using the ABCDE method specifically to prepare an adult for a Collaborative Problem Solving conversation, or using a CPS-style joint conversation as a structured version of Disputation; this page connects two separately evidenced frameworks rather than reporting a tested combination.
Practice this with IX Coach
The two practices on their own
Other pairings with these practices
- Behavior Design (Environment Design) and Learned Optimism (ABCDE Method)
Changing what's easiest to do handles the moment before a setback. A five-step way to argue with your own pessimism handles the moment right after.
- 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.
- Collaborative Problem Solving and Action Planning (Implementation Intentions)
A solution both of you agreed to can still fall apart by Tuesday. Two different reasons that happens, and two different fixes for each.
- Collaborative Problem Solving and Active-Constructive Responding
Handling a child's meltdown and hearing a partner's good news lean on the same skill: staying curious before you react. How to borrow each one.
- Collaborative Problem Solving and Active Listening (Reflective Listening)
The empathy step in Ross Greene's method IS reflective listening, just under a different name. Here's what that overlap actually buys a struggling parent.
- Collaborative Problem Solving and Assertiveness Training
A child's outburst is usually an unsolved problem, not defiance. Rehearsing how you'll name your own concern, calmly, changes how that talk goes.
- Collaborative Problem Solving and Atomic Habits (Habit Stacking / Cue-Craving-Response-Reward Loop)
A collaborative fix often lacks a cue to trigger it; borrowing the habit loop can be what makes an agreed-on solution actually happen at home.
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).
- subject becomes object
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. Shared by 10 practices in the corpus — here in Affect Labeling.
- explanatory style shapes resilience
The habitual way a person explains negative events shapes their vulnerability to giving up and to low mood. Shared by 2 practices in the corpus — here in Learned Optimism (ABCDE Technique).