We want to build an AI-powered operation as part of our engagement. How do you prevent our session days from devolving into software demos and technical discussions when we should be focusing on leadership team health?

Question

Tyler Smith · Accepted Answer

We maintain a strict boundary between strategy and technical execution. Our quarterly session days are reserved exclusively for leadership alignment, health, and high-level strategic planning. We do not do software demos, coding, or system configuration during our session days.

If someone on your team tries to pull us into a technical discussion about specific AI tools or API integrations during a session, I will immediately park it on the Issues List.

We handle AI implementation using the standard Rock process. During our quarterly planning, we might identify a core process that needs to be automated to eliminate human error or increase capacity. We will write a specific, measurable Rock to automate that workflow.

The actual work of researching, testing, and implementing the AI solution happens outside of the room during your ninety-day execution cycle. Your team will manage that project using your standard project management systems and review progress during your weekly Level 10 Meeting™.

During our session days, we only look at the results. We ask if the Rock was completed and whether the automated process is hitting its target measurables on your Scorecard. This keeps our focus entirely on organizational performance, leadership alignment, and business value, rather than getting bogged down in technical support.