Our leadership team wants to set an AI Rock for next quarter, but every time we discuss it, the scope turns into an endless technical wish list. How should we frame and scope an operations-improvement Rock that uses AI so it actually gets completed in ninety days?

Question

Tyler Smith · Accepted Answer

The mistake leadership teams make is naming a Rock around technology. When you set a Rock called Implement AI in Operations, you create an open-ended technical science project with no clear finish line. Technical projects drag on for quarters because teams focus on software capabilities rather than business outcomes.

Never frame a project around machine learning or artificial intelligence. Frame it as an operational improvement that happens to use AI as a tool to solve an expensive bottleneck. Machine learning should only be mentioned as a footnote in the execution plan.

Start with your Scoreboard and your Core Processes. Identify a specific, documented process where human labor is stretched thin and cycle times are hurting gross margin. A proper Rock is specific, measurable, attainable, realistic, and timely. Instead of an AI Rock, write a Rock like: Reduce customer onboarding cycle time from fourteen days to three days by automating file intake and setup.

To ensure completion within the ninety-day EOS® cycle, break the Rock into measurable milestones:
- Document and simplify the manual onboarding SOP during weeks one through three.
- Configure and test the AI automation tool against historical client files in weeks four through six.
- Run the automation alongside the manual process for two weeks to audit accuracy.
- Fully transition the process to the seat on the Accountability Chart and update the Scoreboard metric by week twelve.

By anchoring the Rock to an operational metric rather than software adoption, your team focuses on measurable throughput. The technology serves the business, not the other way around.