Our Visionary comes to every weekly Level 10 Meeting with a list of new AI tools they want the team to adopt immediately, causing operational whiplash. How do we use the IDS process to filter these requests without discouraging their innovation?

Question

Tyler Smith · Accepted Answer

The relationship between the Visionary and the Integrator is vital for healthy growth, but the Visionary's natural Quick Start instinct can easily overwhelm an organization with shiny-toy syndrome. To protect your operational focus, you must use your EOS tools to filter these ideas systematically.

First, establish a hard rule: no new technology tools can be introduced directly to the team without going through the Integrator and the IDS process. The Integrator must act as the operational shield, keeping the team focused on their current quarterly Rocks.

Second, use the Level 10 Meeting Issues List to park these ideas. During the IDS portion of the meeting, evaluate the Visionary's proposed AI tools against your V/TO:

- Does this tool directly support our current one-year plan or three-year picture?
- Do we have the capacity on our Accountability Chart to research and implement this tool right now?
- Is this solving a real operational bottleneck, or is it just an interesting piece of technology?

By running every tech proposal through this filter, you respect the Visionary's creativity while maintaining operational discipline. If an AI tool is truly a game-changer, scope it as a Rock for the following quarter rather than letting it disrupt your current focus.