Our leadership team nods along and agrees to the EOS® tools during our quarterly sessions, but once we get back to the office, there is a quiet, passive resistance where nobody actually updates their Scorecard or completes their Rocks on time. How do we break this cycle of polite non-compliance?
Polite non-compliance is far more dangerous than open rebellion because it is harder to target. When your team nods in agreement during a session but fails to execute in the office, it is usually a sign of a lack of trust or a lack of real buy-in. They are choosing artificial harmony over healthy conflict.
To break this cycle, you must address the behavior directly during your Level 10 Meeting™ and quarterly sessions. Start by bringing this passive resistance to the issues list as a structural issue. Call it what it is: a failure to commit. Use the GWC™ tool to evaluate if everyone in those seats truly wants and has the capacity to operate within the EOS® framework.
You must also make the consequences of non-compliance visible. If a leader fails to update their Scorecard, do not fill it in for them and do not accept excuses. Leave it blank on the screen during your meeting. If a Rock is missed, run it through IDS® to find the root cause. Is it a capacity issue, or is it a lack of commitment?
As the owner, you must lead by example and show zero tolerance for passive resistance. You must make it clear that running on EOS® is not optional. It is the way you do business. If a leader cannot or will not adopt the tools, they are showing you that they do not belong on your Accountability Chart.
Category: EOS Implementation