To deescalate cofounder fight heat in the moment, stop the reply you want to send, shrink the frame to one issue, and buy enough calm that both of you can decide. Speed is usually the accelerant. Structure is the brake.
Recognize escalation before it owns the room
Escalation has tells. Sentences get absolute. Tone sharpens. One of you starts litigating history. The other goes flat or sarcastic. The topic widens from "this release" to "how you always operate."
Amy Gallo's HBR tip is blunt: when conflict spikes, do not react immediately. Reflect first. Ask what the other person might be experiencing. That pause is the first de-escalation move. It costs seconds and saves hours.
On text channels the risk is higher. Slack's guidance on de-escalating workplace conflict stresses listening and questions over answers, and getting enough distance that rational problem-solving returns. If the thread is already hot, stop typing. Move to a voice call or a short walk-apart with a return time.
A five-move cool-down sequence
Run this in order. Do not skip to persuasion.
- Pause the channel. No more Slack volleys. Say you are pausing, not abandoning.
- Name the state, not the verdict. "This is getting sharp" or "I am flooded" beats "you are being impossible."
- Shrink to one issue. Park the backlog. Perel's cofounder work in First Round Review is clear: address one issue; kill the absolutes; attack the situation, not the character.
- Take a real break if either of you is flooded. Gottman's stonewalling research shows that once physiological flooding hits, rational discussion is off the table. Agree at least twenty minutes. Do something soothing. Do not rehearse your case against them.
- Reopen with facts and a decision target. "We need to decide ownership of pricing by 4pm" is a re-entry. "We need to talk about everything that is wrong" is a restart of the fire.
Language that lowers heat
| Instead of | Try |
|---|---|
| "You always do this." | "This is the second time this month I felt cut out of the call." |
| "Calm down." | "I want us both able to decide. Can we take twenty minutes." |
| "That is ridiculous." | "Help me see the part I am missing." |
| "Whatever. Fine." | "I can live with option B if we write the owner and check Friday." |
| Long Slack essay | Three lines, then a live conversation |
Notice the difference. The first column prosecutes. The second column invites a shared problem. Slack's piece quotes the simple move "tell me more" until the other person's view is fully out. That is not agreement. It is oxygen.
What not to do while de-escalating
Do not perform calm while stacking new charges. Do not drag the team into a private fight. Do not use the break to recruit allies. Do not "win" by exhaustion and call it resolution.
Also do not confuse silence with de-escalation. Walking out without a return time is withdrawal, and it usually triggers pursuit. If you need space, name the return. "I am stepping out until 3:30, then we finish the decision" keeps the partnership intact while the nervous system resets.
Handle the room and the channel
Where the fight lives changes the tools.
In person or on video, lower volume and slow speech before you change content. Fast, loud defense keeps both nervous systems hot. On Slack or email, assume tone will be misread. Gallo's remote-conflict guidance, echoed across HBR's conflict work, favors higher-fidelity channels when the stakes rise. A five-minute call beats a twenty-message thread.
If the team can hear you, move. Public de-escalation still leaves residue. Private cool-down protects morale and keeps the conflict from becoming office lore.
Also separate task conflict from identity conflict in your own head. "We disagree on the roadmap sequence" can be sharp and still workable. "You do not respect me" is identity, and it needs a slower reopen. De-escalation often means delaying the identity layer until both of you have capacity for it.
After the temperature drops
De-escalation is not the finish. It only makes a real conversation possible.
Once both of you can think, build a quick shared picture: what happened, where you diverge, what decision is still open. Then decide and write it down. If you cool the room and never land the agreement, the same fight returns with more scar tissue.
Use a minimal close checklist before you leave the conversation:
- What did we decide.
- Who owns the next action.
- When do we check.
- What is explicitly not decided yet, so it does not sneak back in as sabotage.
If you cannot answer those four, you cooled the room but did not finish the work. Schedule the decision conversation while you are still calm. Do not rely on "we'll pick this up later" with no calendar hold. Later is where cofounder fights go to mutate.
For recurring loops rather than one hot hour, use structured cofounder conflict resolution or a Conflict Session that holds both accounts, one shared picture, and a short follow-through window. For the pattern where chase meets silence, see pursue-withdraw cofounder conflict. The broader context lives on cofounder conflict.
Practice the sequence on smaller frictions. De-escalation under a true company-threatening fight is hard if you have never used a pause signal over a weekly scheduling snag. Build the muscle when the stakes are low so it is available when they are not.
In the moment, your job is simple. Interrupt the spike. Protect decision quality. Come back once. Decide once. That is how you deescalate cofounder fight energy without pretending the issue disappeared.
