tyler-smith.com · Questions & Answers

Our leadership team agrees with EOS® in theory, but they are constantly claiming they are too busy to fill out their scorecard metrics or update their Rocks before the meeting. How do we handle this "too busy to do EOS" excuse?

The "too busy" excuse is code for a lack of commitment or a misunderstanding of what EOS® actually is. EOS® is not extra work you do on top of your job. EOS® is how you do your job. When leadership team members treat the tools as administrative busywork, they are still operating in fire-fighting mode instead of running the business.

To break this resistance, you must stop treating the tools as optional homework. If a leader cannot find five minutes to update their Scorecard or Rock progress before a Level 10 Meeting™, it means they are working in the business rather than on it. As the Integrator, you must address this head-on during your Same-Page Meetings or in one-on-one conversations.

Use the GWC™ (Get It, Want It, Capacity to Do It) framework. Ask them directly if they have the capacity to manage their seat. Often, the resistance stems from a lack of delegation. They are holding onto tasks they should have delegated, leaving them overwhelmed. Help them use the Delegate and Elevate tool to clear their plate.

If they still refuse to adopt the tools consistently, you have a People Component issue. A leader who will not run on the company operating system is actively undermining the leadership team's alignment. You must decide whether they are the right person in the right seat.

Category: EOS Implementation

← All questions