We want our leadership team to actively drive AI-powered efficiency across our business, but our weekly Level 10 Meetings are already packed with standard operational fire fighting. How do we structurally integrate our AI automation initiatives into our weekly agenda without overloading our issues list?

Question

Tyler Smith · Accepted Answer

Your weekly Level 10 Meeting™ is a tactical operational pulse, not a strategic planning session. If you try to run deep-dive AI workflow designs or system architecture debates during your standard weekly IDS® section, you will derail the meeting and fail to solve your pressing weekly issues.

To integrate AI-powered operational improvements without cluttering your weekly list, you must categorize these initiatives correctly. If identifying manual, repetitive tasks is a key focus, these opportunities should first be raised as headlines or added to your Long-Term Issues List, which is kept on your V/TO®.

If an AI initiative is critical for the current quarter, it must be established as a quarterly Rock. Once it is a Rock, you only review its status as on track or off track during the five-minute Rock review. If it goes off track, it drops to the weekly Issues List, where the team can remove the specific bottleneck. For smaller, quick-win automations, assign a simple, tightly scoped weekly To-Do to research or implement a specific tool. By keeping long-term AI strategy on your V/TO® and only processing active bottlenecks or small, seven-day action items during your Level 10 Meeting™, you maintain your operational pace while systematically building an AI-powered operation.