My leadership team frequently creates weekly To-Dos that are actually massive multi-week projects, which inevitably fail to get completed in seven days. How do we force leaders to scope To-Dos down to seventy-two-hour bite-sized tasks instead of smuggling entire mini-Rocks onto the weekly list?

Question

Tyler Smith · Accepted Answer

Weekly To-Dos must be highly tactical, realistic action items that can be fully completed within seven days. When leaders write To-Dos like Redesign marketing onboarding sequence or Build out sales dashboard, they are setting themselves up for failure. These are mini-Rocks that require multiple steps, dependencies, and significant hours of work.

To stop this scope creep, the facilitator and the team must enforce a strict seventy-two-hour rule during the IDS phase when To-Dos are being created. A To-Do is not a goal; it is a single, clear, atomic action step.

When a solution in IDS leads to a To-Do, the facilitator must ask the owner: Can you realistically get this entirely finished before our next meeting, given your current operational load? If the answer is no, the task must be broken down into a smaller bite-sized step.

For example, instead of Redesign marketing onboarding sequence, the weekly To-Do should be: Draft first-draft outline of new marketing onboarding sequence. The following week, the next To-Do will be to review it, and the week after that will be to implement it.

By breaking large projects into sequential weekly milestones, you maintain momentum and keep your To-Do completion rate above ninety percent. This discipline prevents leaders from feeling overwhelmed by massive tasks and ensures that the weekly list remains a highly accurate predictor of operational execution.