What Changed This WeekReviewed 25 July 2026

How to Talk to Your Team About AI Anxiety

A useful conversation separates today's work changes from forecasts, acknowledges what management cannot promise and ends with specific next steps.

WorkChanged editorial deskSource-led research and synthesis
Published
25 July 2026
Reviewed
25 July 2026
Next review
25 October 2026
Reading time
9 minutes
Manager listening to a small team during an open, calm discussion about changing tasks and AI
On this page

Answer First

The practical answer

Do not begin by telling people not to worry. Explain what technology is actually being considered, what decisions have and have not been made, and how staff will influence the work design. Invite questions without demanding personal disclosure, correct unsupported rumours, and commit to a dated next update. If someone is struggling with their mental health, use appropriate support rather than treating a group discussion as care.

Who This Affects

Use this guide if any of these describe you

  • Managers hearing concern about job loss or deskilling
  • Teams exposed to automation claims or AI pilots
  • Employees unsure whether to disclose anxiety
  • People leaders planning change communications

Evidence Strength

Emerging

Editorial format

Guide

Portfolio role

Timely interpretation

Key takeaways

  • Anxiety is not evidence of resistance or lack of digital skill.
  • Task-level facts are more useful than sweeping predictions about jobs.
  • The conversation needs a decision, support or next update, not only empathy.

Prepare the facts and boundaries

List the tool, intended task, pilot stage, data involved, people affected and decisions still open. Separate external forecasts from your organisation's plan.

The ILO estimates exposure by tasks and finds large differences within occupations. Use that evidence to avoid turning exposure into a claim that a named person or job will disappear.

Use a calm opening

Try: We are assessing this tool for these tasks. No decision has been made about these areas. I want to hear which risks and opportunities you see, and I will update you on this date.

Ask about work effects, not whether people are anxious in front of colleagues. Provide private channels and make clear that raising a risk will not damage someone's standing.

Respond without false reassurance

Where you know the answer, give it. Where you do not, name the owner and date. If roles could change, explain the process and what support is being designed rather than promising no jobs will be affected.

Record recurring questions and answer them consistently. Correct both inflated capability claims and casual dismissal of genuine risk.

Know the support boundary

A manager can improve work clarity and signpost employee assistance, occupational health, union or healthcare support. A team meeting is not therapy and managers should not diagnose individuals.

If monitoring, selection or employment decisions are involved, include HR, privacy and legal expertise for the relevant jurisdiction.

What To Do Next

A practical sequence for the next seven days

  1. 01

    Prepare a one-page fact, decision and unknowns brief.

  2. 02

    Open with the specific task under review rather than AI in general.

  3. 03

    Offer both group and private routes for questions.

  4. 04

    Assign every unanswered material question an owner and date.

  5. 05

    Follow up in writing with decisions, support routes and the next update.

Related profession guidance

See how this reaches the work you do

Sources

Read the evidence behind this guide

  1. Original research20 May 2025
    International Labour Organization: Generative AI and Jobs: A Refined Global Index of Occupational Exposure
  2. Primary report26 January 2023
    National Institute of Standards and Technology: Artificial Intelligence Risk Management Framework (AI RMF 1.0)
  3. Primary report11 July 2023
    Organisation for Economic Co-operation and Development: OECD Employment Outlook 2023: Artificial Intelligence and the Labour Market

Reviewed and updated

Change log

  1. First publication, checked against the listed primary sources.

A focused return path