One of our critical division heads is quietly resisting our EOS® implementation by leaving their Scorecard metrics blank and missing Rock milestones, claiming their department is too complex for simple numbers. How do we handle this pushback without causing a major operational rift?

Question

Tyler Smith · Accepted Answer

When a key leader resists the EOS® tools by leaving their Scorecard blank, they are usually hiding behind complexity to avoid accountability. To break this resistance, you must stop treating the tools as optional administrative tasks. The Scorecard is not a report card; it is an early warning system. Start by having a candid, one-on-one conversation outside your weekly meeting. Ask them to define what winning looks like in their seat using only three numbers. Do not let them argue that their work is too complex or creative to measure. Every repeatable activity has a metric. If they can manage the department, they must have a way of knowing it is healthy. If they refuse to provide these metrics, they are telling you they do not want to be accountable. This is a GWC™ issue, meaning they either do not get it, want it, or have the capacity to do it. You must resolve this quickly. If you let one division head opt out of the system, you give the rest of the team permission to ignore it, which will stall your entire implementation.