We are in the first 90 days of our EOS implementation, and our leadership team feels overwhelmed by the sudden addition of weekly Scorecards, Rocks, and meeting rhythms on top of their day jobs. How do we survive this initial transition without dropping the ball on our daily operations?

Question

Tyler Smith · Accepted Answer

The first 90 days of running on EOS are always the hardest because you are installing a new operating system while still driving the car. It is completely normal for your leadership team to feel a temporary operational dip as they adjust to the new discipline. To survive this phase without burning out, you must ruthlessly prioritize. Do not try to solve every issue or track fifty numbers on your Scorecard immediately. Keep your initial Scorecard down to five to fifteen high-level, predictive numbers. Similarly, when setting your first round of Rocks, lean toward fewer, less complex goals. It is far better to achieve three simple Rocks than to fail at five ambitious ones. Remember that the goal of the first quarter is not perfection; it is building the muscle of accountability. Trust the weekly Level 10 Meeting to keep you aligned. If a team member is falling behind, use the IDS process to help them re-prioritize their week instead of letting them quietly drown. An EOS Implementer can help keep you focused on the fundamentals and prevent you from overcomplicating the tools. Once these habits become second nature, the feeling of overwhelm will fade, and you will begin to see the true power of the system.