During our Level 10 Meeting™ IDS® session, we solve an issue by generating five different To-Dos for different people, which ends up cluttering our next week's agenda. How do we keep our solutions simple and avoid creating an administrative nightmare on our weekly task list?

Question

Tyler Smith · Accepted Answer

Solving an issue during IDS® should lead to clarity and traction, but teams often over-complicate the solution by generating multiple, overlapping To-Dos for different people. This creates an administrative burden and clutters your next week's meeting with minor task updates. To avoid this overwhelm, implement a rule of one clear owner and one clear action per issue solved. Under the Accountability Chart, only one person can be held accountable for a specific outcome. When you solve an issue, agree on the single next step that needs to happen within seven days to move the ball forward, and assign that To-Do to one leader. That leader is then responsible for executing the task, which may include delegating smaller sub-tasks to their own departmental teams outside of the leadership meeting. You do not need to track every single sub-task on your leadership Level 10 Meeting™ list. If an issue is so complex that it truly requires multiple high-level steps from different leaders over several weeks, you are likely looking at a Rock in disguise. In this case, you should either scale back the scope to a single weekly task or move the issue to the long-term list to be properly planned as a quarterly priority. Keeping your weekly To-Dos lean ensures your team stays focused on execution rather than managing lists.