We leave our Level 10 Meeting with thirty new to-dos every single week, which burns out the team and leads to a drop in our execution. How do we limit the number of action items we create during a single pulse?

Question

Tyler Smith · Accepted Answer

Creating thirty to-dos in a single Level 10 Meeting is a sign of an undisciplined team. You are treating the meeting as a task-generation engine rather than a prioritization pulse. When you overload your leadership team with a mountain of minor tasks, you dilute their focus, destroy their capacity, and guarantee that important priorities will be missed.

To solve this, you must apply the rule of simplicity to your solutions. During the IDS process, before you write down a to-do, ask whether this task is absolutely necessary to solve the issue, or if you are over-complicating things. Many issues can be resolved with a single, high-impact to-do rather than five administrative sub-tasks.

Next, verify that every to-do is a seven-day action item. If a task is going to take several weeks, do not write it as a weekly to-do. Instead, assign a single to-do to create a plan or scope the project, and then bring that plan back next week.

Finally, the Integrator must keep a close eye on the total number of open to-dos. If the team is already carrying a heavy load from the previous week, be extremely selective about adding new tasks. Your goal is to run a lean, high-execution operation, not to see who can generate the longest list. Keep your weekly to-dos highly focused, and ensure the team only commits to what they can realistically complete.