During the first 90 days of rolling out EOS, our leadership team complains that running Level 10 Meetings and updating Scorecards feels like extra administrative overhead on top of their real jobs. How do we get them through this initial hump?

Question

Tyler Smith · Accepted Answer

This complaint is completely normal during the first 90 days of an EOS implementation. It happens because your leaders are attempting to run the new EOS disciplines on top of their old, chaotic operating habits rather than replacing them. They are still holding ad-hoc phone calls, sending frantic weekend emails, and attending unstructured update meetings while also showing up to the Level 10 Meeting. That creates legitimate cognitive overload.

As the owner or Integrator, you must make it clear that EOS is not an additive project. It is the new operating system that eliminates duplicate work. To break through the first 90-day hump, take three decisive actions:
- First, aggressively cancel redundant recurring meetings. If department heads meet weekly for updates, eliminate that meeting. All status reporting moves to the Scorecard and Rock review, and all problems move to the Level 10 Meeting Issues List.
- Second, protect the Scorecard standard. Do not let leaders spend hours formatting elaborate slide decks or spreadsheets. A healthy Scorecard requires five minutes to update weekly numbers before the meeting begins. If pulling the data takes hours, the metric is too complex or your reporting process needs immediate simplification.
- Third, push all spontaneous operational emergencies into the next Level 10 Meeting agenda unless the building is literally on fire.

When team members realize that ninety minutes on Tuesday morning genuinely protects the other thirty-nine hours of their week from constant interruptions, the perception shifts. The first 90 days require rigid boundary enforcement. You must pull the team through the discomfort until the tools prove their efficiency.