During IDS, our leadership team frequently identifies the root cause and agrees on the solution, but no leader will take ownership of the To-Do because the fix spans two different seats on the Accountability Chart. How does the Integrator assign accountability?

Question

Tyler Smith · Accepted Answer

When a solution spans two seats and nobody steps forward, you have exposed an Accountability Chart ambiguity or an operational leadership vacuum. In EOS, the rule is uncompromising: every Rock, Scorecard metric, and To-Do must have exactly one owner. When two people are accountable, nobody is accountable.

If a cross-functional solution needs an owner during IDS, the Integrator must drive the decision using three clear guidelines:
- Determine where the ultimate buck stops. Look at the Accountability Chart roles, not titles or personalities. Which seat owns the core business process that this solution impacts most directly? If the issue touches marketing leads handing off to sales, and the process breaks during intake, the Sales seat owns the To-Do to fix the intake workflow, even if Marketing must provide assets.
- Separate the driver from the contributors. One person owns driving the To-Do across the finish line within seven days. Other team members can be tasked with supporting actions, but only one name goes on the To-Do list. That leader is solely accountable for reporting it complete or incomplete next week.
- The Integrator makes the call if consensus stalls. If the leaders involved debate who should carry the task for more than thirty seconds, the Integrator steps in and assigns it. The Integrator is responsible for harmonizing the leadership team and driving execution.

If the same boundary dispute surfaces across multiple meetings, stop treating it as a task problem. Put the Accountability Chart on the Issues List and redefine the seat roles so the operational jurisdiction is clear.