Certain action items on our Level 10 Meeting To-Do List keep getting rolled over week after week without getting completed or killed. What exact rule should we enforce when a To-Do survives past two weeks?

Question

Tyler Smith · Accepted Answer

A Level 10 Meeting To-Do is a seven-day commitment, period. It is not a project, a backlog item, or a wish list. By definition, 90 percent of To-Dos must drop off the list every single week as complete. When an item rolls over into week two, it is a warning sign. When it sits on the list for a third week, you have a process failure.

Enforce the two-week drop rule. If a To-Do is not completed after two consecutive weekly meetings, the team has only three options during the To-Do review:
- Mark it done because the owner finishes it before the meeting closes.
- Drop it entirely because if the business survived two weeks without it, the task was never truly vital.
- Push it directly to the Issues List for immediate IDS.

When a To-Do is pushed to the Issues List, the team must treat the failure to execute as the problem. Do not simply grant an extension. Ask the owner why the item did not get completed. Did they lack clear direction? Did they take on something that is actually a multi-step project requiring a Rock? Or did they say yes when their real operational capacity was already zero?

Allowing unfinished To-Dos to linger week after week destroys accountability and trains your leaders that commitments are optional. Clean execution requires absolute binary standards: it is either done in seven days, or the underlying roadblock gets solved in IDS.