What to do when a cofounder keeps overstepping their role

A cofounder overstepping their role is usually a decision-rights problem. Your titles say who does what in general. Nobody wrote down who makes the final call in each area, so the more assertive founder fills the gap. The fix is a short written map of who owns which decisions, agreed by both of you.

What does overstepping look like?

It looks like redone work more than open conflict. A hire you made gets re-interviewed. A pricing call gets reversed after a client meeting you were not in. Copy you approved gets rewritten without a word to you.

Watch for four signs:

• Constant second-guessing. Every call in your area gets a "did you think about" or a request to loop them in, even on calls that were meant to be yours.
• Quiet redos. A decision gets made, then remade, and nobody tells the original owner it did not stick.
• You start pre-clearing everything. This is the sign the damage is already done. You run routine calls past your co-founder just to avoid the redo.
• It only goes one way. One founder's area gets this treatment and the other's does not. That tells you where the gap in your setup sits.

This is narrower than a general cofounder power imbalance. Overstepping is about who has the last word inside one area of the business.

Why does it happen when you both mean well?

Because most teams settle titles and never settle decision rights underneath them. "CTO" tells you someone runs technology. It does not tell you whether the CTO can ship a roadmap change the CEO dislikes, or whether a junior hire needs a second signature.

Without that detail, every unclear call becomes a live negotiation. Whoever cares more that week, or worries more about a bad outcome, wins. As Unicorn Labs puts it, "equal equity does not mean equal authority." For the wider method of setting decision rights, read how cofounders should make decisions.

Why does it cause resentment?

Being redone sends a message your co-founder rarely means to send: your judgment in your own area cannot stand alone. Repeat it often enough and the message lands whatever the intent.

The owner then reacts in one of two ways. They push back on every case, which reads as defensive and brings more oversight. Or they pull back and stop putting full effort into an area they no longer feel they own. Their work gets worse, which seems to prove the oversight was needed. Both roads end with one founder running everything and the other checked out.

How do you fix it?

Write a decision map together. Skip the "you need to back off" talk, because a character correction invites a defence.

1. List your areas. Product, sales, hiring, pricing, finance, fundraising, vendors.
2. Name one owner per area. Unicorn Labs' rule is simple: "every cell gets exactly one owner."
3. Split solo calls from shared ones. Hiring below a set level might be the owner's alone. A senior hire needs both of you.
4. Agree the tie-break. Say what happens when you disagree inside someone's area.
5. Put it where you both see it. A map that lives in memory drifts back to vague within months.

The map gives the helpful founder somewhere to put the urge to help: an open question before the decision, instead of edits after it. And it gives the owner something to point to that is not personal: "we agreed this one is mine."

A Founders Align Blueprint holds this: one shared document of who owns what and how you decide, which you both sign and update as the company changes.

How do you raise it without a blame fight?

Name the pattern and its effect. "Decisions in my area keep getting redone, and it is slowing us down and making me unsure I own this" is a fact you can both look at. "You don't trust me" is an accusation your co-founder has to defend against.

Then move straight to drafting the map. A boundary you wrote together is far easier to keep than one declared mid-argument.

If you are not sure where the gaps are, the cofounder alignment check is a quick way to see where your answers differ. If drafting the map turns into its own argument, a Conflict Session lets you each write your side alone, read one summary built from both, and agree what changes. For the wider picture, see our cofounder conflict resolution guide.