Slide 01

I Think I Know Where Your High Performers Are

CxO + Director

Core claim

A VP of Engineering with 60 engineers couldn't answer a simple CEO question: "Who are your top people?" The data was already there. AI usage telemetry. Sort by usage descending. The people with the deepest usage are probably your best people.

Every major AI platform generates usage telemetry — request volume, active days, session depth, completion acceptance rates. Those engineers sit down and do the work. AI is simply where that work happens now.

The real insight The interesting signal is not the top. It is the bottom. Senior engineers showing almost no usage. That signal matters. You need to discover why.

Slide 02

The Interesting Signal Is the Bottom, Not the Top

Problem / signal

Top of the list Obvious

High usage correlates with productive engineers. They sit down and do the work. AI is simply where that work happens now.

Bottom of the list Surprising

Principals, staff, architects, tenured mid-levels — showing almost no usage. These are the names you thought were doing well.

The question Why?

Are they blocked by access friction, or are they choosing not to engage? Two very different problems. Two very different responses.

Pull it up. Sort by usage descending. The people with the deepest usage — those are probably your best people. But that is not the important conversation.

The signal that matters

Slide 03

First Check: Your Organization Is Probably Blocking Them

Economics / comparison

What access friction looks like

Security reviews taking six weeks. Procurement stalling vendors for quarters.
IT tickets for API provisioning sitting unacknowledged for weeks.
Vague data classification policies making cautious engineers restrict everything.
Your best senior engineer showing zero usage because her October access request still has not been unblocked.

What it costs you

One engineering director waited three months for an IAM role — manager approval, VP co-sign due to budget codes touching production.
The VP was not processing non-urgent requests until the next planning cycle.
Three months. Usage: zero. Your most experienced people, sidelined by process.
Before questioning low-usage engineers, trace their access requests. Find where they stopped.

Slide 04

Then Have the Awkward Conversation. Not Accusatory. Curious.

Operating model

Scared

Some are scared of the shift

Picking up new tools feels like admitting old expertise is not enough. Expertise equals identity. The tools feel like a threat to what made them valuable.

Skeptical

Some watched juniors produce fast but mediocre work

They chose slow-but-correct over fast-but-sloppy. A rational response to real pressure. They need to see it done well, not just done quickly.

Paired

Pair them with someone who figured it out naturally

Not formal training. Just two engineers working together. Approach with curiosity, not performance frames. These are rational responses to real pressures.

Key insight You are surfacing something unspoken: why are you not using what everyone uses? The conversation will be awkward. Have it anyway. Do not stop or wait.

Slide 05

Pull the Data Today. Not Next Quarter. Today.

Implementation

The playbook

Sort two ways: highest and lowest usage. Glance at top — probably as expected. Look at bottom. Find the surprising names.

First: Find if they can actually use the tools. Trace it. If blocked, unblock immediately and loudly. Treat it like a production incident.

Second: Have an actual conversation asking what is in the way and what removes it. Some conversations will be easy. Some uncomfortable. A few genuinely hard.

Timeline Today. Not next quarter. The compounding gap between those who adopted and those who did not widens every week.

What the data tells you

Every major AI platform generates usage telemetry — request volume, active days, session depth, completion acceptance rates. You already have this data.

You have been looking at it as budget sanity-checking. Start looking at it as a map of where people need help.

Warning Engineers who have not internalized these tools are falling behind measurably, compoundingly. A year of avoiding this conversation serves nobody.

Slide 06

Some Conversations Do Not Have Happy Endings. Have Them Anyway.

Leadership close

The hard truth

If someone has access, time, training, watched peers shipping at two-to-three times their previous pace — and still is not engaging — that is not a tools problem. That is a judgment problem. And it is yours to address.

You are deciding whether to invest, and on what timeline. Engineers who internalized this new way form your organization's future core. Those who have not are falling behind measurably, compoundingly.

A year of avoiding this conversation serves nobody.