The Operations Bridge

Point four in the AI Strategy Points series. We just talked about the difference between end users and builders. This post is about the fear that sits underneath a lot of AI conversations, and why I think it’s aimed at the wrong target.

The fear people voice, and the risk that’s actually closer

People won’t lose their jobs to AI — yet. They’ll lose their jobs to people who adopt AI. I’ve said this line in enough rooms to know it lands differently depending on who’s listening, and I think that difference in reaction tells you something important.

The fear I hear most often is direct replacement: the AI does my job, and I’m no longer needed. That’s a real long-term risk in some roles, and I won’t pretend otherwise. But it’s not the risk that’s closest to most people right now.

The nearer risk is competitive: a colleague who has learned to use AI well is now meaningfully faster, more thorough, or more capable than a colleague who hasn’t. Over time, that gap compounds. It’s not that the slower person gets replaced by a machine — it’s that they get outcompeted by a peer who has a machine helping them.

This reframe changes what leaders should actually do

If the real near-term risk is adoption gap rather than automation, the leadership response looks different. It’s not primarily about protecting jobs from machines — it’s about making sure your people aren’t left behind by their own peers, inside or outside your organization.

That means treating AI fluency the way you’d treat any other core skill gap: naming it directly, offering real practice time rather than a single training session, and being honest that this is now part of staying competitive in the role, not an optional extra.

Avoiding the trap of false reassurance

I’ve watched leaders try to calm anxiety by promising “AI will never replace you,” which is a comforting sentence and an unreliable one. I’d rather be honest: I don’t know exactly what the next five years hold for every role. What I do know is that the people who spend the next year building real fluency with these tools will be in a stronger position than the people who wait to see what happens.

That’s not a guarantee. It’s a bet, but it’s the same kind of bet I made years ago adopting ChatGPT early, and it’s paid off enough times that I trust the logic behind it.

A question for leaders

Among your team, who has genuinely built fluency with these tools, and who is still waiting to see if this is a passing trend? What is that gap going to look like in eighteen months if nothing changes?

Next: AI will make smart people genius and average people smart — and what that actually means for how you develop your team.