top of page

How Do We Introduce AI Without Undermining Employee Trust?

Oct 26
4 min read

By Laricelle Fouchee, Fouchee Mediation


AI in the workplace. Better communication with employees. Laricelle Fouchee of Fouchee Mediation.

“How do we introduce AI when employees are worried about what it means for their jobs?” Explain the purpose, discuss how the work may change, involve the people affected and be honest about what remains undecided. Give employees training, clear boundaries and a credible way to challenge problems. Trust depends on what happens after the announcement as much as on the announcement itself.


For HR professionals and leaders, an AI project can bring competing pressures. A business wants to reduce repetitive work or improve service. Employees want to know whether their judgement still matters, how their performance will be assessed and whether the organisation is preparing to reduce headcount.


Those questions deserve a response before assumptions fill the gap.


Why the employee conversation about AI matters now


CIPD’s responsible AI adoption resources, published in September 2026, bring together research and case studies exploring AI as a people and organisational challenge. The materials address employee involvement, job design, governance and skills planning.


For workplace leaders, that provides a useful starting point. Choosing a tool is one decision; preparing people to use it fairly and effectively is another. An organisation can have a clear technical plan while still leaving employees uncertain about their own responsibilities.


Explain the problem you are trying to solve


“We need to embrace AI” does not tell a team what will happen on Monday morning.


Be concrete. Are you testing a tool to summarise routine enquiries, help draft documents or make information easier to find? Which tasks are included, and which remain outside the trial?


Explain why the organisation is considering the change and what evidence would show that it is helping. Include quality, customer impact and employee experience alongside speed. If the proposal is still exploratory, say so rather than presenting an experiment as a settled direction.


Answer the question beneath the question


An employee asking whether a tool is reliable may also be asking whether they will be blamed for its mistakes. Someone who challenges productivity claims may be concerned that a faster process will simply bring a larger workload.


Ask: “What concerns you most about how this could affect your work?” Then allow time for an answer beyond the technical features.


Do not dismiss questions as resistance. Employees may identify risks that the project team has missed. Equally, do not assume every concern is anxiety about job security. Listen for the particular issue before deciding how to respond.


Be honest about roles and uncertainty


Avoid promises that the organisation cannot support. “No jobs will ever be affected” may feel reassuring in the moment but can damage credibility if circumstances change.


Describe what has been decided, what has not, who will make further decisions and when employees will receive an update. Where workforce changes are being considered, involve HR and follow applicable information and consultation requirements.


If a question cannot yet be answered, give a reason and a date for returning to it. Repeated silence can be interpreted as a decision that leaders are unwilling to explain.


Involve employees in designing the trial


Imagine a customer service team testing AI-generated replies. Leaders expect shorter handling times. Advisers discover that some replies take longer to check because the suggested wording misses an important nuance.


If the trial measures only how quickly a draft appears, that experience may be overlooked. Ask employees to help identify the measures, common failure points and tasks that still require particular care.


Create a straightforward way to report concerns. Make clear that reporting a problem will help assess the tool, rather than be treated as evidence that the employee is reluctant to learn.


Clarify responsibility before something goes wrong


Employees need practical guidance on approved tools, permitted uses and the information they may enter. Coordinate this with the organisation’s data protection, security and other relevant specialists.


Explain who checks an output, who can authorise its use and how an error should be escalated. “Use your judgement” is not enough if people do not know the limits of the system or the standard expected.


Keep important employment decisions subject to appropriate human scrutiny. Where AI informs a decision affecting someone, provide an understandable route for raising questions and obtaining a meaningful review.


Make training part of the workload


A demonstration is not the same as confidence. People may need time to practise, compare outputs and understand when the tool should not be used.


Agree how learning will fit into working hours. Review whether checking and correcting outputs creates additional work, and avoid assuming that all time saved becomes immediately available for other tasks.


Watch for unfair comparisons between employees with different access, training or responsibilities. Set expectations that reflect the work actually being done, rather than the tool’s advertised capabilities.


Address tensions before they become personal


AI adoption can create friction between colleagues. Some may feel others are taking shortcuts; others may feel criticised for experimenting. Managers may interpret caution as obstruction.


Bring the conversation back to agreed standards: what tools are permitted, what checking is required and how concerns should be raised. Discuss the work rather than labelling people as enthusiastic or difficult.


Where disagreements have damaged relationships, voluntary workplace mediation may help people rebuild communication. It does not replace proper consultation, governance or specialist assessment of the technology.


Keep the conversation open


Review the trial with employees as well as project sponsors. Explain what feedback changed, what remains unresolved and what will happen next. If you decide to proceed despite a concern, explain the reasoning and safeguards.


Employees do not need to agree with every proposal to contribute constructively. They do need to see that their experience is being considered and that responsibilities are clear.


I offer workplace mediation and conflict coaching for organisations in Durham and surrounding areas. If organisational change has created tensions within your team, we can discuss whether independent support could help people move forward.



Sources and further reading



Comments


bottom of page