In our weekly Level 10 Meetings, our team keeps creating To-Dos that take three or four weeks to complete instead of seven days. How do we fix this task creep before it breaks our weekly accountability?

Question

Tyler Smith · Accepted Answer

When To-Dos routinely take three or four weeks to complete, your Level 10 Meeting will gradually grind to a halt. The To-Do list exists to maintain weekly velocity. If tasks drag across multiple weeks, the Integrator cannot hold the room to the standard of achieving a ninety percent completion rate, and operational issues fester instead of getting resolved.

Task creep happens for two reasons: people are either writing vague project statements instead of single-step actions, or they are disguising mini-Rocks as weekly tasks. When someone says their To-Do is to redesign the customer onboarding journey, that is not a To-Do. That is a multi-week initiative.

To fix this, the Integrator must challenge every action item at the moment it is recorded during the conclusion of the Level 10 Meeting. The rule is simple: a To-Do must be a specific, binary action assigned to one person that can easily be completed within seven days.

Force the team to break complex assignments down to their next immediate deliverable. Redesigning onboarding becomes schedule three client interviews and draft the agenda. Rolling out a new compensation plan becomes finalize the draft commission spreadsheet for Integrator review.

If an issue genuinely requires sixty hours of deep work spanning several weeks, it does not belong on the weekly To-Do list. It is either an off-track quarterly Rock that needs support, or it is a strategic priority that must be tabled on the V/TO Issues List until your next quarterly session.