To start a cofounder conflict session without making it worse, name one topic, propose a calm time, and write your side alone before you share anything. Open with what happened, not a verdict on your co-founder. Ambushes, labels about character and Slack threads raise the temperature before the real work starts.
What is a Conflict Session?
A structured way to work through one disagreement. In a Conflict Session, each of you writes your side alone, which takes about forty minutes. You then read one summary built from both sides. It opens for both of you at the same moment, and it is built from your own answers, which you edit before anything is shared. You agree what changes together in one form, then check back on day 7 and day 14.
That matches Embroker's advice to take co-founder conflict somewhere private and deal with it directly, rather than in front of the team or by hoping it fades.
When should you start one?
At a dull, protected time. Avoid:
- the day of a missed deadline
- late at night, when you are both drained
- the fifteen minutes before a board call
- any public channel where either of you plays to an audience
Outlander VC recommends regular co-founder check-ins so issues come up before they sour things. A Conflict Session is for when that has not happened and the issue is already sharp.
How do you invite your cofounder?
Briefly. Name the topic, explain the process and propose a time.
I want us to work through [one-line topic] properly. We each write our side alone, then read one summary of both and agree what changes. Can you do your part by [day]? If that does not work, suggest another day.
Do not send "we need to talk" with no topic, a message that already argues your case, a copy to an investor as pressure, or a diagnosis of their personality.
How should you prepare your side?
Separate facts from your reading of them. Outlander's method: one column for what a camera would have caught, another for the story you built on it. Lead with the first column.
Then pick one ground rule: no interruptions, describe behaviour only, or either of you can pause with a named return time. Reboot coaches founders to name conflicts directly and to listen without drafting a reply mid-sentence. That habit starts in how you write your side.
Which opening mistakes make it worse?
| Mistake | Why it backfires | Do this instead |
|---|---|---|
| Ambush meeting | Triggers defence | Invite with a topic and a time |
| Opening with character | Makes the person the problem | Start with one observable event |
| Bringing the whole history | Floods the room | One disagreement per session |
| Threatening to leave in minute one | Kills safety | Save exit talk for after a real attempt |
| Running it in Slack | Half attention, permanent record | Book a focused block |
Embroker also warns against both giving up your position and forcing a decision through. Do not demand a full apology as the price of starting. What repairs trust is the change you agree and then see happen by day 14.
If contempt or total withdrawal is already the norm, read when to bring in a cofounder mediator first. For the wider process, see our cofounder conflict resolution guide.
Frequently asked questions
- How do you start a cofounder conflict session without making it worse?
- Invite your co-founder with one named topic and a proposed time, never as an ambush. Write your own side privately before anything is shared. Open with what happened, not with a judgement of their character. A predictable, structured start keeps the temperature down, while surprise and public settings push it up.
- Should I tell my cofounder I already started a conflict session alone?
- Yes. In a Conflict Session each of you writes your side alone, so say so when you invite them. Being open about the process matters more than perfect timing. Preparation that stays hidden and then appears as a finished case feels like a power move, even when you meant it as homework.
- What if my cofounder refuses to join a conflict session?
- You cannot force a joint process. Finish thinking through your own side, then send one calm second invite with the topic and a proposed time in writing. Decide what you will do if the answer stays no. A repeated refusal tells you something about the partnership in itself.
- Is Slack a good place to start a hard conversation with a cofounder?
- Use Slack only to agree a time. Do not argue the conflict in a thread. Hard conversations need a protected block, a private setting and both people paying full attention. A thread gives you half attention and a permanent written record of the worst moment, which neither of you needs.
