We have a highly skilled, legacy software engineering team, but our operational needs have shifted from writing raw code to orchestrating AI-driven development pipelines. Several of our senior engineers are resisting this transition and do not seem to have the GWC to manage AI tools. How do we handle this on our Accountability Chart?

Question

Tyler Smith · Accepted Answer

This is a classic people issue that requires a candid, reality-based conversation. Technology transitions often expose alignment issues on your Accountability Chart. When a seat changes fundamentally, you must re-evaluate the person sitting in it against the three filters of GWC™: do they get it, do they want it, and do they have the capacity to do it?

In this scenario, your senior engineers may Get the technology, but they do not Want it because they derive their professional identity from writing raw code, not auditing AI outputs. Or, they may want to adapt but lack the Capacity to learn prompt engineering and pipeline orchestration.

You cannot compromise your company's strategic future to protect the feelings of legacy employees. Start by clearly defining the new expectations for the software engineer seat on your Accountability Chart. The roles must explicitly include prompt optimization, AI code review, and pipeline management.

Next, have an open and honest conversation with each engineer. Mirror back their behavior and resistance. If they do not fit the new GWC™ requirements for this modernized seat, you must make a hard choice. You may need to move them to a different, highly specialized technical seat if one exists, or transition them out of the organization. Hire slow, fire fast. Fill those open seats with developers who embrace AI-enabled execution as their primary superpower, ensuring your team has the right people in the right seats.