Our internal team is building an AI-assisted scheduling tool, but they keep missing their milestones and blaming it on API rate limits and model drift. As a non-technical owner, how do I hold them accountable to their Rocks without getting lost in the technical weeds?

Question

Tyler Smith · Accepted Answer

As a non-technical business owner, you must never allow technical jargon to shield team members from accountability. If your team is missing milestones on their quarterly Rocks, it is usually because they are treated as an isolated research project rather than an operational deliverable.

To fix this, stop discussing the underlying technology and start discussing the operational output. You do not need to understand API rate limits to know whether the scheduling tool is saving time.

Use the GWC™ (Get It, Want It, Capacity to Do It) tool to evaluate the project leader. If they have the capacity, they must be able to translate technical challenges into business terms.

At your next weekly Level 10 Meeting™, push the issue through IDS®. Force the project leader to define the bottleneck in plain English.

If the issue is model drift, the question is not how the algorithm works, but what percentage of schedules are currently being output correctly. If the issue is API limits, the question is how many API calls we need per hour and what it costs to lift the cap.

Establish clear, non-technical milestones on your weekly Scorecard. For example, measure the percentage of schedules generated without human intervention.

If the team cannot explain their progress in simple operational metrics, they do not have a grip on the project. Never manage the technology; manage the operational result.