tyler-smith.com · Questions & Answers

In our Level 10 Meeting™, our leadership team frequently assigns weekly To-Dos to two or three people, and our completion rate consistently drops below 90 percent because each person assumes the other is driving. How do we eliminate shared To-Dos and enforce single-point accountability?

Co-ownership is a lie. When two people own a To-Do, zero people own it. Shared tasks are the primary reason teams miss the 90 percent completion benchmark because ambiguity gives everyone permission to assume the other person was supposed to execute.

In EOS, accountability is always binary and individual. Every single action item created during IDS must have exactly one name attached to it on the To-Do List. That person is not necessarily the only human doing the physical work, but they are the sole individual accountable for confirming the task is complete in seven days.

To break the shared ownership habit, the facilitator must enforce a hard rule before the scribe types the task into your software. If someone says, "Sarah and I will review the new commission plan," the facilitator immediately stops the conversation and asks: "Who owns it?"

Force the two leaders to pick one driver right there. If Sarah owns the task, Sarah carries the burden of scheduling the meeting with the other leader, gathering the input, and bringing the finished result to next week's meeting. If the other person fails to respond, Sarah is still accountable for escalating the barrier before the seven days are up.

Assigning single-point accountability removes plausible deniability. It forces leaders to scope the work realistically because one person knows their reputation is on the line when the box is checked or left empty next week.

Category: Level 10 Meetings

← All questions