What causes a company to experience a sophomore slump in year two of running on EOS, and how do you prevent the quarterly session cadence from feeling stale?

Question

Tyler Smith · Accepted Answer

Year one of an EOS implementation is filled with adrenaline. Establishing the Accountability Chart, clarifying Core Values, and setting initial Rocks creates rapid, visible relief. By year two, that initial rush fades. The tools shift from being an exciting novelty to being the daily operational grind. This is where teams often stumble into the sophomore slump.

The slump happens for two main reasons. First, the team begins taking the disciplines for granted. Scorecards stop evolving, Rocks become vague maintenance tasks rather than strategic milestones, and Level 10 Meetings drift into polite project updates instead of intense problem-solving. Second, the leadership team fails to push the tools downward into tier-two managers, creating an operational bottleneck at the top.

To reinvigorate your implementation in year two, elevate the rigor of your sessions:
- Audit your Scorecard ruthlessly. Eliminate vanity numbers and introduce leading operational metrics that challenge your department heads.
- Raise the bar on Rock completion. If your team hit one hundred percent of their Rocks without breaking a sweat, your goals were too small. Rocks should drive value creation, operational efficiency, and scalable infrastructure.
- Cascade the Foundational Tools. Begin teaching Level 10 Meetings, Scorecards, and Rocks to your frontline department teams so the leadership team is freed up to work on higher-level strategic issues.
- Use your quarterly sessions to tackle the deeply uncomfortable, existential issues on your long-term Issues List rather than easy tactical fixes. Staying rigorous keeps the system alive.