My leadership team consistently falls below the ninety percent To-Do completion rate because they blame external dependencies like clients, vendors, or technology partners for their delays. How do we stop these external excuses and maintain the standard?

Question

Tyler Smith · Accepted Answer

When your team attributes missed To-Dos to external factors, they are confusing activity with accountability. A To-Do in your Level 10 Meeting™ is a commitment to complete a specific task within seven days. Even if a vendor or client is required to finish it, the team member who accepted the To-Do remains entirely responsible for managing that relationship and driving the outcome.

Reclaim To-Do Ownership

To shift your team's mindset and ensure accountability:

1. Rephrase To-Dos for Control:
• Before adding any task to the list, the To-Do owner must agree they have everything required to control the outcome.
• If they do not, the To-Do must be rephrased.
• For example, instead of "write complete contract," the To-Do should be "follow up with client three times on contract status."
• This shifts the focus from an external action to an internal execution.

2. Enforce Strict "Did You Do It?" Review:
• Implement a strict rule: "Did you do it, or did you not do it?"
• There is no middle ground, and no explanations are allowed during the review of [weekly Scorecard](/qa/how-to-review-scorecard-under-five-minutes) or To-Dos.
• If the answer is no, the To-Do stays on the list for one more week.

3. Escalate Persistent External Delays:
• If a To-Do is delayed by an external factor for two consecutive weeks, it must immediately be dropped down to the Issues List.
• Use the IDS® process to solve the root problem, which is typically a bad process, a slow vendor, or poor communication, rather than allowing it to linger on the weekly list. This helps prevent [blame games during IDS](/qa/using-accountability-chart-to-stop-blame-in-ids).

AI never sits in the room during a meeting. It works before the Level 10 Meeting to prepare data and after the meeting to capture and track decisions. For example, AI can help [optimize Scorecard metrics](/qa/ai-in-optimizing-eos-scorecard-metrics-and-accountability) or review [vendor agreements](/qa/ai-vendor-contract-review-automation) to highlight deviations, preventing some external dependencies from becoming issues.

Related questions

• [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)
• [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)
• [Our weekly Scorecard has grown to over thirty different metrics, and the meetings are taking too long. How do we trim the Scorecard down to the numbers that actually matter?](/qa/trimming-your-eos-weekly-scorecard)
• [How do we review our weekly scorecard in under five minutes?](/qa/how-to-review-scorecard-under-five-minutes)
• [How can AI optimize the Accountability Chart for EOS organizations undergoing exit planning?](/qa/how-can-ai-optimize-the-accountability-chart-for-eos-organizations-undergoing-exit-planning)