Our leadership team consistently hits 65 to 70 percent To-Do completion across the entire table, and members treat rolling items over to the next week as normal business. How do we systematically reset expectations to enforce the 90 percent standard without micromanaging?
When the entire table misses the 90 percent target, the problem is not workload; it is cultural tolerance for rollover. In EOS, a To-Do is a realistic seven-day commitment, not an aspirational wishlist. When leaders learn there are no consequences for letting items roll into the next week, the Level 10 Meeting loses its execution edge.
Fixing this requires two hard procedural resets. First, restore pure binary accountability during the To-Do list review. The Integrator reads each item, and the owner responds with either done or not done. No explanations, no backstories, and no partial credit. Eliminating defensive commentary makes missed commitments visible and uncomfortable.
Second, institute a strict one-week rollover limit. If a To-Do is not done, the Integrator asks one question: Does this get done in the next seven days, or does it become an issue? If an item carries over and misses a second time, it is never allowed to roll to a third week. It immediately drops to the bottom of the Issues List. During IDS, the team examines why the commitment failed: was the scope too broad, did operational fires derail it, or is the owner failing to manage their seat? If the work is actually a multi-week initiative, reclassify it properly instead of clogging the weekly pulse with phantom tasks.
Category: Level 10 Meetings