tyler-smith.com · Questions & Answers

We implemented EOS but our leadership team seems to be running a dual system where they do their actual daily management in spreadsheets and only update the EOS tools right before our meetings. How do we stop this superficial compliance and get them to run the business through the tools?

This dual-system behavior is common when a leadership team views EOS® as an administrative overlay rather than the operating system itself. If your team is maintaining side spreadsheets and only updating their Scorecard or Rock progress five minutes before the Level 10 Meeting™, they are wasting time and missing the point. You must make the EOS® tools the single source of truth for your operations. Start by eliminating the side tracking. If a leader brings up a metric or progress update that is not on the Scorecard, stop the conversation and redirect them. If it matters enough to discuss, it must live on the Scorecard. The same goes for issues. If team members are resolving operational problems in side emails or private chats, push those issues into the IDS® portion of your weekly meeting. The Integrator must lead this transition by refusing to engage with data or issues that are not tracked inside the system. You also need to examine if your tools are designed correctly. If leaders prefer their old spreadsheets, it is often because your EOS® Scorecard metrics are too vague or do not accurately reflect weekly performance. Work with your team to refine the metrics so they provide real value. Once the tools actually make their jobs easier, the duplicate tracking will naturally fade. If passive resistance persists, it is a people issue, not a tool issue, and you must use the People Analyzer™ to evaluate their fit.

Category: EOS Implementation

← All questions