Using Collaborative Problem Solving to enhance Never Eat Alone
And how Never Eat Alone sharpens Collaborative Problem Solving in return.
Collaborative Problem Solving (CPS) is an approach to a child's behavioral outburst that starts from the assumption the outburst is a mistaken strategy for solving a real problem the child can't yet solve alone, rather than defiance, and has the adult and child jointly name that problem and build a solution together instead of the adult imposing a consequence. Never Eat Alone names a networking practice built around treating ordinary occasions — a meal, a hallway conversation — as chances to build relationships deliberately, starting from offering something of value before ever asking for anything. On this reading, both rest on the same reversal: instead of treating a strained relationship as something to fix by asserting control or making an ask, you invest in it collaboratively or generously first. The domains are different enough — a parent managing a meltdown, an adult building a career network — that the honest read is the overlap sits at the level of principle, not practice; nothing suggests running one inside the other changes outcomes in either domain.
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 Never Eat Alone rests on
-
Small wins compound
randomised trials
Repeating a small consistent action accumulates over time into a result too large to produce in a single step.
-
Reciprocity through generosity builds relationships
practitioner report
Offering help or value first before asking for anything builds stronger relational reciprocity than asking first.
Where they actually meet
CPS's claim that a solution generated jointly with the person who has the problem produces more durable follow-through than an imposed one, and Never Eat Alone's claim that offering help or value before asking for anything builds stronger reciprocity than asking first, are both claims that a relationship holds up better when something is built or given jointly than when it's imposed or extracted. CPS applies this to a single unsolved problem between two people who already have a relationship; Never Eat Alone applies it to relationships that don't exist yet, built through repeated small acts of offering value first. What flips in each is similar: a stance of "I need something from you, here's the consequence or the ask" becomes "let's figure out or build something together" — the other person moves from an obstacle in the way to a collaborator. Held together, that's the same underlying shift showing up in a child-behavior framework and a networking framework built for entirely different populations, without either in mind when the other was designed.
Using Collaborative Problem Solving to enhance Never Eat Alone
Never Eat Alone's generosity-first approach can stall when a specific relationship isn't responding — a contact who doesn't reply, a collaboration that keeps going sideways — and the instinct is often to assume disinterest and write the person off. CPS's underlying move, treating a behavior that looks like a problem as a mistaken strategy for meeting some real need rather than as a verdict on the person or the relationship, transfers directly: instead of assuming the unresponsive contact doesn't value the relationship, treat the pattern as an unsolved problem, maybe timing, maybe overload, maybe an unstated concern, worth naming and asking about directly. The concrete move is replacing "they're just not interested" with a direct, curious question about what's actually getting in the way, the same question CPS asks a child before assuming defiance.
Using Never Eat Alone to enhance Collaborative Problem Solving
CPS asks a parent to jointly problem-solve with a child around an unsolved problem, but that collaboration works better from a base of existing goodwill than from a cold start, and problem-solving conversations, by nature, tend to happen only when something has already gone wrong, which is a deficit-first way to enter the relationship. Never Eat Alone's principle of offering value first suggests investing in the relationship before the problem shows up: deliberately offer the child something, attention, a shared activity, a genuine question about their day, with no problem-solving agenda attached, the way a networker offers value before ever making an ask. The concrete move is scheduling connection time with no CPS agenda at all, so the collaborative problem-solving conversation isn't the only kind of undivided attention the child gets.
Sitting down with your kid after another blow-up at homework time
It's the third night this week homework has ended in a shouting match, and you're sitting across from your kid, both of you still a little raw. CPS says to name the unsolved problem together rather than hand down a consequence: "I've noticed homework's been really hard to get through lately — what's going on for you there?" But you also notice this is the first real conversation you've had all week that wasn't about a problem. Never Eat Alone's instinct says the collaborative question lands better if it isn't the only kind of attention your kid gets from you, so tomorrow, before homework is even mentioned, you take fifteen minutes to do something with no agenda, a walk, a game, nothing to solve. The problem-solving conversation still has to happen. It just isn't the whole relationship.
Where this does not apply
For an unsolved problem that needs to be addressed now — a child in an active behavioral crisis, a professional conflict with a deadline attached — pausing to build general goodwill first can read as avoidance rather than investment; CPS's direct joint problem-solving is built for exactly that moment and doesn't need a networking frame layered on top of it. Never Eat Alone's generosity-first approach also assumes some baseline safety and willingness to engage from the other person; it doesn't address a skill deficit CPS is specifically designed to diagnose, and substituting warmth for that diagnosis leaves the actual unsolved problem unsolved.
What the evidence does and does not support
CPS's core claim, that a joint, collaborative solution produces more durable follow-through than an imposed one, has observational support in the clinical literature it comes from, and its underlying reframe of misbehavior as an unsolved problem rather than defiance is a clinical account, not an RCT finding. Never Eat Alone's reciprocity principle is anecdotal, drawn from the author's own networking practice rather than controlled study, though the broader finding that small consistent actions compound has RCT support in other contexts. No research has tested applying a child-behavior framework to adult networking or the reverse; this page describes a shared principle, not a studied combination, and the honest read is that the two practices barely intersect in their actual domains even though the underlying logic rhymes.
Practice this with IX Coach
The two practices on their own
Other pairings with these practices
- 168 Hours Time Audit and Never Eat Alone (relationship-building networking practice)
A time audit shows exactly how many meals in your week go to no one — the raw material Never Eat Alone's networking practice asks you to stop wasting.
- 90-Second Rule and Never Eat Alone (relationship-building networking practice)
A ninety-second reaction can end a new relationship before it starts. Here's the one narrow point where these two practices meet.
- Action Planning (Implementation Intentions) and Never Eat Alone (relationship-building networking practice)
Generosity-first networking rarely fails from bad intent; it fails from never happening. A specific if-then plan is what makes it actually occur.
- Attention Management and Never Eat Alone (relationship-building networking practice)
Never Eat Alone stays a good intention until it has a calendar slot. Attention management's blocking turns generosity into something you actually do.
- Behavior Design (Environment Design) and Never Eat Alone (relationship-building networking practice)
Generosity-first networking works, until willpower runs out on a busy week. Environment design is how you make reaching out the easy default instead.
- Calm Company Design and Never Eat Alone (relationship-building networking practice)
A calm, async-first workplace and a network built one real favor at a time both remove invented urgency and keep what's genuine.
- Collaborative Problem Solving and 168 Hours Time Audit
A time log gives a CPS conversation actual evidence instead of impressions. Where the two fit, and where a log turns into surveillance instead.
- Collaborative Problem Solving and 25/5 Rule (Two-List Strategy)
A method for finding a child's hidden reason and a method for ruthlessly cutting a goal list share one move: naming what you're actually solving for.
- Collaborative Problem Solving and 5-4-3-2-1 Grounding
A child mid-meltdown can't do Plan B's give-and-take. 5-4-3-2-1 grounding may be the missing step that gets them there first.
- Collaborative Problem Solving and 90-Second Rule
A joint diagnosis can't happen while someone's still flooded. One reading of why the 90-second wait has to come before Collaborative Problem Solving.
- Collaborative Problem Solving and Acceptance and Commitment Therapy (ACT)
One practice catches a child's outburst before it's punished; the other catches the adult's own snap judgment about it. Here's how they meet.
- Collaborative Problem Solving and Accountability Partners
Collaborative Problem Solving builds a plan a kid agreed to. Accountability partnerships add the follow-up that keeps a good plan from quietly dying.
The principles underneath both
- externalizing makes pattern visible
Putting an internal pattern into an external, structured form makes it visible and available for examination instead of remaining implicit and merely enacted. Shared by 47 practices in the corpus — here in 168 Hours Time Audit.
- parts have positive intent
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. Shared by 3 practices in the corpus — here in Internal Family Systems (IFS).
- small wins compound
Repeating a small consistent action accumulates over time into a result too large to produce in a single step. Shared by 37 practices in the corpus — here in Agile Results (Getting Results the Agile Way).