You're personally behind on AI. You haven't been deliberately ignoring it. You've been running a function, managing priorities, responding to the pressures that actually land on your desk. AI has been on the list, but not at the top of it. You know what you should be doing, and you haven't built the time or the habit to do it.

And yet your team is moving. Not because of systematic leadership from you, but because one or two people on your team have taken AI seriously on their own initiative. They're experimenting, adopting tools, sharing what works, and producing work that's visibly different from what the function did eighteen months ago.

You're getting credit for it. Leadership sees output changing. They assume it's because of you. It isn't. It's because of them.

Why this pattern matters

This is the most precarious of the six patterns, and it's precarious in a way that doesn't feel precarious. Your function is performing. You're not in immediate trouble. But the situation you're in right now has two risks running in parallel, and both of them are likely to surface in the next twelve months.

The first risk is about the people carrying the work. They're under-recognized, unsupported, and recruitable. They're doing ambitious work without the institutional backing to make it official. They notice. They talk to peers at other companies. They get approached by recruiters. When they leave (and they will, on their current trajectory) they take the thing that's been making your function look current. You'll be left holding credit you can't cash.

The second risk is about you. When leadership eventually asks you to talk about the strategy behind what your team is doing (the thinking, the decisions, the framework) you won't have one. Because it isn't yours. You'll either have to admit you don't know, or you'll invent something and it will be obvious you're performing understanding rather than exhibiting it.

If you've been feeling a low-grade discomfort about this without naming it, that discomfort is useful. It's telling you the truth before leadership does. The good news is that this pattern is more recoverable than it feels, but only if you start now.

Your roadmap

This week: Have a real conversation with the person on your team driving AI work.

‍Not a status update. Not a one-on-one with an agenda. Sit with them and ask three questions. What are you doing with AI that I don't know about? What's frustrating you about how our function approaches this? What would you change if you could?

Don't defend. Don't explain. Don't manage. Listen.This conversation is information you need, and it's also recognition the person needs. Accidental Laggards often discover in this conversation that the team member has been waiting months for the leader to engage with what they've been doing. That wait is what will eventually drive them to leave.

‍This quarter: Give them authority, resources, and visibility.

‍A formal role on the team ("AI lead," "capability owner," something that makes the unofficial work official). A budget line they control. A voice in team planning beyond their individual responsibilities. Visibility to your leadership as the person driving this work.

Alongside that, start closing your own skill gap. Not to lead them (you're behind, and they'll see through that) but to stop being the bottleneck. Spend time each week actually using AI tools for your own work. Learn by doing, not by reading. You need enough fluency to evaluate the work they're proposing, not enough to direct it.

The combination, backing them visibly while building your own capability, is what repositions you from Accidental Laggard to engaged leader.

‍This year: Turn individual initiative into institutional capability.

‍The goal is to build a function where the AI capability isn't dependent on one or two motivated people. That means documented workflows, shared prompts, cross-team training, expectations for every recruiter, and rituals that make AI part of how everyone works.

The specific test: if the person currently driving this left tomorrow, what would remain?

That answer is your roadmap. The gap between what you have now and what would remain after they left is the capability you need to institutionalize this year.

The uncomfortable question

If the person on your team who's driving this got a better offer next month, what would your function lose? And what have you done to make sure they don't take that offer?

What people often ask after seeing this result

"What if I'm not sure who on my team is driving this?"

That's itself a sign. The Accidental Laggard's defining feature is incomplete visibility into their own team. Find out by asking, individually, what each person on your team has done with AI in the last month. The patterns will surface fast. You'll usually identify the driver within two or three conversations.

‍"How do I have the conversation with them without it feeling like I'm asking them to do my job?"

You're not. You're acknowledging what they've already been doing and offering them the institutional support to do more of it. Most people in their position have been waiting for this conversation. Leading with curiosity, not direction, is usually enough.

‍"Am I going to be exposed if I formalize their role?"

The opposite. Formalizing their role makes the work institutional rather than personal. That gives you credit as the leader who built the structure, not the leader who got lucky with one team member. The risk is in not formalizing, because then their work stays portable and your function stays dependent.

Where I can help

The Accidental Laggard's path forward has two tracks running in parallel. Backing the person who's been carrying the work, and building your own fluency fast enough to be a real partner to them. Both are real work, and most leaders try to do them in sequence rather than at the same time.

I work with TA leaders in your situation on getting both started in the same quarter. The work is practical: how to structure the conversation with your team driver, what to formalize and how, and how to build your own fluency in a way that's actually useful (not just busywork that lets you say you tried).

If you want to think through how to have the conversation with the person carrying this work, or how to build your own fluency without falling further behind, let's talk.