We have a leader who routinely keeps the same critical weekly To-Do on our list for three or four weeks in a row, always claiming they made progress but just need a few more days, which keeps us from resolving the connected issue. How do we handle these lingering action items without letting them become permanent fixtures?

Question

Tyler Smith · Accepted Answer

A weekly To-Do in a Level 10 Meeting is a firm, seven-day commitment. It is either done or it is not done. There is no middle ground, and there is no such thing as partial credit. When a leader rolls a To-Do over to the next week with the excuse of progress, they are leaking accountability and stalling the momentum of the entire team.

This behavior often happens because the leader does not want to admit failure, or because the To-Do was defined too vaguely in the first place. To stop this pattern, the Integrator must enforce a strict rule: if a To-Do is not completed within seven days, it is officially late. If it is late for a second consecutive week, it must immediately be dropped down to the Issues List as an active issue to be solved during IDS.

During IDS, the team must identify the root cause of why this item is stalled. Is the leader overloaded? Is the task actually a multi-week Rock disguised as a simple To-Do? Or is there a deeper capability or delegation issue? Moving a late To-Do to the Issues List removes the personal friction and focuses the team on solving the bottleneck rather than politely accepting weekly excuses.