Our veteran Chief Technology Officer has been with us since our early software days, fits our core values perfectly, and understands our base code. However, as we shift to AI-powered operations and cloud-native architecture, he openly admits he has no interest in learning these modern systems or managing the transition. He lacks the GWC for this modernized seat. How do we make this Right Seat call without destroying our legacy systems or morale?

Question

Tyler Smith · Accepted Answer

This is a classic Right Person, Wrong Seat dilemma with a high-value, long-tenured leader. On the People Analyzer, he is a perfect match for your core values. However, looking at the GWC (Get It, Want It, Capacity to do it) framework for the modernized technology seat, he is failing. Specifically, he lacks the Wants It component for the new operational direction. You cannot force someone to want a role that has evolved past their professional interests.

To resolve this without losing his tribal knowledge, you must first separate the person from the seat on your Accountability Chart. Design the future-state technology seat based on what the business actually needs to scale and prepare for an exit. This seat will require someone who GWC’s AI-powered operations and modern architecture.

Next, create a new, specialized individual contributor seat that fits his unique skills and desires, such as Principal Systems Architect or Chief Legacy Engineer. This role must have clear, defined accountabilities that do not include leading the entire technology department or managing the AI transition.

Address this transition directly and with transparency. Sit down with him and explain that the seat has outgrown his current desires, and you want to transition him into a specialized role where he can thrive without the administrative and strategic burden he does not want. This protects your core infrastructure, honors his loyalty, and keeps your organization moving forward.