Slide 01

You Found Your Best AI Engineer. Then You Sentenced Her to Full-Time Training Duty.

VP Engineering + CTO + Director

What you did

Sarah goes home and builds things with AI. Ships side projects on weekends. Sees what is possible and cannot stop talking about it. She is rare. So naturally, you made her the "AI Champion" and put her in charge of training everyone else.

The logic is understandable. She is good at AI, enthusiastic, explains things clearly — who better to bring the rest of the team along? Here is the problem: you have sentenced your highest-potential engineer to full-time enablement duty. That is not a reward for excellence. That is a punishment wrapped in a promotion.

What she gave up Sarah does not get to refactor the authentication service you have been deferring for three years. She does not get to build the internal tooling that would save fifteen hours a week. She gets to explain prompt engineering to people still deciding whether they are interested.

Slide 02

Sarah Cannot Move People Who Do Not Want to Move. That Is Not a Skills Gap. That Is a Motivation Gap.

Why the model fails

What Sarah can do

Build complex systems with AI assistance at a pace that would shock most of your team.
Spot architectural opportunities invisible to engineers still working the old way.
Demonstrate what one AI-fluent engineer can actually ship — if given the chance.
Transfer patterns through proximity, pairing, and visible work — not lecture.

What Sarah cannot do

Restructure teams. That requires authority she does not have.
Have hard conversations about career trajectories. That is your job.
Decide whether resistance is a training issue or a fit issue. Also yours.
Allocate budget for outside help. Still yours.
Manufacture motivation in a conference room with better documentation.

Slide 03

Free Sarah. Own the Upskilling Problem Yourself. Let Champions Champion Through Building.

The fix

Move 1

Free Sarah

Let her solve the hard technical problems you have been deferring. The authentication service. The internal tooling that would save fifteen hours a week. The integration nobody wants to touch. Let her demonstrate what one engineer with AI fluency can actually ship. That demonstration will do more for buy-in than a hundred enablement sessions.

Move 2

Own it yourself

The upskilling problem is real. Some percentage of your team is not ready for AI-assisted development, and that gap will cause friction. But that is a leadership problem, not an engineering problem. Bring in external training. Create learning paths with real accountability. Have honest conversations about career trajectories. That is your work.

Move 3

Create pull, not push

The best way to show your organization what AI can do is let your best people do it — visibly, on real problems. That creates pull. That creates curiosity. That creates motivation Sarah cannot manufacture in a conference room with better slides and another lunch-and-learn.

The moral Don't make your high-performing engineers train your low-performing engineers. That is not their job. That is yours.

Slide 04

You Have Engineers With AI Skills, Already on Payroll, Who Know Your Domain. You Didn't Have to Hire Them. You Don't Have to Wait for Them.

The opportunity

What you actually have

Engineers with AI skills you desperately need. Engineers you can afford. Engineers who already understand your domain, your codebase, your customers. You did not have to hire them. You did not have to onboard them. You did not have to wait eighteen months for them to learn where the bodies are buried.

They are already on your payroll. They are already bought in. They are ready to build.

And you have hard problems languishing on the backlog. An organization that needs to see what is possible before they will believe it.

What is in the way

The only thing standing between you and that future is a staffing decision you made with good intentions.

You thought you were rewarding Sarah by giving her the AI Champion role. She saw it as you pulling her off the work she is good at and handing her a job she cannot actually do — change the motivation of engineers who do not want to change.

The risk If Sarah leaves for a company that lets her build, you lose both her output and your best proof point for what AI-native development looks like. That is a two-compounding loss.

Slide 05

Sarah Wants to Build. Let Her. You Bring Everyone Else Along. That Is What Leaders Do.

Decision close

Two paths from here

Path one: Keep Sarah in the AI Champion role. She continues pushing reluctant engineers up a hill. Your organization learns slowly, if at all. Sarah eventually leaves for a company that lets her build. You lose both her and your proof point.

Path two: Free Sarah to solve hard problems visibly. The organization watches what one engineer with AI fluency ships in a quarter. That creates the pull that a hundred training sessions never will. You own the motivation gap — the hard conversations about trajectory, the external help, the accountability structures.

The Guardian Building is still there. It still catches the light. Nobody asks Rowland to teach workshops. They let him build.