The Drift

The person on your team who agrees AI is important and still hasn't started

You know this person. They're on your team right now. They're good at their job. They hit their deadlines. When AI comes up in a meeting, they nod. If you ask them directly, they say the same seven words every time:

"Yeah, I know I need to spend more time with it."

Then they go back to their desk and do the work the way they've always done it. Not because they're against AI. Not because they're afraid of it. Because right now, today, the way they work is producing acceptable results and nothing in their environment is making the switch feel urgent enough to interrupt that.

This person is not resisting. They're drifting. And the drift is the quietest, most expensive failure mode in your entire AI rollout, because it doesn't look like failure at all. It looks like a steady performer doing solid work. Your dashboard doesn't flag it. Your manager doesn't name it. The person themselves wouldn't call it a problem. And every week it continues, the distance between them and the people who started three months ago gets wider in ways neither side can see.

Here's what makes the drift so hard to address: the Drifter's logic is completely rational.

They're not being lazy. They're protecting their throughput. They have weekly deliverables, SLA pressure, and a performance review that measures consistency and accuracy. Nobody is giving them protected time to learn. Nobody has shown them a low-risk entry point tied to their actual work. Nobody has made the cost of not starting visible. Inside their system, waiting is the smart move.

And the reasons they give are real. "I haven't had a clean use case yet." "I don't want to risk rework on something important." "I've seen a few demos but haven't had time to sit down with it." These are not excuses. These are rational decisions made inside a system that has never signaled, clearly and specifically, that this matters enough to interrupt the current workflow. The Drifter is doing exactly what the system is telling them to do: keep producing.

The problem is that the system is wrong. And it's wrong in a way that only becomes visible over time.

Something is happening on mixed teams right now that nobody is naming. Call it asymmetric awareness.

The person who started using AI three months ago knows they have an advantage. They can feel it. Their drafts come faster. Their questions in meetings are sharper. They're volunteering for projects they wouldn't have touched six months ago. They know, in a way they can't quite articulate, that something has shifted in how they work.

The Drifter suspects it. But they can't quantify it. They notice that their colleague is faster. They notice the quality is different. But because nobody talks about it openly, the suspicion stays vague. It doesn't convert into urgency. It converts into something worse: identity.

"I'm not one of the AI people."

That sentence, spoken or unspoken, is where the drift stops being a priority problem and becomes a Human OS problem. Because once someone has built an identity around not being in the game, the barrier to entry isn't learning a new capability. It's admitting they're behind. And that's a psychological cost that increases every single week.

The Drifter isn't falling behind because they made a bad decision. They're falling behind because they made no decision, and the math doesn't care.

So let's run that math.

An early adopter producing first drafts at 3x the speed of their pre-AI workflow is banking roughly 15 to 20 hours a month in recovered capacity. That's not free time. That's reinvestment time. They're using it to iterate, to ask better questions, to push into work they wouldn't have attempted before. They're building prompting intuition, learning where AI fails, and developing judgment about output quality. All of that compounds.

The Drifter is spending those same hours doing it the old way. Their output is fine. Their speed is the same as it was last year. They are, by every visible measure, performing. But they're performing at a fixed altitude while the person next to them is climbing.

After three months, the gap is noticeable. The early adopter is faster, more prepared, producing work with more options and more depth. After six months, the gap has changed shape. It's not just speed anymore. It's the quality of thinking. The early adopter isn't just doing the same work faster. They're doing different work. Better questions. Sharper synthesis. Projects that require the kind of judgment you can only build by doing the reps.

And here's the threshold that changes everything: at some point, AI stops being something the early adopter uses and becomes something their workflow is built around. Their process assumes it. Their speed assumes it. The way they prepare for meetings, the way they draft, the way they think about a problem before they touch it. All of it has been restructured around a capability the Drifter hasn't started building.

At that point, the Drifter isn't catching up to where the early adopter is. They're catching up to where the early adopter was three months ago. And the cost of catching up has tripled, because now it's not just learning something new. It's rewiring how they work, rebuilding their confidence, and admitting to themselves and their team that they waited too long. That's not a training problem. That's a canyon that opened one invisible week at a time.

What's Next

If you're a leader: the drift is happening on your team right now. You have people who agree AI is important and haven't started. Your dashboard doesn't show them because they're not counted as resistant. They're counted as "not yet active," which sounds temporary. It isn't. The gap is compounding, it's unmanaged, and it's unspoken. The question for this week: can you name the Drifters on your team? And what would change if you gave them thirty minutes of protected time, a low-risk use case tied to their actual work, and explicit permission to be slow at it?

If you're already in the game: you know someone who's drifting. You've watched them agree and defer. You've felt the asymmetric awareness. You might have stayed silent about it because it felt like it wasn't your place. This issue is for them. Forward it. Not as a lecture. As a door.

Next Tuesday: we've talked about the people who shrug and the people who drift. But there's a third group. The ones who've thought about it, weighed it, and decided no. They're not uninformed. They're not afraid. And some of them might be right. That changes everything about how you approach them.

See you then.

Q.

Know someone who's drifting? Forward this. They can find the rest at belowthesurface.anchor11.com