Our weekly Level 10 Meeting Issues List is fairly clean, but our To-Do list has ballooned to thirty items because we keep assigning multi-week projects as weekly to-dos. How do we enforce the strict rule that a to-do must be completed in seven days?

Question

Tyler Smith · Accepted Answer

A ballooning to-do list is a primary cause of meeting drag and operational friction. When your weekly Level 10 Meeting™ has thirty pending to-dos, it means your team is using the meeting to track projects rather than driving rapid, weekly execution.

The rule is absolute: a to-do must be something that can be completely finished in seven days. If a task takes longer than that, it is either a Rock, a milestone for a Rock, or an issue that needs to be broken down further.

To enforce this standard, the facilitator must challenge any to-do that sounds like a multi-week project. For example, if a leader suggests a to-do like: rebuild the client onboarding portal, the facilitator must immediately stop them. That is not a weekly task.

Instead, ask the leader what specific, bite-sized step they can complete by next week. The to-do should be: draft the outline of the new onboarding portal flow.

By breaking large projects down into seven-day deliverables, you ensure constant progress and keep your team highly accountable. If a task cannot be completed in a week, do not write it on the list. Keep your to-dos fast, actionable, and tightly focused to maintain your weekly pulse momentum.