Using Collaborative Problem Solving to enhance Extreme Ownership

What each one is actually for

Collaborative Problem Solving

In Collaborative Problem Solving, the adult walks in assuming their own plan may be the broken part. Ross Greene, the psychologist who developed the method, holds that people do well if they can — so when a behavior keeps repeating despite consequences, the honest first suspicion is that the expectation itself was never made workable: unclear, badly timed, or resourced for a capability the person does not yet reliably have. The conversation happens in a calm moment, not after the next failure, and it goes in a fixed order. You name the specific recurring problem in neutral, concrete terms — not "you keep missing deadlines" but "the Friday report specifically, on the weeks the upstream data lands late." You ask what is actually happening at that spot, and you listen to the answer without defending yourself against it. You state your own concern plainly. Then the two of you build a solution together, which means you are also on the hook for whichever parts of it are yours to fix. It is the structural opposite of a written warning: the person in charge puts their own contribution into the room first, and the plan that comes out has both names on it.

Extreme Ownership

Extreme Ownership is a leadership discipline, not a personality trait: a leader trains themselves to respond to any team failure — a missed deadline, a botched handoff, a subordinate's mistake — by asking, out loud and first, what they themselves failed to make clear, teach, plan for, or check on, before asking what the team member could have done differently. It's practiced most visibly in the after-action debrief, a structured review held right after a task, where the person in charge states their own contribution to what went wrong before anyone else is asked to speak. You can picture doing it: the project shipped two days late, and instead of opening the retro with 'what happened on your end,' you open with 'I didn't build in a buffer for the vendor being slow, and I should have, given they were late last time too.'

What you get out of pairing them

Each practice, used alone, tends to stall in a specific, predictable way. Extreme Ownership without a structured follow-up conversation produces a leader who says 'that's on me' sincerely and then does nothing differently, because naming that you own a failure isn't the same as knowing what specifically to change. Collaborative Problem Solving without a leader who has already dropped the reflex to blame produces a conversation that looks collaborative on the surface — questions asked, notes taken — while the more senior person is still quietly scanning for whose fault it was, which the other person can usually feel. Put together, Extreme Ownership does the harder emotional work first, genuinely removing blame from the room before the conversation starts, and Collaborative Problem Solving gives that removed blame somewhere useful to go: a structured, specific diagnosis of the actual gap, rather than a leader absorbing responsibility for a problem that then never gets solved.

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 Extreme Ownership rests on

• Internal attribution increases agency observational studies
  Attributing outcomes including others' failures to one's own controllable actions increases perceived agency and drives problem-solving instead of blame-seeking.
• Leader modeling shapes team norms practitioner report
  A leader who visibly takes ownership of team failures models a norm that subordinates then adopt and this shifts team-wide behavior over time.
• Removing blame target redirects energy to solutions practitioner report
  When blame-shifting is not available as an option the energy that would go into assigning fault gets redirected toward identifying and fixing the actual problem.

Where they actually meet

Extreme Ownership's core instruction — when something fails, look first at what you, the person with more power in the relationship, didn't provide — is positive-intent reasoning pointed up the hierarchy instead of down it. Collaborative Problem Solving assumes the child's outburst is a mistaken strategy for an unmet need, not proof of a bad character; Extreme Ownership assumes the subordinate's failure is evidence of unclear direction or missing training from the leader, not proof of incompetence. Both refuse the easy read — this person is the problem — and both replace it with a harder, more useful question: what did this person not have that they needed, and whose job was it to notice that gap existed. The reframe runs in opposite directions across a power difference, but it's the identical move.

The principle underneath both

A visible failure is data about a missing condition — missing skill, missing clarity, missing capacity, missing support — rather than evidence about the character of the person who produced it, and treating it as a character judgment actively destroys the information needed to fix the actual gap. The moment blame enters the room, whichever direction it points, the person on the receiving end shifts from disclosing what really happened to defending themselves, and the exact detail that would explain the failure — the thing that was actually missing — stops being sayable out loud. Both practices exist specifically to keep that detail sayable.

What that makes the real goal

Extreme Ownership's opening admission and Collaborative Problem Solving's joint diagnosis are aimed at the same target: a conversation where naming your own part in a failure, or the other person's actual obstacle, costs nothing socially, so the real missing condition — the training that never happened, the deadline nobody flagged as unrealistic — gets said out loud instead of defended against. That target isn't specific to parenting or to military leadership; it belongs to any relationship with a power difference where the usual response to a repeated failure, a warning or a write-up, keeps failing to change anything.

Other practices that serve the same goal

Other practices are built around the same objective and carry their own evidence. The blameless postmortem, a practice formalized in software engineering teams and studied within the broader research on high-reliability organizations, has a team review an incident on the explicit rule that no individual is named as the cause, only the conditions that allowed it — with observational evidence from safety-critical industries that this materially increases how much genuine information surfaces in the review. Amy Edmondson's research on psychological safety, the belief that one won't be punished for admitting a mistake or asking a question, has substantial observational and some quasi-experimental support linking it to team learning behavior and error reporting specifically. The 'Five Whys' root-cause method, which keeps asking why a failure happened past the first, person-shaped answer until it reaches a system-level cause, targets the same shift from blame to diagnosis through repeated questioning rather than through a leader's opening admission.

A tradition that already does this

The Toyota Production System's andon cord practice is a genuine precedent for this move, predating both frameworks by decades. Any line worker who spots a defect can stop the entire production line, and the explicit organizational rule is that the worker is never blamed for the stoppage — the question the system asks is what about the process allowed the defect, not who made it. It's the same underlying commitment as both practices here: a failure is treated as information about the system and the conditions surrounding a person, not a verdict on the person, and an entire manufacturing philosophy was built to protect that principle at scale.

Using Collaborative Problem Solving to enhance Extreme Ownership

Extreme Ownership tells a leader to say 'that's on me,' but says comparatively little about what to do in the next five minutes, and a leader who stops at the admission has done the emotionally hard part without doing the useful part. The concrete move: after taking ownership out loud in front of the team, sit down separately with the specific person whose task went wrong and run an actual Collaborative Problem Solving conversation rather than issuing a new directive. Ask the real diagnostic question — not 'what will you do differently' but 'walk me through what actually happened, step by step, from your side' — and stay in that question until a specific, concrete obstacle surfaces: the spec changed twice without anyone flagging it, the deadline conflicted with another commitment nobody knew about, the tool everyone assumes is intuitive genuinely wasn't for this person. Then build the fix together rather than handing one down. A leader who owns the failure and then unilaterally decides the fix has only moved the blame conversation one level up; a leader who owns it and then runs a real joint diagnosis has actually found what was missing.

Using Extreme Ownership to enhance Collaborative Problem Solving

Collaborative Problem Solving asks the more powerful person in the conversation to treat the other person's failure as a mistaken strategy rather than badness, but it's entirely possible to run the steps of the method — sit down, ask the question, generate a solution — while still privately believing the other person simply should have tried harder, and that belief leaks through tone, timing, and which questions get asked first. Extreme Ownership's specific discipline closes this gap: before asking what got in the other person's way, the person with more power states their own contribution first, out loud, as the opening line of the conversation rather than an afterthought. The concrete move: open every Collaborative Problem Solving conversation with your own admission before asking theirs — 'I didn't check in on Tuesday when I noticed you seemed behind, and I should have' or 'I gave you that assignment without checking whether you'd actually been shown how the new system works.' Naming your own gap first isn't a courtesy; it's what makes the positive-intent stance real rather than performed, because it proves before any words are exchanged that this conversation isn't a prelude to blame.

Monday morning, the client deck that went out with last quarter's numbers still in it

The deck went to the client Friday afternoon with a slide nobody caught still showing Q2 figures instead of Q3. You're the one who reviewed it last before it went out, and by Monday standup the easy move is obvious: ask the analyst who built the deck what happened. Instead, you open the meeting with the analyst alone, before anyone else weighs in, and say the true thing first: 'I signed off on that deck Friday at 4:45 without actually opening the numbers tab, because I was rushing to leave, and that's on me before it's on anything you did.' Then, and only then, you ask the real question — not 'how did you miss it' but 'walk me through building that slide, from when you started to when you sent it to me.' It turns out the template was copied from last quarter's file and the numbers tab has the exact same tab name both quarters, so nothing visually signals which quarter you're looking at unless you check the header cell specifically. That's the actual missing condition — not carelessness, a template with no visual difference between quarters — and the fix you build together, a colored header cell that changes by quarter, has nothing to do with anyone trying harder next time.

When this is worth reaching for

The failure has recurred more than once inside a relationship with a real power difference — a repeated missed deadline, a repeated safety near-miss, a repeated communication breakdown — and the usual response, a warning or a consequence, hasn't changed the pattern. It matters most in the specific moment right after a failure, before the usual blame conversation has already happened and hardened positions on both sides. It's least necessary for a true one-off mistake that hasn't repeated and doesn't suggest a systemic gap; running a full ownership-then-diagnosis conversation over a single, clearly anomalous error is more structure than the situation needs.

Where this does not apply

These don't intersect well when the failure in question involves a genuine skill gap that no amount of blame-free conversation will close on its own — someone who has never been trained on a tool needs training, not a diagnostic conversation about why the untrained attempt went wrong. They also don't intersect where the failure involves real misconduct rather than a mistaken strategy — theft, harassment, deliberate deception — where Collaborative Problem Solving's positive-intent frame is the wrong lens entirely and Extreme Ownership's leader-side admission risks reading as the leader absorbing blame for someone else's deliberate wrongdoing. And the sequence depends on the leader's admission being genuinely true and specific; a leader who takes ownership of something they had no real hand in, purely as a technique to open the conversation, produces something that reads as hollow and undermines trust rather than building it.

What the evidence does and does not support

The two practices sit on very different evidentiary ground. Collaborative Problem Solving's positive-intent reframe is clinically well established in child and adolescent behavioral treatment, and the broader claim that externalizing an internal pattern into structured, examinable form works has randomized-trial support in adjacent behavior-change research, though not specific to Greene's exact protocol; the claim that jointly generated solutions produce more durable follow-through than imposed ones rests on observational case-outcome data. Extreme Ownership is a popular leadership framework distilled from military experience and later business consulting, without controlled trials behind it; the claim that owning a failure increases agency has some support from organizational-behavior research on attribution style, and the claim that a leader's modeling shapes team norms is closer to consistent anecdotal report across many organizations than a measured finding. No research has tested whether pairing a leader's explicit ownership with a Collaborative Problem Solving conversation produces better outcomes than either alone — this combination is a reasoned extension of two separately credentialed ideas, not a studied one.