Our leadership team nods along in our sessions, but as soon as we return to the office, they quietly ignore the EOS® tools and default to their old spreadsheets and ad-hoc communication. How do I address this passive-aggressive resistance to the operating system without turning it into a personal conflict?

Question

Tyler Smith · Accepted Answer

Passive resistance occurs when team members do not feel safe voicing their concerns during your sessions. If they nod in agreement but return to their old habits, they have not truly committed. They are just trying to get through the meeting.

To solve this, you must first address the lack of healthy conflict on your team. At your next quarterly session, bring this issue directly to the table. State clearly that using the tools is not optional. It is the one way we run our business. Ask them directly what they dislike about the EOS® tools. Let them air their grievances.

Often, resistance stems from a fear of exposure. The weekly Scorecard and Accountability Chart make individual performance highly visible. If a leader is struggling, these tools will highlight their gaps.

As an owner, you must lead by example. If you allow workarounds, you validate their resistance. You must refuse to engage in conversations that do not follow the IDS® process. You must refuse to review numbers that are not on the weekly Scorecard.

Consider bringing in a Professional EOS Implementer® to facilitate these tough conversations. An outside guide can remain objective, call out passive resistance without triggering defensive reactions, and help your team build the necessary trust to fully commit to the system.