Our team consistently misses the ninety percent weekly To-Do completion standard in our Level 10 Meeting, carrying tasks across multiple weeks. How do we fix this execution leak?

Question

Tyler Smith · Accepted Answer

A chronic failure to hit the ninety percent To-Do completion standard is an indicator of poor task scoping during IDS or a leadership team that tolerates broken commitments. In pure EOS, a To-Do is a specific, single-owner action item that can and must be completed within seven days. If a task routinely rolls over to the next week, your execution cadence is broken.

First, inspect how To-Dos are written during the Solve phase of IDS. Leadership teams often write Rocks disguised as To-Dos. If a task requires thirty hours of work, extensive cross-departmental coordination, or vendor quotes, it cannot be completed in seven days. Break the assignment down to the immediate next step. Instead of write new employee handbook, assign create outline for handbook section one.

Second, eliminate ambiguous ownership. A To-Do must belong to exactly one name on the Accountability Chart. When two people share a task, nobody owns it, and it inevitably rolls over.

Third, enforce strict peer accountability during the To-Do review. The review must be binary: done or not done. No explanations, no storytelling, and no excuses. If a leader repeatedly reports not done, drop that pattern directly to the bottom of the Issues List as a seat, capacity, or prioritization issue to be IDS'd at the end of the meeting.

When leaders realize that failing to complete a To-Do triggers an immediate operational conversation about their capacity, completion rates will rapidly climb above ninety percent.