Our leadership team treats dropped To-Dos as harmless carryovers, letting unfinished seven-day action items roll over for two or three consecutive weeks with zero urgency. What is the exact protocol when a To-Do is not completed on time?

Question

Tyler Smith · Accepted Answer

Allowing unfinished To-Dos to roll over week after week is an operational poison that destroys executive accountability. A To-Do in a Level 10 Meeting™ is strictly defined as a binary, single-owner commitment designed to be completed within seven days. When completion hovers below 90 percent because tasks drag on, the team is tolerating soft commitments.

The Integrator must enforce a strict, unyielding protocol during the five-minute To-Do list review. When an item is read, the owner may only say done or not done. If the answer is not done, there are only three acceptable paths:

- Recommit once: If a sudden, unavoidable operational emergency caused the delay, the owner may recommit to finishing it within the next seven days, but this is allowed only once.
- Push to the Issues List: If the task stalled because of missing information, cross-departmental friction, or hidden complexity, it immediately drops to the Issues List for IDS®. The team must discover why it could not be resolved in seven days.
- Kill it: If the task sat unfinished for two weeks and nothing broke, the To-Do was probably meaningless administrative noise. Kill it off the list immediately.

Never allow an item to sit on the board for a third week without an IDS® conversation. If someone habitually drops To-Dos, it is no longer a task issue; it is a capacity or GWC™ problem that requires direct accountability.