Back to Insights
People & Culture  ·  8 min read

How to talk to your team about AI without causing panic

The conversation almost everyone gets wrong. What the evidence shows about AI and jobs, and what your team needs to hear from you instead.

Most owners would rather do almost anything than have this conversation with their team. They put it off, they bury it inside an all-hands about something else, they outsource it to HR, or they wait for someone to ask. None of these is the best way to handle it.

Your team is already having the conversation. They're having it with each other, with their partners, and on social media. They're reading the same headlines you are. Some of them are quietly anxious. Some of them are pretending not to be. A small number are genuinely excited. What none of them are doing is waiting for you to figure out what to say.

This piece is about how to have the conversation properly. Not because there's a perfect script, but because the cost of doing it badly is high. Good people leave businesses that handle this conversation badly. They stay at businesses that handle it well, even when the changes coming are significant.

Why is this conversation so hard for SME owners?

Three reasons, all worth being up front about.

The first is that most owners don't know what they think yet. The honest answer to "what will AI mean for our business in three years" is usually somewhere between "I don't know" and "probably less than the press is suggesting, but more than I'd like." That uncertainty is uncomfortable to broadcast. The temptation is to either under-claim certainty ("nothing's going to change here") or over-claim it ("this is going to change everything"). Both are wrong.

The second is that the conversation forces owners to admit they're thinking about their team's future without having a plan for it yet. Most owners don't like being in that position. They'd rather wait until they have answers. The problem is that the question is being asked now, with or without their answers.

The third is that the conversation has been polluted by other conversations. Every news article about layoffs, every viral LinkedIn post about replaced jobs, every CEO statement about productivity gains, all of it sits in the room with you when you start talking. Your team isn't listening to your words alone. They're listening through everything they've already heard.

The good news is that none of this means the conversation must go badly. It just means you need to walk in with a clearer view of what they're asking, and what an honest answer sounds like.

What does the evidence show about AI and jobs?

Before you say anything to anyone, know this: the evidence is more interesting than either the doomers or the boosters will tell you.

The most-cited studies all point in roughly the same direction. AI doesn't replace whole jobs in most cases. It replaces tasks. The tasks it replaces are usually the parts of a job that the person doing them would happily give up anyway: drafting, summarising, formatting, scheduling, generating first versions of things, reconciling data between systems. The parts that get harder, not easier, are the ones that require judgement, relationships, and accountability.

What that means in practice for an SME is that whole-role redundancy is rare, but role evolution is universal. The marketing assistant whose job in 2022 was 60 per cent producing content is still in post, but in 2026 they're producing four times the output with the AI doing most of the production and them doing most of the editing, judgement, and stakeholder management. They haven't been replaced. Their job has been re-weighted.

The honest exception to this pattern is the small number of roles that were close to pure production to begin with. Some junior copywriting work, some basic data entry, some first-line customer email handling. These are getting harder to justify as standalone roles. Not impossible. Just harder.

What this means for the conversation with your team is that you can be honest about all of it. The role-evolution story is more accurate than the role-replacement story, and it lands better because it's true.

What does your team want to hear?

In my experience, four things, in roughly this order.

The first is whether they still have a future at the company. Not "am I safe forever" but "do you see me as part of where this business is going." If they hear that, the rest of the conversation gets easier. If they don't, nothing else you say will matter much.

The second is whether you're being straight with them. People can tell the difference between an owner who's thought about this honestly and an owner who's reciting talking points. The detail of what you say matters less than whether you sound like you've actually grappled with it.

The third is what's expected of them now. Vague messages about "embracing AI" or "being curious" don't help. Specific messages about what changes in their day-to-day, what they're being asked to learn, and how their performance will be assessed in a year's time do.

The fourth is how you're personally treating this. If you're using AI tools yourself and being open about it, you signal that this isn't a thing you're imposing on them from above. If you're not, the message is mixed.

Notice what's not on this list. Reassurance that "nothing will change" isn't on it because they don't believe it. Heroic visions of a transformed business aren't on it because they're irrelevant to whether someone's job in customer support in six months still exists. Stories about other businesses aren't on it because they want to know about yours.

The thing you're tempted to say but shouldn't

"I want to assure you that no one's job is at risk." Don't say this. There are three problems with it. First, you probably can't honestly guarantee it. Second, your team knows you can't honestly guarantee it. Third, saying it shifts the conversation from "we're going to figure this out together" to "the owner just promised something the owner can't deliver." Better to say what you mean: that you're committed to working through this with them, that you'll be transparent about what you're learning, and that decisions about roles will be made openly rather than behind closed doors.

How should I structure the conversation?

This depends on the size of your team and the culture you've already got, but here's a structure that works for most SMEs in the 10-to-50-person bracket.

Start with what you've been thinking, not what you've decided. "I've been spending a lot of time over the last six months thinking about what AI means for our business, and I want to share where my thinking is." This signals genuine reflection rather than a corporate roll-out.

Be specific about what's changed already. Most teams have already noticed changes in the work, even if nobody's named them out loud. Name a couple. "I've noticed that the proposals we put together now take half the time they used to, because most of us are using Copilot or ChatGPT for the first draft." This validates what they already see.

Be specific about what's likely to change next. Don't speculate about ten years out. Talk about the next twelve months. "Over the next year, I think we're going to see more of our internal admin work move into automated workflows. That changes what the operations role looks like. It doesn't make it less important, but it makes it different."

Acknowledge what you don't know. "There are some questions I can't answer yet. I don't know exactly what the marketing function will look like in two years. I do know that the people doing it now are the people I want to be doing it then, and that's why I'm investing in training rather than waiting to see how this shakes out."

Tell them what you're asking of them. "What I'm asking of you over the next six months is two things. The first is to genuinely try the tools we're putting in front of you, not just go through the motions. The second is to tell me what's working and what isn't, because I'd rather hear it from you than figure it out the hard way."

Leave space for them to respond. Don't ask "any questions" at the end of a 30-minute monologue and treat one nod as consensus. Build in time for the conversation to become a conversation. If the room goes quiet, that's not agreement. It's discomfort. Ask one good question and wait.

What about the people who are worried?

Some will be. The right response isn't to talk them out of it. The right response is to take it seriously without amplifying it.

Three things help.

A one-to-one follow-up, not a group response. The people who are most worried will rarely say so in a group setting. They'll say so when they've got you for fifteen minutes in your office or on a walk.

Specific reassurance based on what you know about their role, not generic reassurance about "the team." If you know their role is genuinely changing and not disappearing, say that and describe what it looks like in a year. If you don't know yet, say that too, and tell them when you will know.

A concrete plan for them to develop, with your support. Not "go and learn about AI." Something like "I want you to spend two days over the next month working with Sarah to learn how she's using Copilot for the monthly reports. I'll book you on the training course we discussed. We'll review where you are in three months." Real investment in someone's development is the strongest signal you can send that you see them as part of the future.

So what should I do this week?

If you haven't had the conversation yet, three steps.

Spend an hour writing down what you think. Not what you'd say in a town hall. What you really believe about where this is going and where your business will be in two years. Most of the muddle in these conversations comes from owners not having done this work in private first.

Identify the two or three people on your team who'd be most affected by the changes you're seeing. Have a private conversation with each of them before any group conversation. They will appreciate the heads-up, and you will learn things that will improve the group conversation.

Hold the group conversation within the next month. Not a special event. Not a town hall. Something low-key that you signal is ongoing rather than one-off. "I want to spend half an hour at the end of next week's all-hands talking about how we're thinking about AI as a business, and I want to do that regularly from now on." Regularity is more important than performance.

If you've already had the conversation and it didn't go well, the fix is the same. Pretend you haven't had it. Start again with more honesty. Most teams are remarkably forgiving when an owner says, "I don't think I handled that conversation well last time, so I want to try again."

The point of this conversation isn't to resolve anything. It's to demonstrate that you're prepared to have it, that you're treating your team as adults capable of handling honest information, and that the decisions ahead will be made with them rather than to them.

Done well, this conversation is one of the most valuable hours an SME owner spends all year. Done badly, it costs you good people for reasons they'll never tell you.

Found this useful?

Take the free AI Readiness Diagnostic

The People & Skills dimension of the diagnostic gives you a structured view of where your team currently sits on AI capability, what they're worried about, and what a realistic development path looks like. It takes around 15 minutes and the report comes back within one working day.

Take the diagnostic →