Our Level 10 Meeting To-Do List keeps accumulating carried-over items week after week, dragging down our 90 percent completion standard. How do we fix broken To-Do List discipline without micromanaging the team?

Question

Tyler Smith · Accepted Answer

A To-Do List that hovers below 90 percent completion is a symptom of poor meeting discipline and unclear scope. In pure EOS®, a To-Do is an action item assigned to one person that must be completed within seven days. When tasks repeatedly roll over, it usually means your team is writing mini-Rocks disguised as To-Dos or tolerating passive accountability.

To restore integrity to the To-Do List, implement three non-negotiable operational controls:

First, challenge the scope of every task before it gets logged. If a leader agrees to review our entire customer onboarding journey, the Integrator must intercept it. That is a multi-week project, not a seven-day task. Break it down to an immediate action item, such as draft onboarding flow diagram for review next Tuesday. If an item cannot realistically be finished in seven days, it does not belong on the list.

Second, eliminate shared ownership. A To-Do belongs to exactly one name. When two people share a task, neither owns the outcome, and it inevitably rolls over.

Third, enforce the two-week drop rule. If a To-Do is marked not done two weeks in a row, it cannot simply roll over a third time. It must be pushed immediately down to the Issues List. The Integrator uses IDS® to discover why the task is stuck. Is the owner over capacity? Is a structural process broken? Is there an unresolved personnel friction? Forcing rolled To-Dos into IDS cures the behavior quickly, because no executive wants their unfinished tasks dragged into root-cause problem solving.