We are entering our second full year running on EOS, and our leadership team is showing signs of tool fatigue and wanting to loosen the disciplines. How do we keep the system sharp and avoid the second-year slump?

Question

Tyler Smith · Accepted Answer

The second-year slump happens when the initial excitement of implementing EOS fades and the disciplines become routine. In year one, the tools deliver dramatic transformations: chaos drops, communication clears up, and bad fits are removed. In year two, the disciplines feel like work, and leadership teams become vulnerable to boredom.

When teams get bored, they start cutting corners. Level 10 Meetings start late. Scorecards carry numbers that never change. Rocks are written vaguely without milestones. The team begins treating EOS as a chore rather than the operating system driving their enterprise value.

To combat tool fatigue, raise the standard of performance. Your first year was about installing habits. Your second year is about optimizing results. Use your Scorecard to introduce more predictive, forward-looking measurables. Challenge your leadership team to set Rocks that do not just maintain the business, but actively eliminate chronic operational waste and build scalable systems.

Second, look closely at your meeting ratings. If your team is rating Level 10 Meetings a seven or eight without explaining why, demand ruthless honesty. Use IDS to solve the meeting dynamic itself. Ask: Are we bringing our toughest, most terrifying issues to this table, or are we playing small?

Finally, reconnect the team to the long-term vision. Revisit your 10-Year Target and your exit readiness goals. Remind everyone that consistent, boring execution is precisely what builds durable enterprise value. EOS is not a project with an end date; it is how great companies operate every single day.