We are eager to introduce AI-driven efficiencies into our daily workflows, but we do not want to build a separate, chaotic project tracking system outside of our EOS® framework. How do we use our weekly Level 10 Meeting™ and IDS® sessions to manage and pressure-test our AI adoption projects?

Question

Tyler Smith · Accepted Answer

You do not need a new project management system to implement artificial intelligence. In fact, doing so will only create operational chaos and dilute your focus. Instead, treat your AI adoption initiatives exactly like any other operational issue or strategic project by routing them through your existing weekly Level 10 Meeting™.

When a team member identifies a workflow that can be optimized with an AI tool, they should add it to the issues list. During the IDS® portion of your meeting, the leadership team must pressure-test the idea. Do not get caught up in the technical novelty. Focus on the operational impact. Identify the specific bottleneck, discuss whether the proposed AI tool actually solves the problem, and decide if the implementation is worth the resources.

If the team agrees to move forward, assign a clear, actionable To-Do to a single owner on the Accountability Chart. This To-Do should have a hard deadline, usually seven days, to research the tool or run a small-scale test. If the AI project is larger and will take more than a week to execute, do not let it drag on as a vague task. Elevate it to a departmental or leadership Rock for the upcoming quarter.

By using IDS® to vet your AI initiatives and To-Dos to track their immediate execution, you maintain complete control over the rollout. This approach prevents your team from chasing shiny software tools while keeping your technology adoption grounded in real, measurable operational metrics.