(And How to Manage Each One)
You’ve been in the meetings. Someone on your team won’t stop talking about the latest AI prompt they discovered on TikTok over the weekend. Someone else hasn’t opened ChatGPT once. And somewhere in between, the rest of your team is trying to figure out where they stand.
After delivering AI workshops to dozens of executive teams, we’ve identified four distinct employee personas when it comes to AI adoption. Every organization has all four. The ratio varies, but the cast of characters doesn’t.
Understanding who’s in each camp — and managing them accordingly — is one of the most practical things you can do as a leader right now.
TL;DR
| Persona | Key Trait | Biggest Management Mistake |
|---|---|---|
| The Evangelist | First to adopt, loudest to promote | Letting them run unsupervised — enthusiasm without guardrails creates risk |
| The Explorer | Curious but waiting for direction | Failing to provide structured training — their curiosity expires without a path |
| The Pragmatist | Skeptical but persuadable with proof | Dismissing their concerns — they influence peers more than you think |
| The Objector | Principled resistance, not laziness | Trying to convert them — forced adoption destroys trust across the entire team |
1. The Evangelist
Profile: First to try every new tool. Subscribes to 14 AI newsletters. Has already built a custom GPT for something you didn’t ask them to build. Uses phrases like “this changes everything” at least twice a week.
What they get right: Evangelists are your early warning system. They surface tools and use cases that would take months to discover through formal channels. Their enthusiasm is contagious and can shift organizational momentum.
The risk you need to manage: Evangelists can move faster than your governance can keep up. They may feed proprietary data into unsanctioned tools, bypass procurement, or oversell capabilities to clients and colleagues. Enthusiasm without guardrails is a liability.
How to manage The Evangelist:
- Channel the energy, don’t cap it. Give them a formal role — AI scout, internal tester, workshop facilitator. Structure turns recklessness into reconnaissance.
- Make them your pilot program. Let them test tools, but with clear boundaries: approved data sets, defined use cases, reporting requirements.
- Require them to teach. Nothing sharpens understanding like having to explain something to a skeptical peer. Make their insights useful to the broader team.• Set the guardrails early. Acceptable use policies, approved tool lists, and data handling rules aren’t bureaucracy — they’re what allow Evangelists to move fast without breaking things.
2. The Explorer
Profile: Curious but measured. They’ve tried a few AI tools — maybe used ChatGPT to draft an email or summarize meeting notes. They see the potential but want more guidance before going deeper. They’re the ones asking thoughtful questions in your all-hands meetings.
What they get right: Explorers represent your most scalable asset. They’re open, coachable, and tend to adopt tools in ways that are practical and sustainable. They won’t overpromise and they won’t resist.
The risk you need to manage: Explorers stall without direction. If you don’t provide a clear path — training, tools, expectations — their curiosity fades into passivity. They’ll default to old workflows because nobody showed them the new ones.
How to manage The Explorer:
- Invest in structured training. Not a one-off webinar. Ongoing, role-specific education that shows them how AI applies to their job, not the generic concept of AI.
- Pair them with Evangelists. Let the energy of the early adopters pull Explorers forward. Buddy systems and internal demos work better than vendor presentations.
- Celebrate small wins. When an Explorer uses AI to cut a report from 3 hours to 45 minutes, make sure the team knows about it. Proof of value converts curiosity into habit.• Remove friction. Pre-approve tools, create prompt libraries, build templates. The less an Explorer has to figure out on their own, the faster they integrate AI into their workflow.
3. The Pragmatist
Profile: Arms crossed, but listening. They’ve heard the hype before — blockchain was going to change everything too, remember? They need to see the ROI, the security audit, and the use case that directly solves a problem they actually have. They’re not opposed to AI. They’re opposed to wasting time.
What they get right: Pragmatists are your quality filter. Their reluctance forces you to build better business cases, tighter processes, and more rigorous evaluation criteria. Every tool that survives a Pragmatist’s scrutiny is probably worth deploying.
The risk you need to manage: Pragmatists can become organizational bottlenecks if their skepticism is left unaddressed. They influence peers. A vocal Pragmatist who feels ignored will quietly slow adoption across their entire team.
How to manage The Pragmatist:
- Lead with data, not demos. Show them measurable outcomes from comparable companies or internal pilots. Time saved. Errors reduced. Revenue influenced. They don’t care about what’s cool — they care about what works.
- Involve them in evaluation. Put them on the selection committee. Let them stress-test the tools. When they approve something, it carries more credibility than any executive mandate.
- Acknowledge their concerns are valid. Because many of them are. Security, accuracy, job impact — these aren’t irrational fears. Dismissing them guarantees entrenchment.
- Don’t rush the timeline. Pragmatists convert when they’re ready, not when you’re ready. Steady exposure, honest reporting on what works and what doesn’t, and patience will get them there.
4. The Objector
Profile: Their resistance isn’t about laziness or fear of technology. It’s principled. They have genuine concerns about AI ethics, data privacy, job displacement, intellectual property, or the societal implications of automation. They may be your most thoughtful employee in the room.
What they get right: More than you might think. Objectors often see risks that Evangelists and even Explorers miss entirely. They ask the hard questions about bias in AI outputs, about what happens to the roles that get automated, about whether your clients are comfortable with AI-generated deliverables. These are questions your organization needs someone asking.
What not to do: Don’t try to convert them. Seriously. Forced adoption of a tool that conflicts with someone’s core values creates resentment, not productivity. And the moment you make AI adoption feel like a loyalty test, you lose trust — not just with the Objector, but with everyone watching how you handle dissent.
How to manage The Objector:
- Respect the position. You don’t have to agree with it. But you do have to acknowledge that ethical objections to AI are legitimate and widely shared — including by researchers, regulators, and entire industries.
- Find their value in the conversation. Objectors make excellent members of AI ethics committees, policy review boards, and risk assessment teams. Their perspective strengthens governance. Use it.
- Define the non-negotiables clearly. Be transparent about what’s required for their role versus what’s optional. If a specific AI tool becomes essential to their function, have that conversation early, directly, and with empathy.
- Don’t isolate them. The worst thing you can do is make the Objector feel like the last person picked for the team. Include them in discussions. Value their dissent. Organizations that silence internal critics tend to make the biggest external mistakes.
The Real Job Is Managing the Mix
No executive has a team of all Evangelists or all Objectors. You have all four, often sitting in the same meeting, reacting to the same AI initiative in completely different ways.
The mistake most organizations make is treating AI adoption as a single, uniform rollout. One training. One mandate. One timeline. That approach guarantees you’ll only reach the people who were already on board.
The better approach: recognize the personas, tailor the management strategy, and accept that a healthy organization will always have a diversity of perspectives on emerging technology. That’s not a problem to solve. It’s an advantage to leverage.
