My co-founder and I have brought in a new head of operations, but my co-founder constantly bypasses this new leader to give directions directly to frontline staff, undermining their authority. How do I address this co-founder boundary issue without starting an civil war?

Question

Tyler Smith · Accepted Answer

Bypassing your new operations leader and communicating directly with frontline staff is a structural violation that completely undermines your Accountability Chart. When a co-founder ignores reporting lines, they signal to the entire organization that the new leader does not possess real authority. This behavior creates confusion, destroys the trust of your new hire, and stalls your operational scaling.

To resolve this without causing a civil war, you must address the issue as a structural problem rather than a personal conflict. You and your co founder must ground your conversation in the rules of your EOS operating system.

Use this process to realign your co founder:

- Schedule a private meeting with your co founder outside of your standard Level 10 Meeting to review the Accountability Chart.
- Remind them that every seat on the chart must have absolute authority over its designated area of responsibility, and that bypassing a leader violates the core rule of the system.
- Establish a strict communication boundary where all strategic and operational directives for the operations department must go directly through the head of operations, never around them.
- Agree to call each other out immediately and privately whenever either of you violates this boundary.

If your co founder struggles to stay out of the daily details, help them identify why they are reaching past the leader. Often, it is because they have not yet built trust with the new hire or are struggling to let go of control. By enforcing the Accountability Chart, you protect your leadership structure and show your organization that you are serious about building a scalable business that can eventually run without you.