Why Talking It Through Doesn't Stop the 9pm Relapse
And how Ulysses Contracts sharpens Collaborative Problem Solving in return.
Collaborative Problem Solving has two people — often an adult and a child, but the method works for any two people stuck in a repeated conflict — sit down outside the heat of the moment and jointly figure out what unsolved, specific problem is actually producing the blow-up, then build a solution neither could have imposed alone. A Ulysses contract, named for the myth where Ulysses had his crew tie him to the mast so he could hear the sirens' song without steering the ship into the rocks, is a binding arrangement you set up in advance — locking yourself out of a choice, or making it expensive or embarrassing to make — precisely because you already know a future version of yourself, in the grip of temptation, would choose differently than you are choosing right now, clear-headed. The two solve neighboring problems: Collaborative Problem Solving figures out what the recurring fight is actually about, so a plan can be built that matches the real problem instead of a guess at it, while a Ulysses contract makes sure that plan survives contact with the exact moment it was built to survive — the one where willpower alone was never going to be enough. Neither replaces the other, and the honest limits of pairing them are covered further down.
What each one is actually for
Collaborative Problem Solving
Collaborative Problem Solving starts from the idea that a repeated outburst or refusal is not defiance for its own sake — it is what happens when someone doesn't yet have the skill to meet a specific demand a specific way, and nobody has correctly diagnosed which demand and which skill. So instead of imposing a consequence or a solution, the two people involved sit down calmly, outside the moment of conflict, and the person struggling names, in their own words, their side of what's actually hard about the situation. The other person names their own concern. Only once both sides of the actual problem are on the table do they jointly generate a plan — something concrete enough to actually try, like a specific new step in the bedtime routine — that both people had a hand in building, rather than one imposed by whoever has more power in the relationship.
Ulysses Contracts
A Ulysses contract works on a completely different moment: not the disagreement itself, but the predictable instant later on when a person, alone, facing a specific temptation, is going to want to break a decision they made while thinking clearly. Rather than trying to out-willpower that moment when it arrives — which is exactly the fight this method assumes you will lose — you remove the option in advance. That can mean literally locking something away, giving your phone's passcode to someone else for the evening, putting money into an account with a real penalty for early withdrawal, or telling a friend to publicly hold you to something so backing out costs you socially. The contract does its work before the tempting moment ever shows up, which is the entire point.
What you get out of pairing them
A plan built through Collaborative Problem Solving is usually a good plan — it's built from an accurate diagnosis instead of a guess, and both people actually agreed to it. But a good plan is still just a plan, and plans are exactly what a strong urge is built to override in the moment it matters. Bolting on a Ulysses contract at the exact point in that plan where willpower was always going to be the weak link means the specific, hard-won solution the two of you built together doesn't quietly die the first time it's tested by something stronger than resolve. Run the other way, a bare precommitment device with nothing collaborative behind it is just a lock with no diagnosis attached — it might block tonight's specific slip, but it does nothing about the actual mismatch between a demand and a missing skill that's producing the pattern in the first place, and a new workaround tends to show up somewhere else.
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 Ulysses Contracts rests on
-
Implementation intention closes intention action gap
randomised trials
Pre-committing to a specific situational cue paired with a specific response lets the behavior fire automatically when the cue occurs, without depending on in-the-moment willpower.
-
Removing future optionality protects present intent
randomised trials
Binding a future choice through an external cost or barrier prevents a later moment of weaker willpower from overriding a decision made while thinking clearly.
-
Temporal discounting erodes willpower
randomised trials
People systematically undervalue future consequences relative to immediate temptation which is exactly the bias a binding precommitment is designed to neutralize.
Where they actually meet
Plan B and a Ulysses contract share a low opinion of the deciding moment itself, and they hold it for the same reason: that the person facing it — whether that's a child at bedtime or an adult facing a craving at 9pm — is not going to reliably out-negotiate that moment with pure willpower, and treating it as a willpower problem is what keeps producing the same outburst or the same slip. Collaborative Problem Solving takes the negotiating out of the moment entirely by doing it earlier, calmly, together. A Ulysses contract takes the choosing out of the moment entirely by making the choice technically impossible, or expensive, before the moment arrives. Neither one asks the person to simply try harder next time.
The principle underneath both
A person's stated intention to behave differently and their actual behavior in the specific moment that intention is tested are not reliably the same thing, especially when that moment involves a strong urge, an unmet demand, or a skill gap the person hasn't been given the tools to close. Waiting for willpower to bridge that gap in real time is a bet that keeps losing, and both practices are, underneath, a refusal to keep making that bet.
What that makes the real goal
What both are actually organized around is making a good decision, made while calm and clear-headed, durable enough to survive the specific future moment that decision was always going to be tested against — rather than leaving that survival up to whoever the person happens to be, emotionally, when the moment actually arrives.
Other practices that serve the same goal
Motivational Interviewing pursues a version of the same target from a different angle, helping someone voice their own reasons for change in their own words before a hard moment arrives, on the theory that a person defends a plan they said out loud themselves more than one someone else handed them, and it has a substantial trial base of its own. On the precommitment side, commitment devices used in behavioral economics research — automatic payroll savings deductions, or apps that donate your own money to a cause you dislike if you miss a stated goal — target the identical intention-action gap a Ulysses contract targets, with a growing body of randomized evidence behind specific versions of the mechanism. And relapse-prevention planning in addiction treatment often does both jobs explicitly in one document: naming the actual triggers behind a pattern collaboratively with a counselor, then writing concrete, binding steps — who gets called, what gets locked away — for the specific moment those triggers show up.
A tradition that already does this
Alcoholics Anonymous, decades before either of these methods had a name, already combined the two moves in its own structure: a sponsor relationship that works out, collaboratively and honestly, what's actually driving a specific person's pattern of drinking, paired with concrete, agreed-upon precommitments for the exact moment a craving hits — a phone number to call before the drink, not after. It is not the same method, but it is the identical bet: diagnose together, then bind the moment in advance.
Building the lock as part of the plan, not after it
When the two of you sit down and jointly work out what's actually driving a repeated pattern — say, a teenager who keeps staying on their phone well past an agreed bedtime, and the real problem underneath turns out to be a fear of missing a conversation happening in a group chat without them — don't stop the collaborative conversation once you've named the problem and picked a solution. Ask, together, in the same sitting: what happens at 11pm tonight, specifically, when the urge to check one more time shows up, and what would make that choice harder to make in the heat of it rather than easier? Maybe the phone charges in the kitchen overnight by mutual agreement, not as an imposed punishment but as the binding piece of a plan the teenager helped design because it addresses their actual fear — a friend agrees to send a single wrap-up text before the group goes quiet. The lock is different from an imposed rule precisely because it was built inside the same conversation that diagnosed the real problem, which is most of why it tends to actually hold.
Using the moment a lock gets tested to find the real problem
A precommitment device that keeps failing — a phone locked in a drawer that gets fished back out, a savings account someone finds a way to raid early — is not just evidence that the lock was too weak. It's a signal worth treating as data for exactly the kind of joint diagnosis Collaborative Problem Solving runs: sit down, outside the moment, and ask what specific unmet demand made breaking the lock worth the trouble it took. Often the answer reframes the whole plan — a person who keeps overriding a spending lock at 9pm might not have a willpower problem at all; they might be avoiding a specific, nameable dread about being alone with their own thoughts once the evening goes quiet, and no lock addresses that until someone actually asks what the lock is being used to avoid. The failed contract, read this way, becomes the exact information Collaborative Problem Solving needs to build a plan that fits the real problem instead of a second, slightly stronger lock aimed at the wrong target.
The group chat and the kitchen charger
You and your kid have had the bedtime-phone fight four nights running, and you finally sit down on a Saturday afternoon, not at 11pm, and ask them directly what actually happens in their head when the phone buzzes after lights-out. They tell you, a little embarrassed, that their friend group makes plans in a chat that goes quiet by midnight, and missing an hour of it means showing up Monday not knowing what everyone's talking about. That's the real problem — not defiance, a specific, nameable fear of being left out of something ordinary. Together you land on a plan: the phone charges in the kitchen at 10:30, but before it does, they send one message into the chat saying they're signing off, so nobody wonders where they went. The charging spot in the kitchen is the lock. The goodbye message is the part that makes the lock feel like it's solving their actual problem instead of just taking something away from them, which is the entire reason it's more likely to still be working in three weeks.
When this is worth reaching for
The two of you sat down together and diagnosed this correctly — everyone agrees on what the real problem actually is. And the plan still fails, every time, at the exact same predictable moment, where in-the-moment willpower is being asked to do work it has never reliably done. It runs the other direction too: an existing precommitment device keeps getting broken, and nobody has yet asked, calmly and together, what the break is actually protecting the person from.
Where this does not apply
If the conflict itself hasn't been correctly diagnosed yet, adding a lock is premature and can make things worse — a precommitment device built around the wrong problem just becomes one more imposed rule to resent and route around, and routing around it teaches exactly the skill you didn't want reinforced. And a Ulysses contract built without any collaborative buy-in from the person it binds — a lock imposed on someone rather than built with them — tends to be experienced as punishment, which triggers exactly the kind of defiance Collaborative Problem Solving was designed to prevent in the first place, undoing the very method it was supposed to be paired with.
What the evidence does and does not support
Collaborative Problem Solving's core mechanisms — treating a behavior as a skill gap rather than defiance, and building solutions jointly rather than imposing them — draw on a real base of clinical and observational research, including studies in schools and juvenile justice settings, though the method as a packaged whole has fewer large randomized trials than its individual pieces do. Precommitment devices sit on firmer experimental ground: implementation intentions and removing future optionality through binding costs both have substantial randomized-trial support across behavior-change contexts unrelated to any specific conflict method, from savings behavior to smoking cessation. What's untested is the pairing itself — nobody has run a trial on families or individuals using a jointly built solution with a jointly built lock attached to it, against either piece alone. The fit described here follows from what each piece already does on its own, not from a study of the combination, and it should be treated as a reasoned prediction rather than a demonstrated result.
Practice this with IX Coach
The two practices on their own
Other pairings with these practices
- 168 Hours Time Audit and Ulysses Contracts (Precommitment Devices)
Seeing the gap between your hours and your priorities is not the same as closing it. A binding precommitment is the second half.
- Action Planning (Implementation Intentions) and Ulysses Contracts (Precommitment Devices)
An if-then plan works until the moment itself is loud enough to override it. Here's what to add when that keeps happening.
- Attention Management and Ulysses Contracts (Precommitment Devices)
Protecting focus in the moment fails the same way every time. A binding commitment made in advance is what actually holds when willpower runs out.
- Behavior Design (Environment Design) and Ulysses Contracts (Precommitment Devices)
Environment Design nudges you toward the good option. A Ulysses Contract removes the bad one entirely. When each one actually holds.
- 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.
- Collaborative Problem Solving and Action Planning (Implementation Intentions)
A solution both of you agreed to can still fall apart by Tuesday. Two different reasons that happens, and two different fixes for each.
- Collaborative Problem Solving and Active-Constructive Responding
Handling a child's meltdown and hearing a partner's good news lean on the same skill: staying curious before you react. How to borrow each one.
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).
- implementation intention closes intention action gap
Pre-committing to a specific situational cue paired with a specific response lets the behavior fire automatically when the cue occurs, without depending on in-the-moment willpower. Shared by 28 practices in the corpus — here in 50/30/20 Budget Rule.