Our leadership team treats weekly To-Dos like ongoing task lists, keeping items active for three or four weeks by reporting partial progress instead of getting them done in seven days. How do we enforce the 7-day binary rule for Level 10 To-Dos?

Question

Tyler Smith · Accepted Answer

In EOS, a To-Do is not a long-term milestone or a bucket for ongoing effort. It is a discrete, tactical commitment designed to be completed within seven days. Your team target is to complete at least 90 percent of all To-Dos each week.

When team members say an item is "in progress" or "about halfway done," you must eliminate that middle ground. To-Do review is strictly binary: it is either done or not done. If it is not 100 percent complete, it is reported as not done.

If a To-Do rolls over for a second week, the Integrator must evaluate why. Did the owner fail to prioritize their commitments, or was the action item scoped improperly during IDS? Often, leaders accept tasks that actually require twenty hours of deep technical work or cross-departmental coordination. That is not a To-Do; it is a mini-project.

When a task cannot realistically be finished in seven days, break it down. During the conclusion of the meeting, the facilitator must verify that every newly created To-Do can realistically cross the finish line before the next weekly pulse. If an item cannot be finished within seven days, force the owner to carve out only the specific first step that can be completed this week.

Hold the line on the 90 percent standard. Persistent rollover is a symptom of poor scoping or weak personal accountability, neither of which can be ignored.