The conversation about AI adoption in businesses tends to focus on technology, strategy and outcomes. What gets much less attention is what employees experience during AI change and what they need from leadership to navigate it successfully.

​

This matters because most AI initiatives that fail do so not because of technical problems but because people don't engage with them. They resist passively, work around the new tools or simply wait for the initiative to pass. This isn't because employees are opposed to change. It's because their needs during change haven't been addressed.

​

In SMEs this dynamic is particularly visible. Everyone knows each other, communication is direct and resistance shows up quickly. Leaders who understand what employees actually need during AI change can address concerns before they harden into opposition. Leaders who don't find themselves pushing against quiet but persistent resistance.

​

The need for honest information about what's changing

​

The first thing employees need is straightforward information about what's actually changing and what's not. Not strategy presentations or vision statements but practical clarity about how their work will be affected.

​

In most SMEs this information arrives late or not at all. Leaders make decisions about AI adoption and announce them once everything is settled. By that point employees have already filled the information vacuum with assumptions, most of them worse than reality.

​

What happens in practice is that people hear the business is adopting AI and immediately jump to conclusions. They assume their jobs are at risk, their skills will become irrelevant or they'll be forced to work in ways that don't suit them. These fears aren't usually grounded in what's actually planned but nobody has given them better information.

​

This is where leaders often struggle. They think they're being responsible by waiting until they have complete answers before communicating. But employees don't need complete answers. They need enough information to understand what's happening and what it means for them specifically. Partial clarity is better than sustained uncertainty.

​

The mistake many businesses make is treating communication as something that happens after decisions rather than as part of decision-making. By the time employees are informed, they've already formed views and those views are hard to shift.

​

The need to understand why this matters

​

Employees need to understand not just what's changing but why it matters to the business. Not in abstract strategic terms but in concrete operational language that connects to their daily work.

​

In most SMEs leaders assume the business case for AI is obvious. Efficiency, cost reduction, competitive pressure. But these things aren't obvious to everyone. Someone in customer service or operations doesn't automatically see why AI adoption is urgent or how it helps them do their job better.

​

Without understanding why change matters, employees view it as an imposition rather than an improvement. They comply if required but they don't commit. They see change as something being done to them rather than something being done for the business they're part of.

What this requires from leaders is connecting AI adoption to outcomes employees care about. Not just company-level benefits but team and individual-level improvements. Faster response times mean less stress for customer service teams. Better data access means less time hunting for information. Automation of tedious work means more time for interesting problems.

​

These connections don't make themselves. Leaders need to explain them repeatedly and in different contexts until employees genuinely understand what's in it for them beyond just keeping their jobs.

[Diagram suggestion: connecting business outcomes to employee benefits at different levels]

​

The need for involvement not just consultation

​

Employees need to be involved in AI adoption in ways that give them genuine influence, not just consulted after decisions have been made. This is particularly important for people whose work will be directly affected.

​

In most SMEs consultation happens too late to matter. Leaders have already chosen tools, designed workflows and planned rollouts. They then ask for feedback on implementation details while the substantive decisions are fixed. Employees recognise this as theatre and respond accordingly.

​

Real involvement means including employees early enough that their input can shape what happens. It means asking them what problems need solving before choosing tools. It means letting them test options and voice concerns while changes can still be made. It means treating them as people who understand the work rather than obstacles to be managed.

​

This doesn't mean every decision is democratic or that employees have veto power. It means their knowledge and concerns inform the work rather than being acknowledged and then ignored. The difference is visible in whether employees feel their contribution mattered.

What makes this hard for leaders is that genuine involvement takes time and creates complexity. It's faster to make decisions centrally and announce them. But that speed creates resistance that slows everything down later. The businesses that move fastest overall are the ones that involve employees early even though it feels inefficient.

​

For more on the broader leadership requirements, see "Why AI adoption is a leadership challenge, not a technology project".

​

The need for time and space to learn

​

Employees need time to learn new ways of working without being expected to maintain full productivity throughout. This is obvious in theory but rarely honoured in practice.

​

What usually happens in SMEs is that AI tools are introduced and people are expected to learn them while doing everything else at normal pace. There's no reduction in workload, no protected time for practice and no acknowledgement that learning takes effort. People feel pressured to appear competent immediately rather than admitting they're still figuring things out.

​

This creates a predictable pattern. People avoid using new tools because using them well takes longer initially than doing things the old way. They stick with familiar methods even when they're supposed to be changing. Or they use new tools badly because they haven't had time to learn them properly, which reinforces the view that the tools aren't helpful.

​

Leaders create this problem by treating AI adoption as additional work rather than a change to existing work. They add new expectations without removing anything else. The implicit message is that AI should make people more productive immediately, which is rarely how change works.

​

What employees need instead is explicit permission to be slower or less productive temporarily while they learn. They need protected time to practice without business pressure. They need to be able to ask basic questions without seeming incompetent. And they need to see leaders acknowledge that learning takes time rather than pretending it's instant.

​

The need for reassurance about job security

​

The biggest unspoken concern during AI adoption is job security. Employees worry that AI will make them redundant even if leaders haven't said anything to suggest this. These concerns need to be addressed directly rather than left to fester.

​

In most SMEs leaders avoid this conversation because it feels uncomfortable or because they genuinely don't know what the long-term implications are. But avoiding it doesn't make the fear go away. It just means employees assume the worst and plan accordingly. They disengage emotionally, look for other jobs or resist change as a form of self-preservation.

​

What employees need is honest conversation about what AI means for employment. If jobs are secure, say so clearly and explain why. If roles will change but not disappear, explain what that looks like. If there's genuine uncertainty, admit it rather than offering false reassurance.

​

This is where leaders often struggle. They want to reassure people but they're not certain about the future themselves. So they say nothing and hope the issue resolves itself. It doesn't. Absence of information creates fear, not confidence.

​

The businesses that handle this well are the ones where leaders acknowledge uncertainty while being clear about intent. They explain that AI is being adopted to improve operations not reduce headcount. They commit to retraining rather than redundancy. They're honest about what they don't know while being clear about what they do.

[Diagram suggestion: addressing concerns progression from fear to engagement]

​

The need to see leaders engaging with the change

​

Employees need to see that leaders are engaging with AI change themselves, not just requiring it of others. When leaders are visibly using new tools, learning alongside teams and acknowledging difficulty, it legitimises the change and creates permission for everyone else to be imperfect.

​

In most SMEs there's a visible gap between what leaders ask of employees and what they do themselves. They introduce AI tools for customer service but continue using email the way they always have. They talk about efficiency but don't change their own workflows. The message employees receive is that AI matters for some people but not for everyone.

​

This undermines adoption in two ways. First, it signals that the change isn't really that important since leaders aren't participating. Second, it creates resentment that employees are being asked to change while leadership is exempt.

​

What employees need instead is visible leader participation. Not performative announcements but actual use of the tools and practices being introduced. Leaders asking questions about how things work, sharing their own learning and admitting when they get things wrong. This creates a culture where learning is acceptable and change is something everyone does together rather than something imposed downward.

​

The need for ongoing support not just initial training

​

Employees need support that extends beyond initial training into the messy reality of daily use. One training session doesn't create competence. People need ongoing help as they encounter situations the training didn't cover.

​

What usually happens in SMEs is that training happens once, usually right at the start. After that people are expected to figure things out themselves. When they struggle, they don't ask for help because they feel they should already know. They either muddle through ineffectively or they stop using the tools altogether.

​

This pattern is particularly common with AI because it's new enough that most people don't have peers who are expert. The person they'd normally ask for help is also still learning. So problems go unresolved and bad practices become embedded.

​

What employees need is accessible ongoing support. This doesn't mean formal helpdesk systems. It means someone they can ask when they're stuck, regular sessions where people share what they've learned and leaders who treat questions as valuable rather than as signs of incompetence.

​

The businesses that get this right create communities of practice where people learn from each other. They normalise asking questions and sharing solutions. They treat learning as continuous rather than as something that happens once at the beginning.

For broader context on creating supportive culture, see "Building an AI culture in a small or medium business".

​

What happens when these needs aren't met

​

When employee needs during AI change aren't addressed, the result is predictable but rarely acknowledged by leaders. People comply minimally but don't engage. They use new tools only when required and revert to familiar methods whenever possible. They wait for the initiative to fade rather than adapting to it.

​

This passive resistance is hard to counter once it's established because it's not visible as opposition. People aren't arguing or refusing. They're just not participating fully. And because leaders haven't understood what employees needed, they can't diagnose why adoption is failing.

​

The businesses that avoid this pattern are the ones that treat employee needs as central to AI adoption rather than as soft issues to be managed. They recognise that technical success without human engagement is still failure.

​

Practical takeaways for SME leaders

​

• Give employees honest information about what's changing as early as possible, even if details aren't final

​

• Explain why AI adoption matters to the business in terms employees can connect to their daily work

​

• Involve affected employees early enough that their input can shape decisions rather than just implementation details

​

• Provide protected time for learning and accept that productivity will dip temporarily during transition

​

• Address job security concerns directly rather than hoping they'll resolve themselves

​

• Engage visibly with AI change yourself rather than only requiring it of others

​

• Provide ongoing support beyond initial training, particularly as people encounter unexpected situations

​

Building trust through the change process

​

The common thread through all of these needs is trust. Employees need to trust that leaders are being honest with them, that their concerns matter and that the change is being handled thoughtfully rather than recklessly.

​

Trust isn't built through perfect execution. It's built through consistency between what leaders say and what they do, through acknowledging difficulty rather than pretending change is easy and through treating people as adults who deserve real information rather than as problems to be managed. The SMEs that adopt AI successfully are almost always the ones where trust between leadership and employees was strong before AI appeared or where leaders built that trust through how they handled the change.

​

 

Author: Sean Beynon Founder of beynon.ai and an experienced marketer helping UK SMEs adopt AI safely and practically, with a focus on leadership, governance and real-world implementation rather than technology theory.

​