Couples coaching, online
You can't debug your way out of this one.
High-performing analytical couples tend to fail in a specific way: they treat the marriage like a system to optimize, and the optimizing makes it worse, because the fight that keeps happening isn't a broken process. It's a judgment, a settled conclusion each of you has about the other's basic character, and judgments don't respond to debugging. This page is for engineer, founder, doctor, and dual-career couples who've already tried being competent and are baffled that it didn't work.
You've probably run the whole playbook. The shared calendar, the weekly sync, the conflict-resolution framework from the management book, maybe an actual retro after the bad fights. Each one worked for a little while, which was the cruelest part, because it kept the theory alive that this was a problem you could solve with better execution. Meanwhile the same fight keeps recurring in a slightly different form, one of you goes cold and analytical, one goes hot, or you both go quiet and call it being mature, and the post-mortems have started to feel like depositions. I studied this kind of couple before I ever coached one, my research at Berkeley was on how programmers juggle love and work, and the pattern on this page is the one I watched for years. I was not the first Berkeley sociologist on this ground either: Arlie Hochschild named the whole condition the time bind, when work becomes home and home becomes work, and the management tools migrate with the hours.
Why optimizing backfires here
An engineer's instinct is that the parts of a system aren't good or bad, they just are. A slow query isn't an evil query, it's just slow. But somewhere back in your recurring fight, each of you stopped treating the other's nature as a neutral part and started treating it as a crime. "She thinks out loud" became "she's chaotic." "He needs a minute before he answers" became "he shuts me out, he doesn't care." That switch, from difference to flaw to accusation, is the judgment, and it changes how every tool you use behaves. Inside a running accusation, the weekly sync becomes evidence-gathering, the "I" statement becomes an exhibit, and the retro becomes a trial. Worse, the judgment generates its own supporting data: the more one of you treats the other as cold, the more they shut down; the more one treats the other as chaotic, the more flustered and defensive they get. You're both producing the logs you keep pointing at. No system settles down while the observer is amplifying the error signal.
The fixer and the fixed
The most common version of this deserves its own name. One partner, often the more senior engineer of the two, becomes the fixer: every bit of distress from the other gets treated like a ticket, triaged, and answered with a solution, delivered with real love and growing exhaustion. The other partner becomes the fixed: constantly diagnosed, subtly outranked, and starved of the one thing they were actually asking for, which was closeness, not repair. And each of these is a defense. The fixer's nonstop competence is protecting against a helpless feeling they've never made peace with. The fixed one's rising emotion is protecting against a fear that on their own, unhelped, they don't quite count. Each was drawn to exactly this partner, and each is now blaming the other for the very thing that drew them. That whole machine, with its parts named, is the actual root cause, and it's laid out in full here: The Unforgiven Self.
What we do
Twelve sessions, four stages, one fix at the system level: the work. First we build something your retros never did, an accurate model of both people, including the parts each of you has been hiding from the post-mortem. Then we watch the live fight and catch the judgment the moment it fires. Then we remove the thing amplifying the error: the conviction that your partner's nature, or yours, is a defect that should be different than it is. And finally your existing skills work, because process works fine between people on the same side, it just never worked between a prosecutor and a defendant. Costs and details, written the way an engineer would want them, are on how it works.
Before you start
Asked before starting
We’re analytical people. Is this going to be touchy-feely?
No. The approach is basically a mechanism: parts that fit together, a loop with a clear cause and effect, and a specific claim about where you can intervene. Analytical couples usually take to it fast, because it explains the data, including why all your previous attempts to fix things didn’t work. What it asks of you is accurate reporting about yourself rather than performed emotion, which, for a lot of engineers, turns out to be the harder skill.
Why do our fights keep happening if we’ve already figured out the root cause?
Because the analysis stopped one level too high. You found the pattern: who escalates, who shuts down, which topics are landmines. The level underneath is the judgment, a settled conclusion each of you has about the other’s basic character, which no amount of process improvement touches, because it isn’t a process. It’s a conviction. You don’t debug convictions. You drop them, and there’s a way to do that.
One of us treats the marriage like a project to manage. Is that the problem?
It’s usually half of it. The fixer’s constant problem-solving is armor: competence aimed at the helpless feeling of not being able to make another person okay. And the partner being fixed is usually running the opposite armor: leaning on their own experience to avoid the humiliation of being a ticket in someone’s queue. Each is judging the other, "cold and robotic" vs. "irrational and unfixable," and each judgment makes itself come true. Both chairs get worked on here.
Our schedules are brutal and one of us travels constantly. Can the logistics work?
Yes. Sessions are 60 minutes over video, weekly, with morning and midday US hours the norm, and a couple in two different cities on session day is completely normal. What the work does need is the one thing no calendar trick provides: both of you actually present for the hour, laptops shut. Twelve hours over about three months. Most couples in your situation have spent more than that on a single offsite.
From the essays