We want to set an AI automation Rock for next quarter, but we are struggling to write it in a way that is S.M.A.R.T. and does not get bogged down in technical scope creep. How do we scope a quarterly AI Rock for our Integrator?

Question

Tyler Smith · Accepted Answer

The biggest mistake leadership teams make with AI Rocks is writing vague goals like research AI tools for sales. This is a recipe for three months of unproductive surfing and zero implementation. A Rock must be specific, measurable, attainable, realistic, and timely.

To scope an AI Rock for your Integrator, focus on the operational outcome, not the technology itself. Start by identifying the specific bottleneck you want to solve. For example, if your customer onboarding process takes ten days, your Rock should be written as: Reduce customer onboarding time from ten days to three days using AI-assisted automation.

Next, break the Rock down into clear milestones that must be completed within the ninety-day cycle. Week three should be mapping the current onboarding process. Week six should be selecting the tool and running a pilot with five clients. Week nine should be training the team and updating your documented process. Week twelve is full deployment and measuring the result on your Scorecard.

Ensure the Rock clearly states who owns it on the Accountability Chart. Usually, this is your Integrator or operations manager. The definition of done must be crystal clear. Do not accept a completed Rock that is just a list of recommendations. The tool must be fully integrated into your core process, and your team must be actively using it. If the process is not updated and the team is not trained, the Rock is not done.