Our weekly Level 10 Meeting produces dozens of minor To-Dos, and our leadership team spends so much time clearing tasks that they neglect their quarterly Rocks. How do we keep our To-Do list from cannibalizing Rock progress?

Question

Tyler Smith · Accepted Answer

A common operational breakdown occurs when leadership teams confuse weekly Level 10 Meeting To-Dos with personal daily task lists. If your weekly meeting generates twenty operational chores per person, leaders will spend their working hours grinding through low-value administrative items while their strategic quarterly Rocks stall out.

In pure EOS, a To-Do is strictly an action item created during IDS to resolve an identified issue. It is not a place to log routine daily responsibilities, ongoing job duties, or personal reminders. Every To-Do must be scoped so that it can be completed within seven to fourteen days.

To restore balance between weekly tasks and quarterly Rocks, enforce these rules:
- Never assign a To-Do that should properly be classified as an operational milestone for an existing Rock.
- Filter IDS solutions ruthlessly. Only create a To-Do if it fundamentally solves the issue or advances a permanent fix.
- Maintain a weekly To-Do completion standard of ninety percent or higher during the Level 10 Meeting review.
- If a To-Do remains incomplete for two consecutive weeks, drop it straight to the Issues List to determine why it is blocked.

Protect your leadership team by keeping the To-Do list lean and decisive. When weekly action items are kept to essential operational fixes, leaders retain the dedicated capacity required to drive their quarterly Rocks across the finish line.