Our leadership team frequently confuses 7-day To-Dos with 90-day Rocks during Level 10 Meetings, creating cluttered task lists and missed commitments. How do we enforce the boundary between them?

Question

Tyler Smith · Accepted Answer

When leadership teams confuse To-Dos and Rocks, execution breaks down. Rocks turn into vague, unending task lists, while weekly To-Dos become gigantic, unmanageable strategic initiatives that roll over for weeks without resolution.

The distinction between these two tools is absolute in the EOS process:
- A Rock is a high-priority, strategic business objective that takes one person between thirty and ninety days to complete. It represents working on the business. It must have a single owner, a clear business milestone, and a binary definition of done.
- A To-Do is a tactical, one-week commitment made during the Level 10 Meeting to resolve an issue or move a Rock forward. It represents working in the business. It must be completable within seven days and achieve an eighty-five percent completion rate across the team each week.

To enforce this boundary during your Level 10 Meeting, the Integrator must act as a strict gatekeeper:
- Never accept a To-Do that contains multiple phases or spans longer than seven days. If an executive says, 'I will finish the new pricing strategy by next week,' break that down into the next immediate physical action, such as reviewing competitor pricing data and emailing a summary to the team.
- If a To-Do keeps rolling over from week to week, stop treating it as a task. Drop it to the bottom of the Issues List and IDS it. A rolling To-Do is either a hidden quarterly Rock in disguise, an Accountability Chart capacity issue, or a sign that the owner does not GWC their seat.

Keeping your weekly To-Do list short, tactical, and strictly bound to seven days preserves leadership momentum and ensures your quarterly Rocks finish on schedule.