In our Level 10 Meetings, our VP of Operations constantly excuses missed Rocks by claiming their department is understaffed, yet they refuse to adopt AI tools and automated workflows that would eliminate the backlog. How do we break this cycle?

Question

Tyler Smith · Accepted Answer

This is a classic operational defense mechanism. Leaders who are accustomed to managing through headcount often view staffing shortages as a bulletproof excuse for missed deliverables. At the same time, adopting AI tools or automated workflows feels intimidating, complex, and threatening to their established domain.

To break this stalemate, you must stop accepting headcount requests as the default answer to capacity problems. In a modern, exit-ready business, scaling requires building a superstructure powered by automated systems, not simply throwing expensive labor at manual friction points.

Take the issue straight to the IDS board during your next Level 10 Meeting. Dissect the specific processes that are causing the backlog. Force the VP of Operations to map out the exact tasks consuming their team time. When the data reveals that twenty to forty percent of their team capacity is burned on repetitive data entry, manual reporting, or fragmented customer updates, the problem is no longer a headcount issue; it is a system architecture issue.

Assign a mandatory 90-day Rock to implement automated workflows or AI-driven tools that target those specific bottlenecks. Make it clear that future budget allocations for additional hires will be frozen until current workflows are modernized.

Evaluate whether the VP has the Capacity to lead an AI-powered operation. If they continue to drag their feet and demand more bodies to run obsolete manual processes, you have a leader who no longer GWCs the seat. You cannot let one executive operational stubbornness cap the scale and valuation of the entire business.