tyler-smith.com · Questions & Answers

Leaders on our team keep writing To-Dos that are actually mini-projects spanning three or four weeks, which constantly carries them over week to week. How do we enforce the seven-day To-Do rule without creating administrative noise?

When a To-Do carries over for three consecutive weeks, it ceases to be a To-Do. It is an unmanaged project masquerading as a weekly commitment. Allowing multi-week tasks to sit on the To-Do list destroys urgency, obscures bottlenecks, and corrupts your completion percentage.

The rule in the Level 10 Meeting™ is absolute: a To-Do must be completed within seven days. If a task requires twenty-one days of effort, the person accountable must break that work into seven-day binary slices.

Enforce this during IDS® and Conclude when action items are being generated. When a leader says their To-Do is to create a new compensation structure, the Integrator must challenge the scope immediately. Ask what single action can be finished before next week meeting. The To-Do becomes: draft the commission tiers for sales reps and email to the Integrator by Tuesday. The following week, the subsequent action might be: finalize bonus criteria with finance.

If a task cannot be broken into distinct seven-day deliverables, evaluate whether it is actually a quarterly Rock or an ongoing operational responsibility tied to an Accountability Chart seat.

Stop carrying incomplete To-Dos forward indefinitely. If a commitment is not done after two weeks, remove it from the To-Do list and drop it back onto the Issues List. Forcing the owner to publicly reprioritize the issue in IDS exposes whether the commitment actually matters or if it was busywork that can be abandoned entirely.

Category: Level 10 Meetings

← All questions