Using Collaborative Problem Solving to enhance PDSA Cycle

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 PDSA Cycle rests on

• Feedback against prediction corrects belief plausible mechanism
  Comparing the actual result of a change against the predicted result before adopting it corrects mistaken beliefs faster than adopting or rejecting changes based on intuition alone.
• Small scale testing precedes scaling observational studies
  Running a change through a small planned test cycle before wider adoption reveals real-world effects while limiting the risk of being wrong.

Where they actually meet

CPS's principle of generating the solution jointly with the person who has the problem produces buy-in — both people help design the fix, so both are more likely to actually try it — but nothing in that process itself verifies whether the fix worked once tried. PDSA's core logic, comparing an actual result against a stated prediction, is precisely the missing verification step. At the level of principle, CPS is strong on generating a solution people will attempt and comparatively silent on confirming it works, while PDSA is strong on confirming whether a change works and silent on where the change idea should come from; each supplies what the other treats as already settled. The flip sits in what happens to the solution itself: instead of remaining an assumption both people quietly hold — 'this should work, we agreed on it' — it becomes an object, a specific predicted outcome you can look at side by side with what actually happened.

Using Collaborative Problem Solving to enhance PDSA Cycle

A PDSA cycle needs a plan to test, and where that plan comes from matters — a change imposed from outside tends to get followed half-heartedly during the 'do' step, which muddies whatever the 'study' step finds, since a weakly-executed plan and a genuinely bad plan can look the same in the results. CPS's jointly generated solution, arrived at by both people naming the unsolved problem behind the outburst and working out a fix that accounts for both of their concerns, supplies a plan the person actually executing it had a hand in designing — exactly the condition PDSA's small-scale test assumes but doesn't itself create. Concretely: instead of a parent unilaterally deciding 'we'll try rewards for finishing homework' and running that through a PDSA cycle, the CPS conversation produces the specific plan — hardest subject first, then a five-minute break — that the test cycle then evaluates.

Using PDSA Cycle to enhance Collaborative Problem Solving

Once CPS produces a jointly agreed solution, there's a real risk on both sides: declaring success simply because everyone nodded in the room, or abandoning the plan at the first bad day without checking whether that day was actually representative. PDSA's structure asks you to do neither — plan the specific change, run it for a short defined stretch such as one week, and then explicitly study what happened against what you predicted before deciding whether to keep it or revise it. Concretely: after agreeing on hardest subject first, then a break, name the prediction out loud — outbursts drop from most days to two or fewer this week — and then actually check the tally together the following Sunday, rather than either side silently deciding on their own whether it worked.

The Tuesday homework meltdown, six weeks in

You and your kid have already had the CPS conversation, calmly, on a Saturday afternoon — the unsolved problem turned out to be that starting with the hardest subject while already hungry made everything feel impossible, and the plan you built together was: snack first, hardest subject next, five-minute break after. It's now Tuesday of week two. Instead of assuming the plan is working because it felt good to agree on it, you'd written down beforehand what you expected — outbursts down from four days a week to one or none — and tonight you actually look at what happened: three outbursts this week, not the drop you predicted. That's not the plan failing; it's the study step doing its job, and it means the next conversation is about what to adjust, not about whether either of you tried hard enough.

Where this does not apply

If the outburst is being driven by something neither person's agreement can address directly — an undiagnosed learning difficulty, unaddressed trauma, or unsafe conditions at home — no jointly generated solution and no test-and-check cycle substitutes for addressing that underlying condition; both CPS's conversation and PDSA's test loop assume the two people involved can actually generate and evaluate a workable fix together, which requires a baseline of safety and capacity that the conversation itself doesn't create.

What the evidence does and does not support

CPS's claim that misbehavior usually reflects a mistaken strategy aimed at an unmet need rather than badness itself currently rests on clinical observation; that jointly generating a solution increases follow-through compared to an imposed one has only observational support so far. The broader principle that externalizing an implicit pattern into a structured form makes it visible for examination has trial-level support in other contexts, though not specifically within CPS. On the PDSA side, that comparing an actual result to a stated prediction corrects mistaken beliefs faster than intuition alone is a mechanistic account rather than a controlled finding, and that testing a change at small scale before wider adoption reveals real-world effects has observational support from quality-improvement settings, not from parenting or behavioral contexts specifically. No study has tested running a PDSA cycle on top of a CPS-negotiated solution; this is a reasoned application of two separately supported mechanisms, not a demonstrated result.