We have too many issues hitting our Level 10 Meeting IDS list every week, and we waste valuable time trying to figure out which ones are symptoms and which ones are the actual root causes. How can we use AI to analyze our weekly issues log before the meeting so we can run a more efficient IDS session?

Question

Tyler Smith · Accepted Answer

To run a highly productive Level 10 Meeting, your issues list must be clear and prioritized. When your team dumps raw problems into your software during the week, you often end up with fifty minor symptoms instead of the core business issues. You can solve this by setting up a simple automated workflow that pre-digests your weekly issues log before your meeting starts. First, connect your meeting software or issues spreadsheet to an AI assistant via a basic integration tool. Configure the AI assistant to read the raw text of every submitted issue and compare it against your documented core processes and current quarterly Rocks. The AI should look for common patterns, such as multiple complaints about the same client delivery bottleneck or repeated mentions of a specific department. It then categorizes the list into three distinct buckets: operational symptoms, standard process breakdowns, and major strategic issues. Before the meeting, the AI generates a brief, structured summary of these trends and suggests which issues are actually symptoms of the same root cause. The meeting owner reviews this summary ten minutes before the session starts. This workflow does not make decisions for your leadership team, but it allows you to group related symptoms together immediately. When you transition to the IDS portion of your Level 10 Meeting, you can skip the debate about what the list means and go straight to identifying, discussing, and solving the true root causes of your operational problems.