A two week protocol after a cofounder conflict turns one hard conversation into a change you can both see. You write one or two specific requests, check in on day 7, and decide on day 14 whether they held. Agreeing in the room is easy. The protocol tests whether the agreement survives two weeks of real work.
Why two weeks?
Because open promises dissolve under sprint pressure, and two weeks is enough time for the trigger to come back. A missed handoff or a decision made alone will show up inside a fortnight, and the review cannot slip forever.
Outlander VC's field guide on co-founder conflict argues that conflict lives in the story you tell about the facts. The protocol turns that story into a test: the action happened or it did not.
What do you write down before you start?
One or two requests, each in a fixed shape. More than two usually fail because attention splits.
- Trigger. When X happens, a situation you can both name.
- Action. One specific behaviour, owned by one person.
- Window. For the next fourteen days.
- Proof. How you will know it happened: a message, a shared doc, a logged decision.
Good: "When pricing changes the roadmap, I will message you before I tell the team." Too vague: "I will include you more."
Embroker's guide to cofounder disputes argues for a written plan you can reopen when emotions run high. This sheet is that plan at its smallest. Add two rules for the fortnight: describe behaviour, never character, and either of you can call a pause if you name a time to come back.
Agree it in a booked meeting, not in Slack after a board call. Reboot's coaches put it plainly: name the conflict, use structure, and get help when you are too close to it. A Conflict Session gives that first conversation structure: you each write your side alone, read one summary built from both, agree what changes, and check back on day 7 and day 14.
What happens at the day-7 check?
You spend fifteen minutes on three questions:
- Did the action happen when the trigger came up?
- Was the request too vague or too heavy to keep?
- What one change would make next week cleaner?
Stick to what happened, not the motive you guessed. If one of you missed, tighten the wording. "Loop me in" becomes "send the draft before the customer call."
How do you decide on day 14?
Pick one of three outcomes. A mood does not count as a decision.
| Outcome | What it looks like | Next move |
|---|---|---|
| Hold | The trigger came up and the request was mostly kept | Make it a standing rule |
| Adjust | The will was there but the wording failed | Rewrite it and run one more fortnight |
| Fail | The pattern is unchanged or worse | Change the process, not the amount of talking |
Escalating means a coach or mediator, or an honest look at whether the partnership should continue. Repairing a broken cofounder partnership covers that longer path.
When is a two-week protocol the wrong tool?
When the real dispute is equity or roles. Embroker notes that chronic fighting often means roles were never defined, and then you need decision rights written down, not a fortnight of good behaviour. It is also wrong when it never ends. A protocol that keeps extending without a decision is avoidance with a calendar. After a hold, add a standing weekly slot for hard topics so the next friction comes up early. Our cofounder conflict resolution guide covers the rest of the process.
Frequently asked questions
- What is a two week protocol after a cofounder conflict?
- It is a short written experiment two co-founders run after a hard conversation. You agree one or two requests that anyone could see happen, keep them for fourteen days, and meet on day 7 and day 14 to check. It turns a vague truce into evidence about whether the behaviour actually changed.
- Why two weeks instead of a month?
- Two weeks is long enough for the trigger to come back under real workload, so you see whether the new behaviour holds. It is short enough that neither of you can push the review off or hide behind good intentions. Longer windows tend to drift, and shorter ones rarely give the old pattern time to appear.
- What if my cofounder breaks the agreement during the two weeks?
- Treat one miss as information, not a verdict. Raise it at the day-7 check, and if the request was too broad, rewrite it in more specific terms. Keep going. A pattern of misses by day 14 means this agreement failed, which tells you to change the process, not that the partnership is over.
- What happens when the two weeks end?
- You make a decision together. Keep the request as a standing rule if it held, rewrite it and run another fortnight if the wording failed, or escalate if nothing changed. Escalating can mean a coach, a mediator, or an honest conversation about whether the partnership should continue.
