coaching / cofounder-recurring-conflicts · article
coaching/ · 2,200 w · 10 min · ✎ dialogue

Cofounder Recurring Conflicts

Two companion frameworks for diagnosing why the same fights keep recurring — and what to do about them. The first, "Old Wounds and Old Ways," is Jason's original synthesis drawn from six cofounder teams (mostly YC founders), explaining why two competent, non-broken people keep colliding in the same specific ways. The second, "Stop Trying to Fix Your Cofounder," identifies the cognitive error that makes those collisions so damaging and offers the externalization reframe from narrative therapy as the alternative. Together, they form a complete picture: understand the dynamic underneath the surface fight, then shift out of personalization and into problem-solving as a team.


Old Wounds and Old Ways

The surface presentation always looks like one of two things: "My cofounder is way too sensitive — I can't say or do anything without them overreacting." Or: "Why can't this person just get this one thing right? I do my part." Both feel completely reasonable from the inside. Neither sees the full picture.

The underlying reality: the conflict is rooted in a specific interaction between two things — one belonging to each person. An Old Wound is an emotional trigger — a sensitivity that causes a reaction disproportionate to what actually happened. You can feel it activate in the moment even when you can't stop it. The overreaction is real; its logic is rooted in something that predates the partnership. An Old Way is an ingrained behavioral habit that a cofounder has carried for years. It may have been valued in previous jobs or was always a weakness that other strengths compensated for. Either way, it is baked in — changing it is genuinely hard, not a matter of willpower.

The dynamic: one founder's Old Way hits the other founder's Old Wound. The Old Wound makes the Old Way feel intentional — like they're doing it specifically to get at you. The shame the other person feels about their Old Way makes your reaction feel like an attack on their character. Neither interpretation is true. But both feel true. That's why the fight never resolves: it's always about the surface issue (the deadline, the standup, the spending decision) and never about what's underneath. A 30-year study out of the University of Minnesota found that early relational experiences shape how we handle conflict decades later. This runs deep. You can't logic your way past it.

The Case Study

A CTO who is organized and conscientious, paired with a CEO who is creative and relaxed about structure. When the CEO misses a deadline, what the CTO says is: "Why can't you just do what you say you're going to do?" What the CTO doesn't say: "It kills me when people don't follow through. It always has. Long before this company existed." That's his Old Wound — reliability — shaped by a boss who let him down, a partner who burned him, a pattern that left a mark. The CEO responds: "Why do you have to be so intense and aggro all the time?" What the CEO doesn't say: "I know I should be better at this. I'm trying. But it's never enough, and I'm a little ashamed of it." That's her Old Way — loose execution — something she has always had, has tried to change, and hasn't successfully shifted.

Because neither can see the other's inner experience, the fight stays on the surface. Always about the deadline. Never about what's underneath. Jason's personal example: "My wife was bullied in middle school by girls who'd make fun of her and laugh in that passive-aggressive way. It left her sensitive to being laughed at when there's no obvious joke. I sometimes look at her and just laugh out of happiness or because of something endearing she did. She gets annoyed. But laughing is spontaneous. I can't always explain it fast enough, and by then her Old Wound is already activated. Her Old Wound: being laughed at. My Old Way: laughing without thinking."

How to Know If You're In It

Two self-diagnostic questions — one for each role. For the Old Wound: "Is there something that, when you step back honestly, you know isn't as big a deal as you make it? But in the moment, it activates you so strongly you can't stop yourself?" For the Old Way: "Is there something you know you should change, but every time you try, it doesn't stick? And you're a little embarrassed about it?" If both cofounders can identify their own answer to the relevant question, the Two-Conversation Protocol becomes possible.

The Two-Conversation Protocol

Conversation 1: The Origin Story. Each person first spends time alone tracing where their wound or way comes from — a previous boss, a college roommate who burned them, a pattern that left a mark. Then sit down together. Each person tells a story from before this company about where it comes from — not about the cofounder. The other person's only job is to listen and play back what they heard. No challenging. No problem-solving. No "well, but here's the thing about that." This sounds too simple. But it changes things — because for the first time, each person sees why the other reacts the way they do. The CTO's rage about missed deadlines stops being about disrespect and starts being about a wound that runs through his whole professional life. The CEO's shame about her execution stops being something the CTO dismisses and starts being something he can actually see.

Conversation 2: Small Adjustments (scheduled a few days later). For the person with the Old Wound: "What part about this interaction hurts the most? Is there a small adjustment that would help?" The goal is not to eliminate the behavior — it's to design a small buffer between the behavior and the trigger. Maybe it's getting an early heads-up when a deadline will slip, rather than silence until the last minute. For the person with the Old Way: "What's the hardest part about shifting this? How can I help you with it?" Here, diagnosing the type of problem matters. A cue problem — they genuinely forget in the moment — is solvable with a system relatively quickly. An identity problem — they've always been "the creative one" and adjusting threatens who they understand themselves to be — is harder, and requires acknowledging that the identity and the behavior can be separated. A shame problem — they feel broken for having the Old Way, and every time it gets raised they hear "you're deficient" — requires the other person to be explicit: "This is about the pattern, not about who you are." On progress: "A 20% improvement on something they've struggled with their entire adult life is worth recognizing. What gets reinforced gets repeated."

The critical reframe: "The problem isn't your cofounder. It's the interaction between your Old Wound and their Old Way — sitting in the middle of the table, with both of you on the same side looking at it. The moment one of you thinks 'this is something wrong with you that needs fixing,' you're fighting each other, not the real problem."


Stop Trying to Fix Your Cofounder

The companion framework — focused on the specific cognitive and relational error that makes cofounder conflict so damaging, and the reframe that dissolves it.

The presenting situation: your cofounder screwed up again. Lost their temper in a meeting with a key hire. Missed a deadline and forced you to scuttle a launch. Their risk aversion has turned every decision into a week-long debate. And your internal monologue frames this as: "what is wrong with them?" That framing is the problem. It treats the situation as a character flaw — something broken in the other person that needs to be fixed — and in doing so, it enacts two of the Four Horsemen simultaneously: criticism (treating the behavior as evidence of a character problem) and contempt (the implicit positioning that you have this handled and they don't). See cofounder-gottman-framework for the Four Horsemen in full.

Here's what makes this so important: criticism and contempt feel true in the moment. If your cofounder keeps doing the same thing, it is natural to conclude there's something wrong with them. But even when the thought is understandable, expressing it — or letting it shape how you treat them — makes everything worse. "If you were on the receiving end of this, if you were told that something was fundamentally wrong with you or that your co-founder was just better than you... would that make you want to be collaborative? Would that make you want to work on yourself?"

Externalization: The Core Concept

The alternative comes from narrative therapy, developed by Michael White and David Epston: externalization. Rather than treating a problem as evidence of what a person is, you separate the problem from the person. Disorganization is not who your cofounder is. Disorganization is something the two of you are dealing with together. The Same Team Principle reframes behavioral challenges the way you'd naturally frame an external threat. If Apple changes their terms of service and you have to rebuild half your app, you don't turn to your cofounder and say "this is all your fault, what is wrong with you?" You say: "Okay, let's figure out what's going on and how we build a plan to solve this together." The same logic applies to your cofounder's behavior: "Your co-founder's anger problem doesn't define who they are. It is an external obstacle that the two of you would like to address." This is not about ignoring behavior or lowering standards. It's about stopping the personalization and focusing on the outcome you actually want.

The 6-Step Protocol

Step 1: Align on a shared outcome. Start with something you both care about and both agree could be better — shipping product faster, winning more deals, improving team morale. This establishes you're working toward the same thing before introducing any tension.

Step 2: Name the obstacle without making it about them. Don't say "you need to stop doing X." Instead: "Hey, I've noticed that we're missing some of our product deadlines. And I wonder if it's related to your desire to make an amazing product — because you're a great engineer. I'm just wondering if we could figure this out together." No accusations. No character judgment. Two founders trying to make their company better.

Step 3: Get their side of the story. What is the behavior trying to protect or achieve that you don't understand yet? Risk aversion may be shielding against a mistake they made in the past. Anger may signal they don't feel heard. "You won't understand the problem in full until you invite them to share their side of the story and they feel safe and won't be judged for explaining their perspective."

Step 4: Change the environment, not the person. This is the most underused lever. People can work on being less tardy or less reactive — but that change is slow and often backslides under stress. Changing a process, a tool, a role, a schedule, an expectation — these can be implemented in a day. "If someone is forgetful, do you think getting them to improve their memory is going to be easier or giving them a checklist? One of those can be implemented in a day. The other might take months or even years."

Step 5: Learn the warning signs and create pullover points. The behavior will come back. Old habits resurface under stress. Agree in advance on early warning signs — the leading indicators that the pattern is creeping back. Create a protocol: a code word, a way to signal "I'm about to blow up, I need to step out." "Products always have bugs. Partnerships always have recurring friction. You need a good rollback system — for the two of you and your dynamic as well."

Step 6: Ask what you can do to support. Both people are contributing to the dynamic. If the framing is really "we're on the same team dealing with an external obstacle," then both of you can change. Ask: "How can I help you with this? What would make it easier for you to shift this pattern?" And ask yourself the same question — how am I contributing to this situation, and what could I do differently?

"The same team mindset isn't going to change anything overnight, but it can over time improve your dynamic so that you're no longer bickering with each other, pointing fingers, and you're actually solving problems, moving forward, and feeling better about each other along the way."


Thread · 0 replies+ add reply
no replies yet — be the first to write back to this article.