What Do Collaborative Problem Solving and the Rockefeller Habits Have in Common?

What each one is actually for

Collaborative Problem Solving

Plan B, the actual mechanic behind Collaborative Problem Solving, has three parts done in order and out loud. First, the empathy step: the adult asks a genuine, open question about what's making the specific moment hard right now, not why the child is difficult in general, and actually listens for the answer instead of already knowing it. Second, the adult states their own concern in one plain sentence, the thing that makes the current situation not okay to leave as it is. Third, the two of them brainstorm together until they land on a solution both people can actually live with, not one the adult hands down and the child grudgingly accepts. You can picture doing this at the kitchen table on a Tuesday when homework has stalled for the third night running.

Rockefeller Habits

The Rockefeller Habits give a leadership team three concrete rituals instead of one big annual planning event. A daily huddle, ten to fifteen minutes, where each person says what they did yesterday, what they're doing today, and names anything stuck, out loud, in front of the group, not buried in a shared document nobody opens. A quarterly cycle that narrows the company's priorities down to three to five 'Rocks,' the handful of things that actually have to happen in the next ninety days, small enough in number that everyone can hold them in their head. And a single page, the company's purpose, core values, targets, and current Rocks, kept visible so a new hire or a distracted long-timer can look at one sheet and know what the quarter is actually for.

What you get out of pairing them

CPS's payoff is specific: a kid whose real obstacle gets named and solved with them stops fighting the same battle every night, because the actual thing in the way, not enough time between the bus and dinner, a worksheet format nobody explained clearly, got fixed instead of punished. That is different from compliance, which fades the moment the adult isn't watching; a solution the child helped build tends to survive because they understand why it works. The Rockefeller Habits' payoff is the organizational version of the same relief: a team that names its blocker out loud in a ten-minute huddle catches it while it is still small, instead of discovering in week eleven of the quarter that the same handoff problem has been quietly costing everyone time since week two. Neither practice is selling comfort. Both are selling the difference between a problem that gets fixed once it's named and one that just keeps recurring because nobody ever said what it actually was.

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 Rockefeller Habits 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.
• Rhythmic cadence sustains alignment observational studies
  A regular cadence of daily and quarterly check-ins sustains organizational alignment better than an annual planning event.
• Short feedback loops surface obstacles early practitioner report
  Brief daily huddles surface obstacles while they are still small enough to fix quickly.

Where they actually meet

Both practices refuse to let a recurring problem stay implicit. Collaborative Problem Solving externalizes a behavioral pattern by putting it into words two people examine together, on the premise that what looks like misbehavior is usually a mistaken strategy aimed at a real need rather than badness needing correction. The Rockefeller Habits externalize organizational drift the same way, putting priorities and blockers onto a visible one-page plan and into a recurring huddle, on the premise that alignment left implicit erodes by default. The seam is the shift from something running silently, an unnamed need driving an outburst, an unnamed blocker slowing a team, into something named and looked at jointly. What was simply enacted becomes something a group can actually examine and choose about, the same move at two different scales.

The principle underneath both

A problem that never gets put into words keeps producing the same reaction on a loop, because there is nothing specific to actually work on, just a feeling that something is wrong again. Say the specific thing out loud, in front of the person or people it affects, and it turns from background friction into a target two people can actually aim at together.

What that makes the real goal

If naming the specific obstacle out loud is what does the work, the goal both practices are chasing is the same regardless of scale: turn a vague, recurring friction into something concrete enough that two or more people can check, later, whether the fix actually held. That target doesn't care whether the friction is a child's meltdown or a missed handoff between two departments; the method for reaching it is the same in both cases, name the specific thing, in front of the people it affects, on a schedule that keeps it from sliding back into silence.

Other practices that serve the same goal

The 5 Whys, a root-cause technique that came out of the Toyota Production System, chases the identical target from manufacturing: instead of stopping at the first plausible explanation for a defect, a team asks 'why' repeatedly until it reaches the actual cause rather than a symptom, and Toyota's own quality-control history is the evidence base for taking that extra step seriously. Agile software teams run something structurally close in a retrospective, a recurring meeting at the end of each work cycle built specifically to name what went wrong concretely instead of assuming the team will just do better next time; case studies from software engineering associate regular retrospectives with fewer repeat defects, though that research is observational rather than randomized. And Marshall Rosenberg's Nonviolent Communication gives an individual conversation a four-part structure, the observation, the feeling, the unmet need, and the request, built explicitly to get an unmet need into words instead of leaving it to come out sideways as blame; it carries observational support for reducing conflict escalation in couples and workplace settings. All three, like Collaborative Problem Solving and the Rockefeller Habits, are betting that the problem was never mainly a discipline or effort problem. It was an unnamed one.

Using Collaborative Problem Solving to Sharpen a Rockefeller Huddle

A daily huddle can slide into a status recitation, everyone reporting what they did, without ever surfacing why the same blocker keeps recurring. Borrow CPS's actual question directly into the huddle: when an obstacle shows up three huddles running, stop the status format and run a short joint diagnosis on it the way Plan B runs its empathy step, asking what's actually making this hard right now rather than logging it again as a blocker to route around. If design keeps missing a handoff deadline, the question isn't 'why are you behind,' it's the CPS-style 'what's making this specific step hard,' asked genuinely, with the same patience Plan B asks an adult to bring to a kid. That turns the huddle from a reporting ritual into the place where a genuinely unsolved problem gets named instead of quietly repeating.

Giving a CPS Solution a Place to Actually Recur

CPS is good at diagnosing a specific unsolved problem, but nothing in the method itself guarantees the agreed solution gets revisited. A joint diagnosis reached on a hard Tuesday can quietly lapse once the crisis passes and nobody's watching for it to come back. Borrow the Rockefeller cadence directly: give the CPS solution a line on a simple written plan and a standing thirty-second check at a regular, brief touchpoint, even a version scaled down to a single family, a whiteboard line and a nightly two-minute check-in, the same way a Rockefeller huddle checks a Rock every day rather than trusting everyone remembers the quarter's priorities. That matters because CPS's own advantage, a solution someone helped build sticks better than one handed down, still needs a recurring moment to hold it in view, or the advantage fades along with everyone's memory of the original conversation.

The Third Tuesday the Same Handoff Delay Shows Up

It's the third Tuesday huddle in a row where someone reports the same handoff delay between design and engineering, and you can feel the room's patience thinning into something that sounds like blame. Instead of logging it again, you pause the status-report format and run a short CPS-style diagnosis on the spot: what is the actual unsolved problem in this handoff, is it unclear specs, is it competing priorities nobody named out loud? The answer, design doesn't know engineering's sprint capacity before committing dates, gets written onto the one-page plan as a standing line, not just a note, so next Tuesday's huddle checks whether the fix is holding instead of discovering the same blocker fresh, the way a Plan B solution gets checked at dinner the next night instead of assumed to have stuck.

When this is worth reaching for

The same blocker has come up in three huddles running, and the room is starting to read it as somebody not trying hard enough rather than as an actual unsolved problem. That's the moment for the diagnostic step, not week one, when a blocker might resolve on its own, and not after the frustration has curdled into blame that makes an honest joint diagnosis harder to run. On the family side, the matching moment is a solution that got agreed on once, worked for a week, and then quietly stopped holding, that's when it's worth borrowing a written line and a short recurring check rather than re-running the whole diagnostic conversation from scratch.

Where this does not apply

Collaborative Problem Solving is built around a specific dyad working through a specific behavioral pattern together, and stretching its diagnostic conversation across an entire team's huddle can flatten it into something closer to generic brainstorming, losing the individualized attention to one person's underlying need that gives CPS its traction. A ten-person huddle is not a kitchen-table conversation, and treating it like one can just produce a longer meeting. In the other direction, the Rockefeller cadence is built for organizational execution and priority-tracking, and a family leaning on a formal one-page-plan-and-huddle structure for ordinary parenting friction, rather than genuine multi-person coordination, may find the format keeps the friction on a schedule without actually diagnosing what's underneath it. Logging a recurring meltdown on a whiteboard isn't the same as sitting down and running the actual empathy step CPS is built around.

What the evidence does and does not support

The mechanism both practices lean on, that putting an internal or organizational pattern into explicit, external words makes it something people can actually work on, has randomized-trial support as a general finding, though that evidence comes from research outside both the CPS and Rockefeller Habits literatures specifically, so read it as a mechanism both happen to use rather than a finding about either by name. CPS's own claim that difficult behavior usually reflects an unsolved problem carries clinical support from Ross Greene's own program; the buy-in advantage of a jointly built solution is observational. The Rockefeller Habits' cadence and daily-huddle claims are largely anecdotal and observational, drawn from business consulting practice rather than controlled study of the operating system itself. Nobody has measured running a CPS-style diagnostic inside a business huddle, or holding a family solution accountable with a Rockefeller-style written check-in. This page reasons from what each practice already claims about itself, not from evidence about the pairing.