Our team's weekly To-Do completion rate has slipped below ninety percent because everyone is writing vague, multi-step projects as single weekly tasks instead of biting off true seven-day deliverables. How do we fix our To-Do definition process during the Level 10 Meeting™ to restore accountability?

Question

Tyler Smith · Accepted Answer

To-Dos are seven-day action items. When your weekly completion rate drops because people are writing multi-step projects as single tasks, you are failing at the definition stage. A To-Do must be binary, bite-sized, and realistic to finish before the next meeting pulse.

To fix this, the facilitator must enforce strict rules during the wrap-up and IDS portion of your Level 10 Meeting. First, stop accepting vague verbs like analyze, coordinate, or look into. These are not actions, they are thoughts. Replace them with specific, measurable deliverables. Use verbs like draft, call, send, or decide.

Second, verify the scope of every To-Do before the scribe writes it down. The facilitator should ask the owner if they can realistically complete this specific task within seven days alongside their daily operational responsibilities. If the answer is no, or if it depends on someone else, break the task down into a smaller milestone. For example, instead of write new training manual, the To-Do should be draft outline of chapter one.

Third, hold a hard line during the To-Do review. If a task carries over, do not let the owner explain why it was too big. If they agreed to it, they owned it. The lesson is to write better, smaller To-Dos next time. When you tighten the definition of a To-Do, you eliminate the excuse of running out of time and easily push your completion rate back above the ninety percent baseline.