One of our co-founders is passively resisting the EOS® tools, showing up to meetings unprepared and rolling their eyes. How do we address this high-level resistance without creating a massive rift in our partnership?

Question

Tyler Smith · Accepted Answer

Passive resistance from a co-founder is poison to an EOS® rollout. When a leader signals that the operating system is optional, the rest of the organization immediately stops taking it seriously. You must address this behavior directly and privately, framing the conversation around the future value of the business rather than personal frustration.

Start by pointing out the specific behaviors: the missed preparation, the eye-rolling, and the late arrivals. Ask them directly if they are still committed to the vision of building a scalable company that can operate without either of you. Remind them that a clean, institutionalized operating system is the single greatest driver of exit value. If the business is dependent on the personal whims of the founders, its market value drops significantly.

Use the GWC™ framework to evaluate their alignment. Do they want their current seat? Do they understand it? Do they have the capacity to lead it using our chosen operating system? If they genuinely want the business to scale, they must agree to model the behavior they expect from the rest of the team.

If the resistance persists, it usually indicates a deeper structural issue: one partner has outgrown their seat, or you are no longer aligned on the ultimate exit plan. In these scenarios, having a neutral Professional EOS Implementer® in the room is vital. An implementer can facilitate these tough conversations objectively, keeping the focus entirely on what is best for the organization rather than personal egos.