When our leadership team weekly To-Do completion rate drops below 90 percent, leaders routinely defend missed tasks by claiming they were blocked by people outside the leadership team. How do we eliminate external dependencies as an excuse?

Question

Tyler Smith · Accepted Answer

A To-Do in EOS is an absolute commitment made by a leadership team member to complete a specific, binary action within seven days. When leaders excuse missed To-Dos by pointing fingers at direct reports, external vendors, or slow clients, they reveal a fundamental misunderstanding of ownership.

Leadership team members do not get a pass because an external party failed to deliver. The individual who owns the To-Do owns the outcome, not just the initial request.

If your To-Do completion rate is consistently missing the 90 percent benchmark because of third-party bottlenecks, implement two operating rules during IDS.

First, ban passive delegation in task commitments. If an Integrator asks a VP of Sales to get a vendor quote by next week, the VP of Sales cannot write down: Wait for vendor proposal. That is a passive dependency. The To-Do must be phrased around what the leader directly controls: Follow up with vendor daily and escalate to CEO if quote is not received by Thursday.

Second, size To-Dos properly during the meeting. If getting an answer from a client typically takes two weeks, do not agree to a seven-day To-Do that guarantees failure. Instead, break the commitment into an immediate, controllable action step: Call client procurement lead by Tuesday to establish decision timeline.

When a leader reports an uncompleted To-Do and says, I sent the email but Bob never replied, the Integrator must hold the line. Bob did not drop the ball; you did. What did you do on day three when Bob went silent? Ownership means driving the commitment across the finish line regardless of who else touches the work.