When our departments run AI workflow experiments between sessions, how do we bring those outcomes into our quarterly session without turning the day into a software demonstration?

Question

Tyler Smith · Accepted Answer

AI experiments must be evaluated through the lens of business results, not technical novelty. A quarterly session day is dedicated to organizational health, strategy, and execution, not software demonstrations or vendor reviews. When your team implements an AI tool between offsites, that initiative should be captured exclusively through your standard EOS tools: Rocks and the Scorecard.

If streamlining customer onboarding using AI was selected as a Rock for the quarter, the reporting during the session takes less than thirty seconds. Did the Rock get completed, yes or no? Did it reduce onboarding labor hours by the target percentage, yes or no? If the initiative succeeded, the new workflow is documented as part of your Core Processes. If the project failed, stalled, or caused operational friction, it drops to the Issues List for IDS.

During the IDS portion of the day, we do not critique code or evaluate software interfaces. We identify the operational root cause. Was the workflow poorly defined? Did the seat holder lack the technical competency to execute? Did middle management resist adoption?

By treating AI tools as operational levers rather than isolated IT pet projects, your leadership team keeps its focus on capacity, margin improvement, and process repeatability without wasting valuable session hours on technical presentations.