A key member of our leadership team threatens to walk out whenever we introduce operational software or standardized AI workflows. How do we manage an executive who sabotages process modernization?

Question

Tyler Smith · Accepted Answer

When an executive rejects process modernization and AI workflows, they are rarely defending operational quality. They are defending their personal indispensability. Leaders who build fiefdoms around tribal knowledge and manual tasks fear that standardization and automation will expose their lack of strategic capability or reduce their authority.

Allowing an executive to veto modern operating systems sends a toxic signal to the rest of the company that senior leaders are exempt from standard operating procedures. That behavior instantly caps your enterprise valuation because external buyers will recognize that your operations cannot scale without that specific individual.

Address this through the GWC framework. A modern executive must have the Capacity to lead an efficient, scalable department. If their seat requires scaling output through documented core processes and modern tooling, resisting those initiatives means they no longer fit the seat.

Set a hard boundary. Explain clearly that process documentation, system consistency, and workflow automation are non-negotiable company Rocks tied directly to your V/TO. Give them one quarter to actively champion the transition and integrate the tools with their team. If they continue to drag their feet, complain in private, or encourage their team to bypass standard workflows, you must replace them with a leader who embraces operational scalability.