The Conflict Protocol

The Problem

There's a conversation you need to have, and you've been putting it off for weeks.

Maybe it's with your co-founder about their work ethic. Maybe it's with a direct report whose performance has quietly slid. Maybe it's with an investor about the milestone you missed. You know roughly what you need to say. What stops you is the how. You can't see a version of the conversation that doesn't end in a mess, so you keep choosing the mess of silence instead.

And silence has a cost. The thing you're avoiding doesn't sit still. It grows. The resentment compounds, the behaviour repeats because nobody named it, and by the time you finally crack, you're not having a conversation anymore. You're detonating.

Here's the part most people get backwards. The hard conversations that go badly almost never fail in the room. They fail before you walk in, because you show up unprepared, running on emotion, armed with your interpretation instead of the facts, with no clear idea of what you actually want out of it.

So you flip that. You do the hard work before you open your mouth. By the time you walk in, the conversation itself is the easy part.

Who This Is For

Any founder with a specific difficult conversation coming up who would rather prepare for it than wing it. Not conflict in the abstract. The real one, with the real name attached, that's been sitting in your chest since last Tuesday.

What You'll Need

• Time commitment: Thirty minutes alone to prepare, plus the conversation itself.
• Prerequisites: One specific conversation you've been avoiding. Not a category. The exact one, with the exact person.
• Tools: Paper or a notes app. You're going to draft before you deliver.

The Protocol

The whole protocol lives in the preparation. Five of the seven steps happen before the other person is even in the room. That's not padding. That's the design. Walk in prepared and the conversation runs itself. Walk in raw and no technique will save you.

Name the Outcome You Actually Want

Write down the specific outcome you want from this conversation.

"I want them to understand" is not an outcome. That's a hope. What do you want to be different afterwards? A changed behaviour? A clear agreement? A resignation? Name it in plain words.

And check the outcome before you go further. If what you actually want is for them to feel bad, stop. That's punishment, not a conversation, and it will leak into every word you say. Go back and find what you genuinely need to change.

Write Down Three Facts, Not Interpretations

Facts are observable, undeniable, and free of judgement. "You were late to three meetings this week" is a fact. "You don't care about the team" is a story you've built on top of the fact.

Test each one with the camera question. Would a camera in the room have recorded it? "Checked their phone four times during the update" passes. "Was disrespectful" fails, because a camera can't film disrespect, only the phone. Start with facts, because facts are the one thing that can't be argued with.

Write Down Their Likely Perspective

This is the step almost everyone skips, and it's the one that changes the conversation most.

Before you walk in, write down what you think their side of it is. If you can put their view into words in advance, you won't get blindsided by it, and you'll listen better, because you'll be confirming a hunch instead of hearing it cold and reacting. If you genuinely can't imagine their perspective at all, you're not ready. Go talk to someone who knows them first.

Open With Your Intention, Not Your Complaint

Start the actual conversation by naming where you want to end up. "I want to talk about X, because I want us to get to Y."

That single sentence frames the whole thing as collaborative instead of adversarial. Compare it to the usual opener. "I need to give you some feedback" isn't an intention, it's a threat, and the other person's guard goes straight up before you've said anything real. Lead with the destination, not the accusation.

State Your Facts, Then Stop Talking

Deliver the three facts you prepared. Then close your mouth.

The silence after the facts is where the real conversation happens. Most people can't stand it, so they fill it with more arguments, more examples, more justification, and a conversation quietly turns into a lecture. Don't. The urge to keep talking will be strong. Sit in the silence and let them fill it. It's the most powerful tool you've got, and it costs nothing but nerve.

Listen, Then Restate Before You Respond

When they answer, don't counter. Restate. "So what I'm hearing is..."

That one phrase de-escalates more conflict than any clever technique. It proves you actually listened. It gives them room to correct you if you've got it wrong. And it slows the whole thing down enough for both of you to think instead of react. Just don't confuse restating with conceding. "What I'm hearing is you felt unsupported" is restating. "You're right, I should have supported you more" is agreeing. Keep them separate until you've actually decided which one you mean.

Close With a Specific Agreement and a Date

Vague endings produce vague outcomes. "Let's both do better" changes nothing.

Name the specific thing that will be different, and set the date you'll both check on it. "We'll meet in two weeks to see how the new standup cadence is landing." And if they won't commit to anything specific, that's information too. It tells you the conversation isn't finished, or that the relationship has a bigger problem than the one you came to talk about.

What You'll Find

The preparation matters more than the delivery, every time. Most hard conversations go sideways because someone walked in unprepared, driven by feeling, armed with interpretation, with no clear outcome in mind. This flips it. By the time you're in the room, the hard part is behind you.

The other thing you'll notice: the conversation is almost always smaller than the dread. You'll spend a week bracing for a blow-up and then watch it resolve in eight quiet minutes. The weight was never the conversation. It was the avoiding.

Adaptations

For co-founder conflict: Add one step before you start. Agree a "no ultimatums" ground rule out loud. Co-founder conversations carry existential weight, and the moment "maybe we shouldn't do this at all" is on the table, honesty shuts down. Take the nuclear option off the table first, and the real conversation becomes possible.

For a performance conversation: Add the consequences, not as a threat, as transparency. "If this doesn't shift in thirty days, here's what happens next." People deserve to know the stakes. Withholding them isn't kindness. It's setting someone up to be surprised by a decision you'd already half made.

For remote or async teams: Don't do this over Slack, ever. Video at the minimum, in person if you can. If you truly have to go async, send the facts in writing so they aren't ambushed, then schedule a live call for the response. A conflict conversation in a text channel is a fight waiting to happen, because tone is the first thing text loses.

Where This Came From

This is built from Brené Brown's rumble work crossed with the Crucial Conversations model, bent to fit the specific power dynamics of a startup, where the person across the table might be your co-founder, your first hire, or the investor who owns a chunk of your company.

The "state your facts, then stop talking" step didn't come from a book. It came from watching hundreds of coaching conversations and noticing one pattern over and over. The founders who got the best outcomes were the ones who learned to sit in the silence. Everyone else rushed to fill it, and filled it with the exact thing that turned a conversation into a war. The discipline to say your piece and then be quiet is rare, and it's most of the skill.

Related Protocols

• The Effective Feedback Protocol. The Conflict Protocol prepares you for a specific hard conversation. The Effective Feedback Protocol is the repeatable structure for the smaller, more frequent ones, so feedback stops being a dreaded event and becomes something your team does in the company's own language.
• The Radical Reception Protocol. This one is about giving the hard thing. Reception is the other half: how to take feedback without going defensive, which is the skill that lets a conflict conversation run both directions instead of one.
• The Co-Regulation Protocol. A hard conversation only works if you can stay regulated inside it. When the other person's fear spikes and yours rises to meet it, this is how you keep both nervous systems out of the fight, so the conversation stays a conversation.