During the first 90 days between Focus Day and Vision Building 2, our managers feel overwhelmed trying to run daily operations while mastering the new EOS tools. What should leadership strip away to give the team breathing room so the implementation sticks?

Question

Tyler Smith · Accepted Answer

The first 90 days of an EOS implementation reveal every ounce of operational waste you have tolerated for years. When managers claim they are too overwhelmed by the EOS tools to run daily operations, the problem is not the tools. The tools take roughly two hours a week: ninety minutes for a Level 10 Meeting and thirty minutes updating the Scorecard and Rock tracking. The real issue is that your managers are still carrying legacy busywork that should have died on Focus Day.

To create immediate breathing room, execute an operational freeze on discretionary initiatives. Put all non-essential internal projects on ice. If an initiative does not directly map to a company Rock or protect critical client revenue, pause it until after Vision Building 2.

Second, eliminate redundant meetings. If a department head is running daily check-ins, ad-hoc syncs, and status updates, kill them all. The Level 10 Meeting replaces those fragmented conversations. Enforce the rule that operational updates happen exclusively on the weekly Scorecard and Rock review, freeing up three to five hours of calendar clutter per manager every week.

Third, audit the To-Do lists coming out of your weekly meetings. A healthy Level 10 Meeting generates seven-day commitments, not multi-week projects disguised as tasks. If a To-Do cannot be realistically executed in seven days alongside daily operations, break it down or drop it.

Protecting your team during the first 90 days requires ruthless subtraction. You cannot layer EOS disciplines on top of undisciplined chaos without breaking your people. Stop doing the low-value work so the core system can take root.