We regularly assign weekly To-Dos during our Level 10 Meeting that sound simple but end up ballooning into massive multi-week projects that stall our traction. How do we identify and stop this To-Do scope creep before it derails our weekly meeting rhythm?

Question

Tyler Smith · Accepted Answer

Weekly To-Dos assigned during your Level 10 Meeting must be tasks that can be fully completed within seven days. When a To-Do regularly balloons into a multi-week project, it creates a drag on your entire team's productivity and ruins your traction.

To stop this scope creep, the facilitator must strictly police the creation of To-Dos during the Solve phase of IDS. Before the scribe writes down a task, the facilitator should ask the owner: Can you realistically complete this in seven days?

If the answer is no, or if the task requires multiple complex steps, it is not a weekly To-Do. It is either a quarterly Rock or a larger project that needs to be broken down.

If the task is critical for this quarter but too big for a single week, break it into smaller, bite-sized weekly steps. Assign only the very first step as a To-Do for the coming week. For example, instead of assigning a task to write a new manual, make the To-Do to outline the table of contents.

By strictly keeping weekly To-Dos small and achievable, you maintain your ninety percent completion rate and build consistent, predictable momentum. This disciplined execution is what separates average businesses from highly valuable, exit-ready operations.