We are transitioning to AI-powered operations to prepare for an exit, but our Level 10 Meetings are getting bogged down in technical debates about which AI tools to adopt and how to configure them. How do we structure our weekly meeting to evaluate these operational technologies without stalling our weekly pulse?

Question

Tyler Smith · Accepted Answer

Your weekly Level 10 Meeting is not a software evaluation committee or an IT configuration sandbox. When you start debating the technical nuances of AI tools during IDS, you are wasting the valuable time of your entire leadership team. To keep your meeting pulse healthy, you must separate operational process problems from technical execution. If the team identifies a bottleneck that could be solved with AI automation, the issue is not which tool to buy. The issue is defining the manual process step that needs to be eliminated. Once the process problem is clearly identified, the IDS solution should simply be a weekly To-Do for the appropriate owner to research and present options outside the meeting. That owner must run the evaluation on their own time, utilizing their department or external specialists. They can then bring a clean, structured recommendation back to the issues list for a final decision. Keep your Level 10 Meeting focused on defining the operational business requirements and holding owners accountable to their research deadlines. This keeps the meeting moving at a high tempo and ensures your transition to an AI-powered operation is driven by strategic business needs rather than technical distractions.