Two key leaders on our team openly roll their eyes at EOS terminology like Rocks and IDS, dismissing them as corporate buzzwords and dragging their feet. How do we handle this passive resistance so it does not undermine our rollout?

Question

Tyler Smith · Accepted Answer

Passive resistance usually stems from one of two causes: fear of exposure or past trauma from bad corporate management fads. Experienced leaders have often endured multiple consultant programs that demanded heavy administrative paperwork and delivered zero operational relief. They assume EOS is another academic exercise designed to micromanage them.

Address the resistance head-on during your next session or one-on-one conversation. Strip away the jargon. Rocks are simply ninety-day business priorities that matter more than everyday firefighting. The Level 10 Meeting is just ninety minutes of structured time to kill your recurring problems so you do not have to talk about them all week. Explain that EOS does not add work to their plates. It organizes the work they are already doing and eliminates the operational chaos they complain about daily.

Then hold the standard firmly. Give them space to express their skepticism, but make adoption non-negotiable. If a leader refuses to show up prepared for the Level 10 Meeting, misses To-Dos repeatedly, or ignores the Scorecard, run them through the People Analyzer against your Core Values. If they cannot or will not demonstrate GWC for their seat under a transparent operating model, you are looking at a culture fit problem, not a tooling problem. The system requires five to seven leaders pulling in the exact same direction. You cannot allow cynical holdouts to hold the rest of the company hostage.