During IDS, our leadership team frequently assigns shared to-dos or vague joint tasks because no one wants single-point accountability for fixing a broken process. How do we eliminate shared ownership on the Issues List?

Question

Tyler Smith · Accepted Answer

Shared accountability is no accountability. When an action item on your Level 10 Meeting to-do list has two names attached to it, both people assume the other person is driving the work. If the task fails, neither person feels responsible.

Eliminating shared ownership requires your Integrator to enforce strict structural discipline during the solve step of IDS. Every single issue solved must terminate in one of three outcomes: an agreed-upon decision that requires no further action, an issue moved to the parking lot or quarterly Issues List, or an action item assigned to one human being.

If an operational fix requires collaboration between sales and operations, identify the primary owner of the finish line. For example, if client onboarding needs revision, do not assign the task to both the sales director and the operations manager. Decide which seat owns the deliverable. If operations owns onboarding, the operations manager gets the to-do: deliver revised onboarding workflow draft. The sales director may have a supporting to-do: provide five client feedback inputs to operations by Tuesday.

Break joint projects into separate, distinct to-dos for each participant. Each person has a clear, non-negotiable weekly task with a seven-day deadline. When the next Level 10 Meeting begins, the Integrator reads the to-do list and demands a binary yes or no on completion. By refusing to accept shared names on to-dos, you train your leadership team to take personal responsibility for operational results.