During our Level 10 Meetings™, our team keeps bringing up issues that are actually just tasks they forgot to do, turning IDS® into a messy to-do list review. How do we police our issues list to keep it focused on true operational roadblocks?

Question

Tyler Smith · Accepted Answer

When your weekly issues list becomes a dumping ground for forgotten tasks and minor operational updates, your Level 10 Meeting™ will lose all traction. This happens because the team lacks the discipline to separate individual accountability from team-wide problem-solving. To fix this, you must strictly police what gets added to the issues list. Before any item is discussed, ask the person who raised it: is this a true roadblock that requires the collective brainpower of the leadership team, or is it just a to-do you need to complete? If it is just a task, do not run IDS® on it. Turn it into a weekly to-do on the spot, assign it to the responsible person, and move on. The issues list is reserved for systemic bottlenecks, strategic opportunities, and red scorecard metrics that require collective problem-solving. Additionally, enforce the rule that individual tasks must be managed outside of the Level 10 Meeting™. Your weekly meeting is designed to keep the leadership team aligned, not to micro-manage personal checklists. Maintaining this operational boundary requires practice and strong leadership. If you struggle to maintain this discipline, examine the keys to a successful EOS® implementation with an experienced guide. An EOS® Implementer can observe your meetings and help you rebuild the strict boundaries needed to keep your weekly sessions focused on high-level strategy and execution.