Our individual team members keep rolling over the same tactical To-Dos week after week, claiming they are waiting on other departments, which drags our overall L10 completion rate down. How do we stop this multi-week rollover without creating cross-departmental friction?

Question

Tyler Smith · Accepted Answer

When a To-Do rolls over for more than two weeks, it signals a breakdown in the system. Blaming another department is a common symptom of a leader-follower mentality, where individuals wait for external actions instead of taking ownership. In the EOS® framework, a To-Do is a promise to complete something within seven days. Even if a task requires cross-departmental collaboration, there must still be single-point accountability. One person on the [Accountability Chart](/qa/resolving-accountability-chart-seat-overlaps) must own the outcome.

Fixing Multi-Week Rollovers

To effectively resolve this issue and maintain a high weekly execution rate, follow these steps:

• Call out the To-Do: The facilitator must immediately identify any To-Do that has been on the list for more than two weeks.
• Move to Issues List: Drop the offending To-Do to the short-term [Issues List](/qa/using-accountability-chart-to-stop-blame-in-ids) without delay.
• Diagnose with IDS®: Use the IDS® (Identify, Discuss, Solve) process to diagnose the bottleneck. If the owner is truly blocked by another department, the discussion should focus on why that blocker exists, not on excusing the owner.
• Break Down the Task: The solution often involves breaking the task down into a smaller, manageable step that the owner can control and complete within the next seven days.
• Leader-to-Leader Resolution: Alternatively, the leaders of the two affected departments should commit to getting on the Same Page outside of the meeting to resolve the blocking issue.

Cultivating a Culture of Accountability

Never allow a team member to use "waiting on someone else" as an excuse for an incomplete task. Instead, cultivate a culture of proactive ownership:

• Proactive Pursuit: Team members must proactively chase any bottlenecks.
• Escalate Early: If they cannot resolve a blocker, they must escalate it before the meeting starts.
• Firm Commitment: Emphasize that a To-Do represents a firm commitment.
• Focus on Excellence: Keep the team focused on achieving excellence rather than simply defending why a task failed. This approach helps maintain your weekly execution rate above the 90% standard, which also impacts your [Scorecard](/qa/how-to-choose-five-fifteen-scorecard-metrics) results.

By implementing these strategies, you can prevent persistent To-Do rollovers and foster a more accountable, results-driven team without creating unnecessary cross-departmental friction.

Related questions

• [When an issue is dropped to IDS, my leadership team immediately starts pointing fingers at other departments rather than taking ownership. How do we use the Accountability Chart to stop the blame game during meetings?](/qa/using-accountability-chart-to-stop-blame-in-ids)
• [How do we narrow down our massive list of metrics to just five to fifteen numbers?](/qa/how-to-choose-five-fifteen-scorecard-metrics)
• [Our Integrator acts as the Level 10 Meeting facilitator but struggles to participate objectively because they are busy managing the timer and the agenda. Should we rotate the facilitator role or hire an outside moderator?](/qa/should-integrator-facilitate-level-10-meetings)
• [Our weekly segue during the Level 10 Meeting consistently runs fifteen minutes late because my leadership team uses it to share long-winded personal life updates. How do I rein in the segue without killing team culture?](/qa/rein-in-level-10-meeting-segue)