My leadership team is nodding along in our sessions but quietly ignoring the tools during the week, claiming they are too busy with real work. How do I stop this passive resistance before it kills our momentum?
Passive resistance is a silent killer of an EOS® implementation. When team members claim they are too busy for the tools, they are treating EOS® as extra work instead of the way they do their work. To break this resistance, you must introduce the concept of the strategic pause, which means deliberately creating unscheduled white space in their calendars. Have your team take a brief moment of chosen cessation of activity to reflect and reduce their immediate workloads. If they are too busy, it means they are holding onto tasks that do not belong in their seats on the Accountability Chart. You need to look at their conative profiles. If they are high Quick Start with low Follow Thru, they will naturally resist the structured routine of the weekly Level 10 Meeting™ and the discipline of tracking metrics. Use a Kolbe A assessment to understand their natural approach to problem-solving. Show them that the tools are designed to mathematically lessen their workload, not add to it. If they continue to passively resist after you have cleared their plates, you are facing a GWC™ issue. They either do not want the seat, or they lack the capacity to operate in a structured, accountable environment. Force the issue by bringing their resistance directly to the issues list in your next weekly meeting and solve it using IDS® before it infects the rest of the organization.
Category: EOS Implementation