How does a leadership team prevent the sophomore slump in year two of running on EOS when the tools start feeling routine and complacency creeps in?

Question

Tyler Smith · Accepted Answer

In year one of an EOS implementation, enthusiasm is high. Setting Rocks, running weekly Level 10 Meetings, and cleaning up the Accountability Chart feel transformative because the business was previously chaotic. By year two, however, the novelty wears off. Tools that once felt revolutionary now feel like standard administrative chores. This is the sophomore slump, and if ignored, it quietly degrades operational rigor.

Complacency shows up in predictable ways:
- Rocks become routine to-do list tasks rather than needle-moving strategic milestones.
- Scorecard numbers stay consistently green because targets were set comfortably low to avoid uncomfortable conversations.
- The Issues List fills up with minor operational complaints instead of tackling massive, structural bottlenecks.

To destroy complacency in year two, the owner and Integrator must raise the standard of performance.

First, audit your Rocks strictly. If an executive completes ninety percent of their Rocks every quarter without breaking a sweat, the Rocks are too small. Rocks must stretch the leadership team and force structural improvement, not just reward daily operational upkeep.

Second, reset your Scorecard measurables. Look at your 3-Year Picture and 1-Year Plan on the V/TO. Increase target thresholds so that maintaining the status quo triggers an off-track flag. If your business is growing twenty percent annually, your Scorecard metrics must reflect leading indicators for that growth.

Third, demand tougher issues during IDS. Push past surface-level department squabbles and force the team to confront difficult questions: customer churn, underperforming sales channels, legacy software debt, or leadership gaps. EOS is not a checklist you complete; it is an operating system that requires continuous sharpening.