When leadership team members realize a To-Do cannot be completed within seven days, they sometimes delete it or ask to remove it from the list during Conclude. What is the standard protocol for handling stalled or obsolete To-Dos?

Question

Tyler Smith · Accepted Answer

Allowing leaders to silently delete an unfinished To-Do destroys team accountability. If people can wipe away incomplete commitments without team review, your 90 percent To-Do completion metric becomes meaningless fiction.

In a Level 10 Meeting™, once a To-Do is written and assigned during Conclude, it stays on the list until the entire team reviews it during the following week's meeting pulse. No one is permitted to erase or rewrite a To-Do mid-week in your tracking software.

When you reach the To-Do review, handle stalled or obsolete items with this exact three-step protocol:

First, mark it as not done. Even if the task became obsolete twenty-four hours after the last meeting because a client cancelled or priorities shifted, it must be recorded as incomplete. That keeps your metric honest and reflects reality.

Second, determine whether the item is truly obsolete or simply delayed. If business conditions changed and the task is no longer necessary, the owner states the reason in five seconds, and the team agrees to remove it.

Third, if the item is still necessary but cannot be executed in the coming seven days, do not let it sit on the To-Do list accumulating roll-overs. Move the item immediately to the Issues List.

Dropping stalled tasks to the Issues List forces the team to confront why it stalled. Was the owner overcommitted? Was the task actually a multi-step project? Or did an operational barrier prevent execution?

Solve the root cause in IDS® rather than letting dropped commitments vanish into thin air. Integrity around small commitments is what creates predictable execution across the entire business.