Our leadership team is not actively arguing against the operating system, but we are seeing passive compliance where they nod in the sessions and then completely ignore the tools in their day-to-day work. How do we break through this silent resistance?

Question

Tyler Smith · Accepted Answer

Passive compliance is far more dangerous than active resistance. Active resistance is vocal and can be addressed directly through the IDS® process. Silent compliance allows mediocrity to fester under a veneer of agreement.

To break through this behavior, you must make the use of the tools non-negotiable and highly visible. Start by bringing their day-to-day work directly into the weekly Level 10 Meeting™. If a leadership team member is nodding in agreement during quarterly planning but ignoring their Scorecard, call out the missing data immediately. A blank or outdated line on the Scorecard is an operational issue that must be dropped down to the IDS® section.

Do not let them off the hook with verbal updates. Force the issue by asking if they are truly on track with their numbers. If they cannot produce the data, it becomes a systemic problem.

You must also tie their quarterly performance reviews directly to their execution of the tools. Use the People Analyzer™ to evaluate whether they truly share your core value of accountability. If a leader consistently fails to run their department using the shared operating system, they are showing that they do not GWC™ their seat.

Make it clear that using the system is not a voluntary option. It is the specific way your company conducts business. When silent objectors realize that their lack of engagement is being tracked weekly on the Scorecard and analyzed during quarterly reviews, they will either step up or opt out.