We frequently assign To-Dos to multiple owners during our Level 10 Meeting™ because several departments need to collaborate on the solution, which leads to finger-pointing when the To-Do is not done. How do we enforce single-point accountability for weekly To-Dos?

Question

Tyler Smith · Accepted Answer

In the EOS® framework, if more than one person is accountable for a task, nobody is accountable. Assigning a weekly To-Do to multiple people is a guarantee that it will slide, get delayed, or result in finger-pointing when the deadline arrives. To maintain operational momentum, you must enforce single-point accountability for every single action item.

When a solution in IDS® requires work from multiple departments, the team must identify one single owner to hold the To-Do. This individual is not necessarily the person doing all the work; rather, they are the quarterback who is fully responsible for ensuring the task gets completed. They are the person whose name goes on the list, and they are the one who must report done or not done at the next meeting.

If the task is too large or complex for one person to manage, it is likely not a weekly To-Do. You should either break it down into smaller, individual To-Dos assigned to specific people, or elevate it to a Rock if it requires a full quarter of cross-functional effort.

Do not let your team hide behind joint accountability. When reviewing the issues list and setting To-Dos, the facilitator must ask: Who is the single owner of this item? If the team hesitates, do not move on until one person steps up and takes ownership. This clean line of responsibility eliminates confusion, builds trust, and keeps your execution high.