What to Do When the Same Solution Keeps Failing the Same Kid

And how SCAMPER sharpens Collaborative Problem Solving in return.

Collaborative Problem Solving, developed by the psychologist Ross Greene, treats a repeated behavioral outburst as evidence of an unsolved problem rather than defiance, and has the adult and the child work together to name that specific problem and then jointly generate a solution both people can actually live with. SCAMPER is a creativity checklist, built from Alex Osborn's original brainstorming work and later organized into an acronym by Bob Eberle, that applies seven prompts — Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse — to something that already exists, to force new angles a person would not have reached by just thinking harder about it. The place they connect is narrow but real: once Collaborative Problem Solving has correctly identified the actual unsolved problem, it still asks the two of you to invent a workable solution, and that invention step is exactly the kind of stuck moment SCAMPER's structured prompts were built to break open, translated into language a child can actually use.

What each one is actually for

Collaborative Problem Solving

The third step of Collaborative Problem Solving is a brainstorm, and it fails most often by being too short. Ross Greene, the psychologist who developed the method, has the adult and the other person generate solutions together once both concerns are on the table — and the common failure is stopping at the first idea, which is nearly always the one the adult walked in already holding. The two steps before it exist to make a real brainstorm possible. First, empathy: you ask open questions to genuinely understand what is hard about one specific recurring situation from the other person's side, not to lecture, just to gather real information — "what's up with getting your shoes on before we leave?" Second, you state your own concern plainly, the actual reason the expectation matters, with no threat attached. Only then do you start generating options, and the constraint that makes that productive is a demanding one: every candidate has to answer both concerns rather than just yours, which rules out most of the obvious moves and pushes the search somewhere less familiar. A solution the other person had a real hand in choosing sticks in a way an imposed one does not.

SCAMPER

SCAMPER takes something that already exists — a product, a routine, a plan that is not working well enough — and runs it through seven fixed lenses, one at a time, asking a different kind of question each time. Substitute: what could you swap out for a piece of this? Combine: what could you merge it with? Adapt: what else does this remind you of, and what could you borrow from that? Modify or magnify: what could you make bigger, smaller, or different in scale? Put to another use: could this work somewhere else entirely? Eliminate: what could you remove? Reverse: what happens if you do the opposite, or run it backward? The method does not ask for one big flash of inspiration; it asks for seven small, structured attempts, and the value is in having a fixed set of angles to try when the obvious ideas have already been tried and have not worked.

What you get out of pairing them

Collaborative Problem Solving's payoff is that it treats the child as a source of real information rather than a problem to be managed, which tends to lower the temperature of the interaction on its own and, over time, teaches the exact skill that was missing rather than just suppressing the behavior it produced. But knowing the real problem is not the same as having a workable answer to it, and a lot of well-run empathy-and-concern conversations stall at the third step because both people run out of ideas and default back to whatever was already not working. SCAMPER's payoff is specifically for that stall: it gives two people who have correctly diagnosed a problem but cannot think of a new answer a concrete way to generate one, by forcing them through several distinct angles instead of circling the same one or two ideas that already failed.

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 SCAMPER rests on

  • Perspective taking expands frame randomised trials
    Deliberately adopting a vantage point other than one's own default view widens the range of interpretations or options available for a situation.
  • Constraint forces novel combination practitioner report
    Forcing a specific type of change onto a familiar idea forces combinations that unconstrained thinking would not reach.
  • Structured prompts widen idea generation practitioner report
    Applying a fixed set of transformation prompts to an existing idea generates a wider range of alternatives than unstructured brainstorming.

Where they actually meet

Both methods refuse to trust an idea that stays only in someone's head. Collaborative Problem Solving will not accept an unspoken assumption about why a child is struggling; it insists the actual unsolved problem gets said out loud, in specific terms, before anyone tries to fix it. SCAMPER will not accept a vague sense that an idea "could be better"; it insists the existing idea be laid out plainly enough to run seven specific questions against it. Once each method has done that externalizing work in its own domain, both add a second move that turns the externalized material into new options: Collaborative Problem Solving invites two people to build a shared answer together instead of one person deciding alone, and SCAMPER runs a fixed set of transformation prompts against what has been laid out instead of hoping a better idea simply appears. Neither method treats naming the problem as the finish line; both treat it as the raw material for a structured next step.

The principle underneath both

An idea or a problem that stays vague and implicit resists being worked on; the same idea or problem, once stated plainly enough to look at from outside your own head, can be pushed through a repeatable set of prompts that reliably produce options a person would not reach by simply trying to think harder from inside their default view.

What that makes the real goal

If externalizing a problem and then running it through structured, repeatable prompts is what actually generates new options, the goal both practices serve is producing a genuinely wider menu of possible solutions than either person would generate on their own, especially in a situation where the obvious answers have already been tried and have already failed.

Other practices that serve the same goal

Design teams reach for a close cousin of this same move constantly. The "How Might We" reframing technique, popularized through design-thinking practice, takes a stated problem and deliberately rephrases it as an open, generative question before brainstorming begins, on the theory that the exact wording of a problem statement shapes which solutions become visible. Edward de Bono's Six Thinking Hats asks a group to deliberately rotate through six distinct viewpoints, one at a time, on the same problem, which forces the same kind of angle-switching SCAMPER forces through its seven prompts, just organized around perspectives instead of transformation types. And in motivational interviewing, used widely in coaching and counseling, the practitioner deliberately elicits the other person's own ideas for change rather than supplying solutions, which shares Collaborative Problem Solving's core bet that a person is more likely to follow through on an answer they generated than one handed to them.

Using SCAMPER's Prompts to Get Unstuck at the Brainstorming Step

Collaborative Problem Solving's third step asks the adult and child to brainstorm a mutually workable solution, but in practice this step often produces the same two or three tired ideas — try harder, set a timer, no screens until it's done — because neither person has a structured way to reach for something different. Once the real unsolved problem has been named honestly in step one, translate a handful of SCAMPER's prompts into plain, kid-sized language and run them together, out loud, as a game rather than a checklist. If mornings fall apart over getting shoes on, ask together: what could we swap out — a different kind of shoe, a different spot to put them? What could we combine it with — shoes going on during a favorite two-minute song? What could we do backward — shoes on before breakfast instead of after? You do not need all seven prompts every time; picking even two or three that feel like they fit the specific problem is usually enough to produce an option neither of you would have reached by just asking "what should we do" and waiting.

Using Collaborative Problem Solving's Empathy Step Before SCAMPER on a Recurring Conflict

SCAMPER is normally run on a product or a plan, not on a relationship, and applying its seven prompts directly to a recurring conflict without first understanding why the current approach is failing tends to produce clever-sounding ideas nobody actually wants to try. Borrow Collaborative Problem Solving's first move before reaching for SCAMPER's checklist: spend real time gathering what is actually hard about the current situation from the other person's side, plainly, without an agenda, before running any of the seven prompts. A team stuck on why a recurring project handoff keeps failing will get more out of SCAMPER's substitute-and-eliminate prompts once someone has actually asked the person doing the handoff what specifically goes wrong for them, rather than running the checklist cold against an assumption about the problem that might not even be accurate.

Tuesday, 7:40am, the Shoe Fight Nobody Wants to Have Again

You and your seven-year-old have had the same fight about putting shoes on before school four mornings this week, and you have already tried the obvious things — a countdown, a reward chart, a stern voice — and none of it has held for more than a day. Tonight, calm, you sit down together and actually ask what's hard about it, and it turns out the real problem is not the shoes at all: he hates that his socks bunch up inside them and it drives him a little bit crazy every single time, which is not something you had ever asked about before. Naming that gets you further than any of the previous mornings did, but you still do not have an answer, so you try a couple of SCAMPER prompts together as a game. Substitute: different socks, seamless ones, tried on tonight to check. Reverse: socks and shoes on before he gets dressed instead of after, so there is no rushed, half-dressed moment where the bunching feels worse. He picks the reverse idea himself, because it is his idea, not yours, and the next morning, for the first time in a week, shoes happen without a fight — not because either of you tried harder, but because the actual problem got named and then run through a few genuinely different angles instead of the same three tired ones.

When this is worth reaching for

The real problem has already been named honestly, out loud, and the adult's concern is on the table — that part worked. What's stuck is the third step: the same two or three ideas keep circling back, all previously tried, all previously failed, and nobody in the room has a fourth. Skip this until brainstorming has actually stalled; plenty of named problems have an obvious fix the moment they're understood, and running a seven-prompt creativity checklist against an easy fix adds a step nobody needed.

Where this does not apply

If a child, or either party in any version of this, is currently dysregulated, mid-meltdown, or otherwise not in a state where calm conversation is possible, no brainstorming technique belongs in that moment — Greene's own model is explicit that Plan B only happens once both people are calm enough to think together, and introducing a structured creativity checklist into a moment of active distress misapplies both methods at once. SCAMPER's seven categories are also fairly abstract for a young child; with kids much under seven or eight, running the full acronym by name adds jargon exactly where the exercise most needs to feel like a game, and a much simpler "what else could we try" brainstorm, without the formal structure, is the more honest fit. And for genuinely non-negotiable situations — safety rules, situations with no room for compromise — Collaborative Problem Solving's own model says these are not collaborative at all, and no amount of creative reframing changes that; applying SCAMPER there misreads what the situation actually calls for.

What the evidence does and does not support

Collaborative Problem Solving has a growing evidence base, including observational studies and some controlled research in school and juvenile-justice settings showing reductions in suspensions, restraints, and disciplinary incidents where it has been implemented, though the research base remains smaller than the largest randomized trials behind more established parent-training programs. SCAMPER itself comes out of a practitioner tradition in creativity and innovation training rather than a research tradition, and while its component ideas, like perspective-taking and constraint-driven thinking, have their own separate research support, the specific seven-prompt technique as packaged has had little direct empirical testing of its own incremental value over unstructured brainstorming. Nobody has studied this specific combination, translating SCAMPER's prompts into Collaborative Problem Solving's brainstorming step; what is offered here is a reasonable, practically motivated extension of two separately-grounded ideas, not a tested protocol.

Practice this with IX Coach

Try this practice

The two practices on their own

Other pairings with these practices

The principles underneath both