Our leadership team claims they are on board with EOS®, but we are experiencing a passive-aggressive resistance where they nod in our quarterly sessions but quietly ignore the tools in their daily operations. How do we break through this silent veto and force our leaders to actually live the system?

Question

Tyler Smith · Accepted Answer

Passive resistance is more dangerous than active rebellion. When a leader nods in agreement during a session but returns to their department and runs things the old way, they are exercising a silent veto. This behavior destroys accountability and signals to the rest of the organization that your operational standards are optional.

To break the silent veto, you must make the tools the only path to survival. Stop accepting off-line status updates and manual reports. If a metric is not on the weekly Scorecard, it does not exist. If an issue is not raised and solved in the weekly Level 10 Meeting, it does not get addressed. You must force all departmental communication through the EOS framework.

Next, use the Accountability Chart to address the behavior directly. Review the roles of each seat and ask whether the leader is truly executing their functions. A key part of GWC is having the capacity and the desire to run the operating system. If a leader refuses to use the tools, they do not GWC their seat.

Call out the artificial harmony in your next session. Use the IDS process to put their passive resistance on the list as a structural issue. Force them to state their objections openly. If they cannot or will not align with the system, you have a people issue that must be resolved. A healthy leadership team requires absolute alignment, not polite non-compliance.