One of our most senior leaders is showing quiet resistance to EOS, attending our Level 10 Meetings and filling out their Scorecard but refusing to engage in IDS or voice real issues. How should the Integrator confront this passive pushback before it infects the room?
Passive resistance from a senior leader is far more toxic to an EOS® rollout than loud disagreement. Loud disagreement can be brought to the table and solved through IDS®. Malicious compliance, where an executive mechanically updates their Scorecard and sits silently through Level 10 Meetings, signals to the rest of the company that the system is optional.
The Integrator must address this directly in a private, one-on-one conversation outside the Level 10 Meeting™. Do not wait for quarterly planning. Address the behavior within forty-eight hours of observing the pattern.
Ground the conversation in Core Values and the Accountability Chart. Be completely specific. Point out the exact observable behaviors: you submitted your measurables, but you have not entered an issue on the Issues List in four weeks, and during IDS you declined to offer an opinion on critical company decisions. Ask them directly what they are thinking: Do you believe this system is ineffective, or do you have reservations about the direction of the company that you are holding back?
Make it clear that passive participation is not acceptable on the leadership team. Every seat at that table requires complete engagement, open vulnerability, and active conflict resolution.
If the leader expresses valid critique about how the tools are being facilitated, adjust the facilitation. But if the leader simply rejects structured accountability and transparent measurables, you have a People Analyzer® issue. They do not fit the culture or they lack the capacity to operate in an open, accountable environment. You must either resolve their commitment or transition them out of the seat.
Category: EOS Implementation