A quiet meeting does not prove your team is afraid of AI. A missed deadline does not prove it either. Workload, unclear priorities, fatigue, or a recent reorganization may explain what you are seeing.
But if AI is changing how work gets done and you avoid the subject because you cannot promise what comes next, your silence is part of the situation.
Imagine a manager sharing a new AI tool with the team. The response is muted. Work slows. The manager wonders whether people are tired or struggling with the workflow. Those are plausible explanations. So is uncertainty about what the tool means for the people expected to use it.
The manager may not know. That matters.
It is tempting to treat leadership as the ability to answer every question. If you cannot explain what the organization plans to do, or promise that roles will not change, you may decide the safest move is to keep the conversation focused on deliverables. You can keep work moving. You can avoid raising a concern you cannot resolve.
But avoiding a question does not make the question disappear. It leaves people to make their own sense of the changes, with whatever information they have and whatever fears they bring to it.
That does not mean every dip in performance is AI anxiety. It does mean you should not assume that a positive announcement and a link to a new tool are enough. For an employee, “This could save us time” and “What happens to my work if it does?” may be the same conversation.
You do not have to pretend that AI is harmless. You also do not have to declare that replacement is inevitable. Both claims offer a kind of certainty that you may not possess.
There is a harder answer: separate what you know from what you do not. Be clear about what has actually changed, what decisions are still pending, and what you can commit to doing next. If staffing decisions sit above you, say so. Do not imply you control decisions you cannot make. If you can bring questions to leadership, set a time to do that—and return with an update, even if the update is that there is no new answer.
Then ask what the change means for the work in front of the team. What tasks are being altered? What skills need practice? What would make experimentation useful rather than another demand added to an already full workload?
A conversation will not guarantee that people feel reassured. It may surface questions you cannot answer, or concerns you would rather not carry. And if you invite candor without following through, the conversation can feel worse than silence.
So do not promise comfort. Promise honesty about the limits of your knowledge, and follow-through on the parts you can influence.
Your team does not need you to manufacture certainty. It needs to know whether you are willing to face uncertainty with them—or whether they are expected to manage it alone while pretending nothing has changed.
