When we decide to automate a workflow using AI, how do we track the implementation progress during our ninety-day cycle without turning our quarterly sessions into tech-support meetings?

We treat AI automation exactly like any other major operational improvement. It must be framed as a Rock with clear, non-technical milestones.

When we set an AI-related Rock during our quarterly session, we do not discuss coding, APIs, or software selection. Instead, we focus on the business outcome. The Rock might be to automate eighty percent of our customer onboarding process, or to reduce manual data entry in finance by ten hours per week.

The owner of that Rock is responsible for the technical execution outside of our sessions. During our ninety-day cycle, we track progress at a high level. If the Rock is on track, we move on. If the implementation hits a technical roadblock, it is listed as an issue on your weekly Level 10 Meeting™ agenda.

If the issue cannot be resolved weekly, we bring it to our next quarterly session. Even then, we do not solve the technical bug. We solve the operational impact of the delay.

- Focus quarterly sessions on business outcomes, not technology implementation details.
- Keep AI-related Rocks clear, measurable, and outcome-oriented.
- Use the weekly meeting pulse to handle execution bottlenecks.

This approach keeps your technology improvements fully aligned with your business strategy without dragging your leadership team into the weeds.

Category: Working With Tyler