When we assign a To-Do at the end of our Level 10 Meeting, the whole team tries to design the exact action steps and timeline for the owner rather than just defining the expected outcome. How do we stop this over-collaboration on weekly tasks?

Question

Tyler Smith · Accepted Answer

The final phase of the Level 10 Meeting is the wrap-up, where you document weekly To-Dos. A common waste of time occurs when the entire leadership team tries to design the exact action steps for a newly assigned To-Do. This is a micro-management trap that kills meeting momentum. When an issue is solved during IDS, the resulting To-Do must be assigned to a single owner on the Accountability Chart. Once that owner accepts the To-Do, they own the how. The rest of the team must step back. The only thing that needs to be agreed upon in the meeting is the what and the when. Write the To-Do as a clear, binary action item that can be completed within seven days. For example, instead of the team debating how to write an email template, the To-Do should simply read: Draft new client email template. The owner of that To-Do is fully responsible for figuring out the copy, the layout, and the distribution method on their own time. If they need input from other team members, they can schedule a separate, brief sync outside the Level 10 Meeting. Do not allow your weekly meeting to become a working session. By keeping To-Dos focused strictly on high-level deliverables, you maintain accountability, respect individual autonomy, and wrap up your meeting on time.