Using Collaborative Problem Solving to enhance Stretch Goals

What each one is actually for

Collaborative Problem Solving

Collaborative Problem Solving starts from a specific reframe that Ross Greene built his whole model around: a person who blows up, shuts down, or refuses when asked to do something ordinary, put away a toy, leave the house on time, take feedback on a draft, is not choosing to be difficult, they're hitting a specific point where what's being asked exceeds a skill they currently have, whether that's flexibility, frustration tolerance, or the ability to switch attention on command. The method, often taught under the name Plan B, has the adult sit down with the person outside the heat of the moment, not during the outburst itself, and run a short structured conversation: first genuinely gathering the other person's actual concern about the situation, in their own words, rather than assuming it; then stating the adult's own concern plainly; and finally inviting both people to generate possible solutions together and pick one to actually try. The solution that comes out the other end wasn't handed down by the adult and accepted under pressure; it was built by both people, which is a large part of why it tends to actually get followed once agreed on.

Stretch Goals

Stretch goals work from the opposite direction: instead of waiting for a demand to exceed someone's current capability and then addressing the fallout, they set the demand beyond current capability on purpose, from the start. A stretch goal isn't simply an ambitious version of an ordinary goal, ten percent more than last quarter; it's specifically set at a level where the strategies a person or team already knows how to execute clearly won't get them there, which is the point, a goal reachable with existing methods only produces more effort applied to the same approach, while a goal that clearly can't be hit the usual way forces a genuine search for a different one. The tradeoff, and it's a real one, is that this deliberately widens the range of what actually happens: stretch goals produce more outright breakthroughs than moderate goals do, but also more outright failures, because setting a target beyond current capability doesn't guarantee the new strategy gets found in time.

What you get out of pairing them

Collaborative Problem Solving is precise about repairing a capability gap once it's already produced a breakdown, but it doesn't have much to say about deliberately setting a demand beyond current skill on purpose, the way a coach or a manager sometimes needs to in order to produce real growth rather than comfortable stagnation. Stretch goals are precise about deliberately creating that gap to force growth, but the research behind them is honest about the cost: without anything closing the gap between the target and current capability, a meaningful share of stretch goals produce exactly the collapse, shutdown, or disengagement that Collaborative Problem Solving was built to address, just in an adult performance setting instead of a child's bedroom. Borrowed carefully, Collaborative Problem Solving's structured conversation gives a person setting a stretch goal a way to actually diagnose, collaboratively, where the specific skill gap sits before or after setting the target, rather than setting it blind and hoping; and stretch-goal thinking gives Collaborative Problem Solving something it doesn't usually reach for on its own, a case for occasionally setting a demand deliberately ahead of current comfort rather than only meeting a person exactly where their current skill already is.

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 Stretch Goals rests on

• Difficulty drives strategy search observational studies
  Setting a goal beyond current comfortable capability forces a search for novel strategies rather than incremental effort on existing ones.
• Goal difficulty raises effort and performance randomised trials
  Within the limits of ability and genuine commitment harder specific goals produce higher effort and performance than easy or vague goals.
• Stretch goals increase outcome variance observational studies
  Setting goals beyond current capability raises the spread of outcomes producing both more breakthroughs and more outright failures than moderate goals.

Where they actually meet

Both practices are working at the same boundary, the line between what's currently being asked of someone and what skill they currently have to meet it, they just arrive at that line from opposite directions and treat it differently. Collaborative Problem Solving finds the gap after it's already produced an outburst and works backward, collaboratively, to understand exactly where the skill fell short and what would close it. Stretch goals create the gap on purpose, before any breakdown has happened, betting that the pressure of a demand beyond current capability will itself produce a new strategy rather than a collapse. Put the two side by side and you can see what each is missing precisely because of which direction it approaches from: the collaborative diagnosis that would tell a stretch-goal setter where the gap actually sits and what support would close it well, and the willingness to occasionally set a demand ahead of comfort rather than always meeting a person exactly where they already are.

The principle underneath both

What both practices are actually responding to is the same underlying fact: when a demand exceeds someone's current capability, that gap itself isn't the problem, plenty of real growth happens exactly there, what determines whether the gap produces a breakthrough or a breakdown is whether anything closes it, through collaborative diagnosis, real support, or new strategy, rather than the gap just sitting there as pure, unaddressed pressure.

What that makes the real goal

Seen that way, what both are ultimately organized around is the same practical target: turn a moment where a demand outruns current skill into a genuine occasion for growth, rather than either avoiding the gap altogether by never asking for more than someone already knows how to give, or leaving the gap to sit as unaddressed pressure until it produces a collapse. Framed at that level, this isn't a child-behavior question or a workplace-performance question specifically, it's a general test for any situation where you're asking more of yourself or someone else than current capability comfortably covers: is this gap being handled, or just imposed?

Other practices that serve the same goal

Lev Vygotsky's developmental concept of a zone of proximal development, the specific range just beyond what a learner can do independently but within reach with the right support, and the scaffolding practice built around it, a more capable other providing exactly the support needed and gradually withdrawing it as skill grows, chases the identical target with heavy support in early education research: set the demand just past current capability, and provide the specific structure that closes the gap rather than leaving it to raw effort. Carol Dweck's research on goal-setting and mindset, with substantial experimental support, finds that framing a difficult goal as an opportunity to develop a new strategy, rather than as a test of fixed ability, changes how people respond to exactly this kind of gap, pursuing new approaches rather than giving up when the obvious methods fail. In workplace settings, the OKR framework used by many technology companies explicitly separates aspirational stretch goals from must-hit operational goals precisely because conflating the two, treating an intentionally ambitious target as something failure to reach should be punished for, is a well-documented way stretch goals turn into exactly the kind of collapse this pairing is meant to prevent.

A tradition that already does this

Vygotsky's zone of proximal development, paired with the scaffolding practice built around it, already fuses both halves of this exact move inside developmental psychology, decades before either practice named here existed. A more capable other, a parent, teacher, or tutor, deliberately sets a task just beyond what a child can do alone, which is a stretch by definition, but pairs that stretch with active, collaborative diagnosis of exactly where the child's independent skill runs out and exactly what support closes the remaining gap, withdrawing that support gradually as the skill develops. Deliberately reaching past current capability and collaboratively diagnosing the exact shape of the gap, together, from a tradition neither of these two practices drew on directly.

Using Collaborative Problem Solving to enhance a Stretch Goal

Before setting a stretch goal for someone, whether it's a direct report, a teammate, or your own kid working toward something ambitious, run a short version of the collaborative conversation first: genuinely ask what they see as hard about the stretch, in their own words, rather than assuming you already know; state plainly what you're actually trying to accomplish by setting the goal that high; and then, together, generate what specific support or strategy might close the gap between where they are now and where the goal sits, rather than setting the number and leaving them to figure out the rest alone. This doesn't make the goal less of a stretch, and it shouldn't; the point isn't to soften the target, it's to make sure the gap between current capability and the target has an actual plan attached to it instead of being pure unaddressed pressure. A stretch goal set this way is far more likely to produce the strategy search it's designed for and far less likely to produce the kind of shutdown or quiet disengagement that shows up when someone is simply told to reach further with no idea how.

Using a Stretch Goal to enhance Collaborative Problem Solving

Collaborative Problem Solving is built to repair a gap once it's already produced an outburst, which means it's naturally oriented toward meeting a person exactly where their current skill sits, closing today's specific gap rather than deliberately building toward more than today's skill covers. Once a specific unsolved problem has actually been solved collaboratively, a stretch-goal mindset gives the next step something Collaborative Problem Solving doesn't usually supply on its own: instead of stopping at we found a solution that works for today's version of this demand, ask together whether the solution that worked could be deliberately extended a bit further next time, not by raising the pressure suddenly, but by naming, together, one small way the demand could stretch past today's comfortable version once the current solution is genuinely solid. This matters mainly once a pattern of successful collaborative solutions has built real trust between the two people; used too early, before that trust exists, adding stretch on top of a still-fragile solution risks reintroducing the very pressure the collaborative process was built to relieve.

A Tuesday afternoon check-in about a goal that's clearly too big right now

You manage someone on your team who was given an ambitious quarterly target, deliberately set well past what last quarter's approach could produce, and for the past two weeks they've gone quiet in status meetings and stopped proposing ideas the way they used to. Instead of assuming they're not trying, you set up a short one-on-one and open, genuinely, by asking what feels hardest about the target right now, and you actually wait for the answer instead of filling the silence. They say, after a pause, that they don't see how the number is even possible with the tools they currently have, and they've stopped bringing it up because every idea they've had so far felt too small to matter. You name your own concern plainly, that the target matters to the wider team's plan and you don't want to quietly lower it without a real conversation first. Then, together, you spend the rest of the meeting generating actual options, not solutions handed down, options built jointly, and land on trying one specific new approach for two weeks before revisiting the number. The target hasn't moved. What's changed is that the gap between where they are and where the goal sits now has an actual plan in it, built by both of you, instead of being a number they were quietly avoiding.

When this is worth reaching for

A target is genuinely running ahead of what someone can currently do, and what shows up isn't strategy search — it's shutdown, avoidance, disengagement. That's the moment a diagnostic conversation can redirect the stretch back toward growth instead of collapse. A goal that's comfortably within reach doesn't call for either practice.

Where this does not apply

Be honest that these two practices come from genuinely different worlds and don't naturally belong together for most of their common uses; Collaborative Problem Solving was built for recurring behavioral outbursts, often in children, and most of its evidence sits there, while stretch-goal research mostly concerns adult performance in work and athletic settings, and applying either one wholesale in the other's context, running a full Plan B conversation over a missed sales target, or setting a workplace-style stretch goal for a five-year-old's chores, tends to feel forced rather than useful. And if a gap is being caused by something outside either practice's reach, insufficient resources, an unclear or contradictory goal, active burnout, no amount of collaborative diagnosis or ambitious reframing will close it; that calls for changing the actual conditions, not applying either technique harder.

What the evidence does and does not support

Collaborative Problem Solving carries a real, if still developing, evidence base, including randomized and quasi-experimental studies in school and clinical settings showing reductions in behavioral incidents compared to more traditional consequence-based approaches, concentrated mainly in child and adolescent populations. The core research on goal difficulty and performance, associated with Edwin Locke and Gary Latham's work, has decades of experimental support for the general finding that harder, specific goals raise effort and performance within real limits; the specifically branded stretch goal framing used in business and athletics rests more on organizational case study and observational evidence than on controlled trials of the stretch-goal format itself. Nothing has tested the combination described here, using a collaborative diagnostic conversation to set or repair a stretch goal; that pairing draws a bridge between a child-behavior model and an adult-performance framework that, as far as published research goes, have simply never been studied in the same room.