Why Smart Teams Don't Adopt AI on Their Own

I was listening to a podcast recently where the host asked how AI would change things for product managers, engineers, and designers. The audience was largely PMs and product leaders, and you could feel the anxiety through the questions. How will my role change? Will I still be needed? What does this mean for my career?

Every single question was about the job title. Not one was about the results.

This is a pattern I see constantly. When AI comes up, the default reaction is territorial. People map the threat to their identity and start building walls around it. The operations manager worries about the operations role. The sales lead worries about the sales role. The accountant worries about the accounting role.

The tragedy is that this instinct — which feels like self-preservation — is actually the thing most likely to make them irrelevant.

The people who thrive don't defend territory

I don't think of myself as having a job title to defend. I care about getting certain results. And if how I get those results needs to change, great. I've never been happier. Less of the work I hate doing needs to be done, and more of the work I enjoy gets to be done.

But when I talk to teams inside companies, I hear the opposite. People who see AI not as an opportunity but as a threat to their identity. They don't say it that directly — it comes out as thoughtful-sounding objections. "That won't work for our use case." "Our processes are too complex for AI." "We tried something like that and it didn't work."

Sometimes those objections are legitimate. Sometimes they're identity defense dressed up as analysis.

This isn't a character flaw — it's an incentive problem

Before you blame your team for being resistant, understand why this happens.

Most employees don't eat what they kill. Their incentive isn't to get the best possible result. Their incentive is to not get fired. When the path to not getting fired has been "be really good at this specific set of tasks," anything that threatens those tasks feels like a direct threat to their livelihood.

They're not being irrational. They're responding to the incentive structure that exists in most organizations.

Your operations team has spent years getting good at the current way of doing things. They know the tools, the workarounds, the quirks. That knowledge is their value. When you suggest that AI could handle parts of their work, you're not asking them to try a new tool. You're asking them to devalue the expertise they've built their career on.

That's a big ask. And it explains why adoption doesn't happen from the bottom up.

The loom analogy

Think of a skilled basket weaver in the era just before the mechanical loom.

This person is a craftsperson. They take pride in the weave, the tension, the artistry of doing it by hand. Their identity is wrapped up in the act of weaving.

Then the loom arrives. The job isn't weaving anymore. The job is operating looms to produce textiles. The output is the same — maybe better. But the craft is gone. The hand skill that defined this person's professional identity is no longer the thing that matters.

Some weavers looked at the loom and thought: "I can produce ten times as much now. This is incredible." Others resisted as hard and as long as they could — because what they loved was never the output. It was the process.

You see this exact split playing out across every function in every company right now. The people who define themselves by outcomes are thriving. The people who define themselves by how they do the work are struggling.

What this means if you're running a company

The people who will be most valuable to you in the next two years are the ones who define themselves by results rather than activities.

When you're hiring, stop asking "how do you approach [task]?" and start asking "tell me about a time the best path to a result required you to completely change how you work." Look for people who care more about the destination than the vehicle.

When you're managing your existing team, watch for the territorial signals. The person who pushes back on AI tools isn't always being thoughtful. Sometimes they're defending hand-weaving. The person who says "that's not how we do things" might be telling you something important about quality — or they might be telling you their identity is threatened. Your job is to figure out which.

And when you're looking in the mirror, ask yourself the honest question: are you chasing results, or are you defending your own role? CEOs aren't immune to this. The CEO who says "I'm an operations person" might resist letting AI handle operations. The CEO who says "I know my business better than any machine" might resist admitting that AI can process their data faster and more consistently than they can.

It comes down to one question

The thing that separates the people who will thrive from the people who won't isn't talent or experience. It's whether they define themselves by what they produce or by how they produce it.

In a world where the "how" is changing every six months, you'd better be anchored to the "what."

The companies that figure this out early — that build cultures where results matter more than process, where the best idea wins regardless of whether a person or a machine came up with it — will operate at a fundamentally different speed than the companies that don't.

And the gap compounds quickly.