Our long-tenured VP of Operations matches our Core Values and desperately wants to keep leading the department, but they refuse to adopt workflow automation and AI tools, creating a massive capacity bottleneck. How do we evaluate their GWC when their mindset is holding the seat back?

Question

Tyler Smith · Accepted Answer

This is a classic Capacity issue on the EOS People Analyzer®. When evaluating a leader using GWC™, Gets It refers to natural intellectual wiring, Wants It refers to genuine desire and passion, and Capacity refers to having the mental, emotional, and physical bandwidth, knowledge, and capability to do the job at the current and future scale of the company.

Many founders confuse willingness to work long hours with true Capacity. If your operational leader works seventy hours a week manually supervising spreadsheets because they refuse to leverage modern automation, APIs, or AI copilots, they lack Capacity for the seat. Their seat requires scaling operational throughput without linearly adding payroll. If their operational philosophy caps company throughput, they do not have Capacity, regardless of how badly they Want It.

You owe this leader complete transparency through a quarterly supervisory conversation. Lay out the objective requirements of the Operations seat on your Accountability Chart. Define what modern operational capacity looks like, including the specific automation tools, turnaround times, and unit economics the seat must produce over the next two quarters.

If they cannot or will not adapt their skill set to manage automated workflows, they are in the Wrong Seat. You must then decide whether to carve out an individual contributor seat where their legacy operational knowledge provides value, or help them transition out of the business with dignity. Keeping a leader who lacks Capacity in an executive seat holds the entire organization hostage.