ADD Engineering Leadership Deck
CxO + Engineering leadership 01 / 06

Slide 01

You Gave Engineers AI Tools. Then Built a System That Punishes Using Them.

CxO + VP Engineering + Board
What is happening right now

Peter is 58. He finishes his sprint work by 11 AM. It is 2:47 PM. He tried going full speed once — burned through the backlog, asked for more work. His manager said product was not ready. HR had questions about his time tracking.

Peter does not do that anymore. Now he uses AI to do just enough. 31 queries per day. The minimum is 30. His AI generates documentation nobody reads, just enough to keep his adoption metrics up. He is responding perfectly to the incentives you created.

1999 vs. 2025 In 1999, Peter did 15 minutes of real work in a week. In 2025, your highest-velocity engineer paces himself to avoid scrutiny. Same equation. Different decade. More back pain.

Slide 02

Peter Is a Rational Actor. Two Tuitions. A Herniated Disc. Seven Years Until Medicare. He Cannot Afford Scrutiny.

Root cause
Peter's situation 58 yrs

35 years of engineering experience. Can ship features in a quarter of the time it used to take. COBRA would bankrupt him. He cannot afford a review that questions his "trajectory." He is not going to do anything that shows up in a performance conversation.

His daughter Emma 26 yrs

Ships features in hours at an Austin startup. No scrum master with people skills. No mandatory 30 queries a day. Just outcomes. Her equity is worth more than his 401k. He is proud of her. Also painfully aware she is doing what he wishes he could do.

The slow bleed Invisible

You will not get a dramatic crisis. You will get a slow bleed. Competitors pull ahead. Leadership wonders why AI investment did not move the needle. Nobody connects the dots back to the 30-query minimum and the HR questions in October.

"My only real motivation is not to be hassled. That, and the fear of losing my job. But you know, Bob, that will only make someone work just hard enough not to get fired." — Peter Gibbons, 1999. And right now, in your org.

Twenty-six years later, the fear is realer. The tools are better. Nothing else has changed.

Slide 03

You Measure 30 AI Queries Per Day. Your Competitor Measures What Ships. That Gap Compounds Every Quarter.

Economics

What you are measuring

  • AI queries per day — minimum 30. Brian in Platform is at 75. Leadership cites him as the gold standard.
  • Story points per sprint. Velocity discussions. Retros asking why velocity is light.
  • Time tracking flagged when a fast engineer finishes early.
  • "We've enabled 2,000 engineers with AI assistants." Nobody asks what they shipped.

What the board eventually asks

  • Features shipped per engineer per quarter. Not queries. Not story points. Features.
  • Time from spec to production. Product takes two weeks to document what takes three days to ship.
  • Revenue per engineer. The number that surfaces when adoption metrics stop impressing.
  • Why your competitor — 47 engineers — ships 6x more features than your 1,800.

Slide 04

Peter Wants to Build. He Did Not Become an Engineer to Check Stock Prices and Generate Fake AI Queries.

The fix
What your system does to him

Your measurement system tells him to slow down. Your governance model tells him to stay in his lane. Product cannot feed him fast enough. Your AI query minimums reward theater over outcomes.

Emma does this every day. Ships in hours. No scrum master. No mandatory query counts. Just outcomes. She is 26 with equity worth more than Peter's retirement. He is 58 with 35 years of experience and a manager asking why he is only at the minimum.

You are not letting him build. That is the diagnosis. The fix is not a restructuring. It is removing obstacles.

What to do instead

Do not fire Peter. Do not restructure him. Do not send him to another AI training session led by someone who has never written code.

Move things out of his way. Let him write his own specs. Let him test his own code. Stop making him wait for handoffs from people slower than his AI assistant. Kill the query minimum and measure what he ships.

The upside Pay Peter for outcomes. Let him ship at full speed. A Peter who cares is worth ten Brians hitting 75 queries generating nothing.

Slide 05

Your AI Adoption Is Being Run by People Who Have Never Written Code. That Is Structural, Not Personal.

Root cause
Scrum master

"I have people skills."

29 years old. Never wrote a line of code. Now runs AI adoption for the engineering org. Checks in on Peter's status. Writes something in his notebook. "Any impediments to surface at retro?" Peter has heard this speech before — different decade, different scrum master, same energy.

Agile coach

"AI-Enabled Agile Transformation."

Certified from a two-day September workshop. Now teaches engineers how to use tools they understand better than he does. "Have you tried timeboxing your waiting?" Peter has been writing code since before this person was born. He nods anyway.

Peter

Mass analyzing codebases while they learn to prompt.

While the scrum master and agile coach figure out how to prompt for a meeting summary, Peter is doing work at a scale neither can evaluate. Nobody in that room is positioned to understand what he is actually capable of — or measure it.

Diagnosis Your AI transformation is being governed by people whose career depends on the old process surviving. That is not a criticism of them. It is a structural problem you created — and that only you can fix.

Slide 06

You Built a System That Trains Top Performers to Perform Mediocrity. You Can Also Build One That Does Not.

Decision close
Where you are right now

Your AI investment is producing 11% productivity improvement. Your competitor — 47 engineers — ships 6x more features than your 1,800. That is not a tooling gap. That is a governance gap. You gave engineers the tools and wrapped them in a system designed to absorb the gains.

Peter is not going to leave. He cannot. But he can start caring again. A 35-year veteran with nothing to prove and everything to lose, finally with permission to do his best work. He could be shipping circles around your competitors right now.