Using Collaborative Problem Solving to enhance Calm Company Design

What each one is actually for

Collaborative Problem Solving

Collaborative Problem Solving's actual technique — what Ross Greene calls Plan B — is a structured conversation that happens away from the moment of conflict: name the other person's concern about a demand, in their own words; name your own concern about the same situation; then work out, together, a solution that addresses both rather than one side imposing a rule on the other. The premise is that behavior which looks like resistance or defiance is usually a mistaken strategy for meeting a real, unstated need — not badness to be corrected, but a problem still waiting to be named out loud.

Calm Company Design

Calm Company Design starts from the claim that urgency at work is mostly a design choice, not a fact of business — a chat message that demands an instant reply, a meeting that could have been an email, a culture where being constantly available reads as commitment. The practice is to name the specific manufactured-urgency habits actually running a team and remove them on purpose: protected, uninterrupted blocks for real focused work, async communication that doesn't require an instant response, fewer and shorter meetings. It doesn't ask anyone to work harder or care more about deadlines. It asks what manufactured urgency is currently doing the damage, and takes it out.

What you get out of pairing them

The reason to bother naming an unsolved problem instead of just enforcing a rule is that a rule without a diagnosis tends to produce compliance that doesn't hold: a team member told to stop pinging in chat after hours will often keep doing it anyway, quietly, because the actual driver — fear of looking unresponsive, a manager who says one thing and rewards another — was never addressed, just told to stop. The reason to bother removing manufactured urgency is separate but related: chronic overwhelm at work is frequently treated as something to simply push through, and pushing through a manufactured cause, rather than a real one, means absorbing stress that a genuine structural change could have removed instead. Neither fix requires anyone to become more resilient. Both assume the actual cause is findable and removable, if someone is willing to look for it specifically rather than assume it's just how work 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 Calm Company Design rests on

• Protected focus time improves deep work observational studies
  Structuring uninterrupted blocks of time protects the conditions required for high-quality cognitive work that fragmented attention otherwise prevents.
• Reducing artificial urgency lowers chronic stress observational studies
  Removing manufactured urgency cues like constant chat and unnecessary meetings and replacing them with async focused-work structures lowers chronic workplace stress.

Where they actually meet

Both treat what looks like a personal failing — a child's outburst, a team's chronic overwhelm — as evidence of a structural, removable cause rather than a character flaw to punish or grit through. Collaborative Problem Solving's technique is naming: putting the mismatch between a demand and a person's actual capacity into words, out loud, where both sides can look at it together instead of one person simply living inside it. Calm Company Design's technique is also naming, aimed at a different target: identifying manufactured urgency specifically, rather than treating 'work is just stressful' as a fact requiring no further diagnosis. In both, an experience that was invisible and simply endured — the outburst that seems to come from nowhere, the overwhelm that seems like the cost of doing business — becomes something named and, once named, something that can actually be changed.

The principle underneath both

What reads as a personal failing at either scale — a child who 'won't just behave,' a team that 'can't seem to keep up' — is frequently a structural cause that has never been named specifically enough to remove. Naming it does the real work; punishing the symptom or pushing through the overwhelm does not, because neither one touches the actual cause sitting underneath.

What that makes the real goal

If naming the specific structural cause is what actually changes anything, the goal in both cases is the same: replace a vague, blame-shaped account of what's wrong — 'he's being difficult,' 'we're just busy' — with a specific, removable cause that someone can actually act on. Once a cause has a name, it stops being a fact of life and starts being a design decision someone made, which means it's also a design decision someone can unmake.

Other practices that serve the same goal

Root cause analysis, a structured method used across engineering and operations to repeatedly ask 'why' until the underlying cause of a failure is found rather than stopping at the first symptom, chases the same objective through a different discipline's tooling, with its own track record in manufacturing and operations contexts. In organizational psychology, psychological safety research — the finding, from Amy Edmondson's work, that teams where people can name a problem without fear of blame perform measurably better on error-catching and learning — supports the naming half of this specifically, independent of Calm Company Design. And 'no-meeting days,' a lighter-weight structural change some companies adopt unilaterally, pursue the same manufactured-urgency-removal goal as Calm Company Design's protected time without requiring the full philosophy behind it.

A tradition that already does this

Jason Fried and David Heinemeier Hansson's own books describe this exact move repeatedly and by name — treating 'busy' as a choice a company makes rather than a condition it suffers, and tracing specific overwhelm back to a specific removable habit, an open-door policy that guarantees interruption, a chat culture that rewards instant replies, rather than accepting it as an unavoidable cost of growth. That is the identical instinct Collaborative Problem Solving applies to a child's outburst, just aimed at an organization instead of a person — both refuse to treat the presenting symptom as the actual explanation.

Using a Plan B Conversation on a Resistant Team Member

Calm Company Design tells you to remove artificial urgency but says little about what to do when a specific team member resists the new structure — skips the protected quiet-hours block, keeps pinging in chat anyway, even after the policy is announced. Collaborative Problem Solving's actual method, developed for a different context but not specific to children, is to assume the resistance is a mistaken strategy for a real unmet need, and to sit down and name that need before proposing anything further. Applied to a team, that means asking the resistant person directly what makes the old always-on habit feel necessary — a fear of looking unresponsive, a manager who says the new policy exists but still expects instant replies in practice, a client relationship that genuinely does require fast turnaround. Build the new structure around that actual answer, rather than mandating the async policy and treating continued pinging as noncompliance to be corrected.

Protecting the Unhurried Time a Plan B Conversation Needs

Plan B asks an adult to sit down and jointly diagnose an unsolved problem with a child in real time, which requires a kind of unhurried attention that's genuinely hard to produce inside a day already run by manufactured urgency of its own — a phone checked mid-conversation, a meeting looming in twenty minutes, an inbox that feels like it's owed a reply. Calm Company Design's core move, removing artificial urgency cues and protecting real blocks of uninterrupted time, gives Plan B something it needs but doesn't supply on its own: an actual protected window long enough for a real diagnostic conversation to happen without either person feeling rushed toward a quick fix. Treat one recurring block of unhurried time — the way a calm company protects deep-work time from meetings — as reserved specifically for this kind of conversation, not as time that gets the first claim any errand makes on it.

Tuesday, 4pm, the Same Fight About Homework Starting Again

It's Tuesday at four and your child is refusing homework again, and you can feel the old script loading — the raised voice, the ultimatum, the exact fight you had Thursday. You've got twenty minutes before you need to leave for a pickup, so instead of starting the conversation now, rushed, you name it out loud instead: 'this matters, and I don't want to rush it — let's actually figure this out tonight after dinner, both of us, no phone.' Naming the unsolved problem is itself the first move, done in the moment even though the real conversation waits. Protecting a genuinely unhurried block for it later — the way you'd protect focused work time from a meeting that could've been a message — is what makes the actual Plan B conversation possible that evening, instead of another rushed, half-present attempt squeezed into the twenty minutes you didn't actually have.

When this is worth reaching for

A conflict, at home or on a team, has recurred enough times that the obvious explanation — defiance, laziness, not caring — has stopped being satisfying, because it doesn't explain why the same specific thing keeps happening in the same specific way. It matters especially once a rule or a policy has already been stated out loud and hasn't changed the behavior, which is usually a sign the actual cause was never addressed, only told to stop.

Where this does not apply

Collaborative Problem Solving is built around one person's specific unmet need, diagnosed through direct conversation, and it doesn't scale cleanly to a whole team's structural habits the way Calm Company Design does — running a full individual Plan B conversation with every resistant team member would be a slow, person-by-person way to fix what a straightforward policy change, backed by actual management follow-through, could fix faster and for everyone at once. And Calm Company Design's changes to meeting culture and chat norms do nothing on their own for a parent-child conflict that has no organizational structure to redesign around it — a family isn't a company, and 'protected focus time' has no obvious equivalent for a five-year-old refusing to get dressed.

What the evidence does and does not support

Collaborative Problem Solving's core technique — externalizing an internal pattern into a form both people can examine — has randomized-trial support from a wide base of research on structured, externalizing conversations reducing conflict. Its premise that difficult behavior reflects an unmet need rather than bad intent has clinical-level support from Greene's own model and practitioner outcomes, with less controlled-trial weight than the externalizing mechanism itself carries; the claim that jointly generating a solution increases follow-through is observational. Calm Company Design's two principles — protected uninterrupted time improving deep work, and removing manufactured urgency lowering chronic stress — both rest on observational research on knowledge workers rather than randomized trials, and much of the underlying philosophy comes from Fried and Hansson's own applied experience rather than academic study. No research has tested applying Plan B's method to organizational habits specifically, or using protected time to support these conversations directly; the connection drawn here is a structural analogy between two separately evidenced approaches, not a studied combination.