Using Collaborative Problem Solving to enhance Pleasant Events Scheduling

And how Pleasant Events Scheduling sharpens Collaborative Problem Solving in return.

Collaborative Problem Solving, often shortened to CPS and also called Plan B, has an adult and a child sit down and jointly work out the specific unsolved problem behind a recurring outburst, instead of treating the outburst itself as something to punish. Pleasant Events Scheduling puts enjoyable activities onto a calendar and does them on a set schedule, on the finding that mood usually follows action rather than the other way around, so a flat week gets treated as a gap in scheduled activity rather than a lack of willpower. On this reading, the useful overlap is narrow but real: when someone resists the very activity a schedule put in front of them, a CPS-style conversation about what is actually making it hard to start can surface a specific, fixable obstacle that a schedule alone has no way to ask about. The two are not solving the same problem in general — one diagnoses, one schedules — and whether running them together beats either alone has not been measured.

What each one is actually for

Collaborative Problem Solving

Sit next to the person, not across from them, and ask what is actually making a specific recurring behavior hard right now — not in general, tonight. Ross Greene, the child psychologist who developed the approach, built it on the premise that a kid who is struggling is missing a skill or facing an unsolved problem, not choosing to misbehave, so the conversation has three concrete moves: name the other person's concern in neutral language first, without judgment, then name your own concern about the behavior, then invite them to help build a solution that actually addresses both concerns. You are not handing down a fix. You are finding out, together, what specifically is in the way.

Pleasant Events Scheduling

Write a short list of activities that reliably feel good — a walk, a call with a specific friend, fifteen minutes with a book, nothing elaborate — and put them on the calendar for specific days and times, the same way you would schedule a dentist appointment. Then do them on schedule, regardless of whether you feel like it that day. The premise is that waiting to feel motivated before acting usually means waiting a long time, because for a flat or low mood, motivation tends to show up after the action, not before it, so scheduling makes the activity happen on the strength of the calendar entry rather than on the strength of how you feel that morning.

What you get out of pairing them

The reason to reach for CPS here rather than more encouragement is that encouragement assumes the person already knows what is wrong and just needs a push, and often they do not — the specific thing making Tuesday's walk hard to start is usually more concrete and more fixable than 'low motivation,' and a five-minute joint conversation can surface it in a way that pep talks cannot. The reason to reach for Pleasant Events Scheduling rather than waiting to feel like doing something is that the wait can go on indefinitely once mood is flat, and a calendar entry gives the day a fixed point to act from instead of a mood to negotiate with. Together, what a person gets is a schedule that survives contact with a bad week, because when it stalls, there is a way to ask why beyond 'try harder.'

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 Pleasant Events Scheduling 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.
  • Behavioral activation precedes motivation randomised trials
    Taking action before motivation appears, rather than waiting for motivation to arise first, itself generates the motivation and improved mood that waiting would delay.

Where they actually meet

Both practices refuse the same shortcut: reading a stuck person as simply uncooperative or simply unmotivated. CPS reads a recurring outburst as a mistaken strategy for an unmet need and goes looking for the specific need. Pleasant Events Scheduling reads a flat week as a gap in scheduled input and goes looking for what got left off the calendar. Where they actually touch is narrower than that shared instinct: it is the specific moment when a scheduled pleasant activity itself becomes the thing being resisted, because that is the one point where CPS has something to diagnose and PES has nothing built in to ask.

The principle underneath both

A person who is not doing the thing that would help them is not, on either account, lacking desire. Something specific is in the way of the doing — a felt obstacle CPS is built to name, or a missing calendar entry PES is built to supply — and naming or supplying that specific thing does more than repeating the instruction to just do it.

What that makes the real goal

Find the specific, nameable thing standing between a person and an action they already have reason to want, and either remove it or schedule around it, rather than treating the gap between wanting and doing as a character trait.

Other practices that serve the same goal

Functional behavior assessment, the special-education practice of systematically observing what happens right before and right after a behavior to identify what it is accomplishing for the person, chases the same target as CPS's joint diagnosis through third-party observation instead of a direct conversation, and carries its own body of applied-behavior-analysis research. WOOP, a technique from psychologist Gabriele Oettingen — Wish, Outcome, Obstacle, Plan — has a person name a wish, imagine the outcome, then name the specific inner obstacle in the way and build an if-then plan around it, which does for an individual planning alone roughly what a CPS conversation does with two people in the room, and it carries randomized-trial support of its own. Motivational interviewing's practice of asking directly what has gotten in the way of a change before offering any suggestion serves the identical objective in a counseling setting.

A tradition that already does this

Behavioral Activation, the broader depression treatment that Pleasant Events Scheduling comes out of, already builds a version of this move into its own manuals: clinicians following Martell, Addis, and Jacobson's activation protocols are trained to treat a client's failure to complete a scheduled activity as data about a specific barrier — energy, logistics, a feared interaction — worth naming directly, not as evidence of insufficient effort, and to problem-solve that barrier before simply re-scheduling the same activity. The instinct this page borrows from CPS was already sitting inside one half of the pairing.

Using Collaborative Problem Solving to enhance Pleasant Events Scheduling

Pleasant Events Scheduling can stall when a person resists the very activity meant to help, and the standard response — read the resistance as more proof of low motivation — usually deepens it rather than resolving it. Apply CPS's actual conversation instead of a fresh reminder: sit down and jointly work out why starting the scheduled activity is hard right now, rather than a parent, partner, or clinician handing down the schedule and expecting compliance. The concrete move is turning 'go for a walk at 4pm' into a short exchange — what specifically makes 4pm hard, what would make it easier — worked out together rather than assumed, so the plan carries the buy-in that comes from being built jointly instead of imposed. That is the same mechanism CPS uses for a behavioral outburst, aimed here at a scheduling gap instead of a meltdown.

Using Pleasant Events Scheduling to enhance Collaborative Problem Solving

CPS conversations take real bandwidth from both people, and a family or a pair running on empty has less of it to spend, which is part of why the proactive version of these conversations often gets skipped exactly when it is needed most. Borrow PES's premise that action can be put on the calendar ahead of motivation, and schedule small, low-stakes pleasant activities for the relationship itself — a specific walk, a specific shared meal — before attempting the harder unsolved-problem conversations. The concrete move is treating baseline connection as an input that has to be scheduled rather than assumed to already be there, so there is some reserve built up before the two of you sit down to work out something harder.

Tuesday, 7pm, homework still not started

Your kid is on the fourth night this week of stalling on homework, and you can feel the script forming in your head — sit down and do it now. Instead you try the CPS move: you sit next to them, not across, and ask what is making homework hard to start tonight specifically, rather than assuming it is the same as every other night. It turns out tonight's assignment references a group project where they feel behind, and that specific piece gets solved together in a few minutes. Separately, you notice the two of you have not done anything just-for-fun together in over a week, so before Thursday you put fifteen minutes of a shared activity they actually like on the calendar — not as a reward for finishing homework, but as its own scheduled input, so Thursday's conversation, if there needs to be one, is not starting from empty.

When this is worth reaching for

A pleasant activity is already on the calendar, has been for weeks, and keeps not happening — not because the week got busy once, but on a pattern, the same activity, the same kind of excuse, three times running. That repetition is the signal that something specific is standing in the way rather than ordinary bad luck, and it is worth five minutes of a real conversation instead of a fourth reschedule. It also matters in a household or pair where a low mood has already produced some conflict about it, so the scheduling itself has started to feel like one more demand rather than support — there, the diagnosis has to come before the calendar entry means anything again.

Where this does not apply

CPS is built around a specific, identifiable unsolved problem behind a specific recurring behavior, most often in a parent-child or clinical context, while Pleasant Events Scheduling addresses a general dip in mood or activity that may have no single findable cause — situational grief, a hard season, ordinary fatigue. When the low mood is not attached to a specific solvable antecedent, CPS's joint-diagnosis structure has nothing concrete to attach to, and plain Pleasant Events Scheduling, just getting enjoyable activity back onto the calendar without a diagnostic conversation about it, does the more relevant part of the work on its own.

What the evidence does and does not support

Treating an apparent misbehavior as a mistaken strategy for an unmet need, and putting an internal pattern into a structured, visible form, both carry clinical and observational backing specific to CPS's own literature with children. Behavioral activation — acting before motivation arrives, on the finding that the action produces the motivation waiting would only delay — has randomized-trial support in depression treatment, and small consistent actions accumulating into a larger result is a broadly evidenced pattern rather than a PES-specific finding. What neither literature has looked at is the narrow overlap this page describes: whether a CPS-style conversation about a stalled scheduled activity actually gets the activity done more often than simply rescheduling it. That specific comparison has not been run.

Practice this with IX Coach

Try this practice

The two practices on their own

Other pairings with these practices

The principles underneath both