We are ready to cascade EOS to our departmental teams but we are worried that introducing more weekly Level 10 Meetings and department-level Rocks will create meeting fatigue and drag our people away from their core work. How do we roll this out efficiently?

Question

Tyler Smith · Accepted Answer

Cascading EOS to your departments should never create administrative bloat or meeting fatigue. If your team feels overwhelmed by the rollout, it is usually because you are adding new meetings on top of your existing, unstructured communication channels instead of replacing them.

The weekly Level 10 Meeting is designed to replace all of the random, ad-hoc meetings, status updates, and long email chains that currently disrupt your team's focus. When you introduce the department-level Level 10 Meeting, you must cancel all other operational alignment meetings. Your team will quickly realize that ninety minutes of structured problem-solving saves them hours of fragmented coordination throughout the week.

When cascading Rocks, keep the focus tight. Departmental employees should not have three to five complex Rocks. Start by assigning just one clear, highly impactful Rock to each department head and key team member. Ensure this priority is directly aligned with the leadership team's quarterly Rocks and the overall V/TO.

By keeping the structure lean and teaching your managers the exact same meeting discipline used by the leadership team, you build a consistent operating rhythm. This alignment ensures that everyone is pulling in the same direction without wasting valuable time in unnecessary or redundant meetings.