Our Visionary wants to replace our entire legacy software system with AI-native tools this quarter, but our Integrator warns that this will create massive technical debt and operational chaos. How do we use the IDS® process and our V/TO® One-Year Plan to sequence this transition safely?

Question

Tyler Smith · Accepted Answer

The classic tension between a Visionary who wants to race ahead and an Integrator who wants to protect stability can stall your business if left unresolved. To move forward without breaking your operations, bring this issue to your next weekly Level 10 Meeting™ and use the IDS® process to identify, discuss, and solve the root conflict.

First, identify the real issue: it is not whether to adopt AI, but how to sequence the transition. The Visionary sees the long-term competitive advantage, while the Integrator sees the immediate operational risk. During the discussion, refer to your V/TO® One-Year Plan to ground the conversation in your current commitments. Look at your existing corporate Rocks and operational capacity.

To solve the conflict, agree to split the transition into manageable phases. Instead of replacing the entire legacy system at once, write a specific Rock for the upcoming quarter to pilot an AI tool in a single, non-critical department. This allows you to test the technology, document the new Core Processes, and measure the results without risking your core business operations.

By sequencing the rollout in your One-Year Plan, you satisfy the Visionary's drive for innovation while giving the Integrator the structured timeline they need to maintain operational excellence and prevent technical debt.