How to Talk About AI Usage in 1:1s (Without Making It a Performance Metric)

2026-11-15 · 8 min read · 1:1 Meetings

AI coding tools are changing how your engineers spend their day. Some have rebuilt their whole workflow around an agent. Some use autocomplete and nothing else. Some have tried everything and quietly gone back to typing.

You should know which, and the 1:1 is the right place to find out. It's also the easiest place to get it wrong. Ask the wrong way and "how are you using AI?" sounds like "why aren't you faster?" — and you'll get a defensive answer, not an honest one.

This guide covers how to bring AI into your 1:1s so it helps the engineer, the team and you, without turning into a performance metric.

Why the 1:1 Is the Right Place

AI use is personal in a way most tooling isn't. It touches how someone thinks, how confident they feel in code they didn't type, whether they worry about their role, and how they learn. A team meeting is the right place to share workflows. A 1:1 is the right place to understand this person's experience of them.

It's also where the conversation can be two-way. Engineers often have strong views on AI tools — about quality, about what they're being pushed toward, about what's worth the licence. You want to hear those views before they show up in a resignation letter or a quietly ignored mandate.

Set the Frame First

Before the first conversation, say plainly what this is and isn't. Something like:

"I want to understand how AI tools fit into your work — what's helping, what isn't, what you'd want from me. This isn't something I'm going to use to compare people or in reviews. I'd just like to know."

Then keep that promise. If AI usage ever shows up in a performance review as a number, every future conversation about it will be guarded.

Questions That Open Conversations

Good questions are open, specific to their work, and curious rather than evaluative.

About their workflow

About quality and confidence

About learning and growth

About the team

Questions That Shut Them Down

Avoid anything that sounds like a judgement or a quota:

Each one tells the engineer that AI usage is being measured against them, and the honest answer becomes risky to give.

Using Data Without Weaponising It

If you can see agent-assisted work in your team's Git history (see how to tell which agents your team uses), it's tempting to open with the number. Use it as a prompt for curiosity, not as evidence.

Better:

Worse:

Two reminders whenever you look at the data:

The Engineer Who Doesn't Use AI

Every team has someone who isn't using coding agents. Don't assume it's a problem to fix. Ask why, and listen:

What you shouldn't do is set a usage target. Mandated adoption produces performative adoption.

The Engineer Who Uses It for Everything

The opposite needs a conversation too, gently:

Frame it as protecting their growth, not limiting their tools: "You're shipping a lot with the agent, which is great. I want to make sure you're still getting the depth on the payments system you'll need to lead it next year."

Make It Part of the Rhythm

AI doesn't need a dedicated 1:1. A light touch works better:

For the broader craft of 1:1s, see the complete guide to 1:1 meetings, and for why the safety of these conversations matters so much, psychological safety in engineering teams.

How Emtricks Helps

Emtricks shows each engineer's AI adoption — their share of agent-assisted commits and PRs, how steady it is, and which tools and repos it shows up in — on their 1:1 page, right next to their GitHub activity, goals and impact stories. It's there as context for the conversation, labelled as a floor, and it never appears in a ranking. Team totals live separately in Pulse.

Key Takeaways


Bring each engineer's GitHub activity and AI adoption into your 1:1 prep automatically. Try Emtricks free for 30 days.