AI and Job Security: How to Talk to Your Team About AI and Their Jobs

Talk to your team about AI and their jobs early, before rollout, and honestly. Say which tasks will change, what will not, how the business will support people and what it has not yet decided. Avoid promises you cannot keep. Then give staff a way to raise worries and a real part in shaping the change.

This is general information, not legal advice.

Why are employees worried about AI and their jobs?

Employees are worried because they hear that AI will replace work like theirs, and usually nobody at their own company has said otherwise. Silence lets people assume the worst. Worry is highest where businesses are changing the most, which is exactly where leaders most need their team's trust.

The worry is widespread. According to Pew Research Center's survey of 5,273 US workers, 52% are worried about the future impact of AI use in the workplace, and only 36% feel hopeful. A third say they feel overwhelmed, and 32% think AI will mean fewer job opportunities for them in the long run.

It rises with the scale of change. BCG's 2025 AI at Work survey found that employees at companies undergoing comprehensive AI-driven redesign are more worried about job security than others, 46% against 34%. So the more ambitious your plans, the more the conversation matters.

When should you talk to your team about AI?

Talk to your team before rollout, before training and before rumours fill the gap. The best moment is straight after leaders have agreed where AI fits and what it may touch, so you can speak specifically. If a change will significantly affect roles, consultation may also be a legal requirement.

Speaking early does not mean having every answer. It means telling people what has been decided and what has not, and when they will hear more. Staff cope far better with honest uncertainty than with discovering later that plans were made without them.

In Australia, the Fair Work Ombudsman explains that award consultation clauses generally require consultation when an employer "has decided to introduce major changes in production, programming, organisation, structure or technology that are likely to significantly affect employees". Employers must notify affected staff, discuss the changes, provide written information and consider their views, though consent is not required. Enterprise agreements must also contain a consultation term. Check the award or agreement that applies to your business.

What should you say to staff about AI and their jobs?

Cover six things: what is changing, what is not, what it means for roles, how the business will support people, what has not been decided yet, and how staff can raise concerns. Speak about tasks rather than jobs, and use examples from your own business rather than headlines about AI in general.

A simple structure for the announcement:

1. Why. What the business wants AI to help with, in plain terms.
2. Changing. The specific tasks AI will start helping with first.
3. Not changing. Work that stays with people, and the approval rule.
4. Roles. What this means for jobs, as honestly as you know it.
5. Support. Training, champions and time to learn.
6. Voice. How to raise worries, and who will answer.

The "not changing" part reassures more than any promise. Saying that a named person still approves everything sent to customers tells staff their judgement remains essential. The decisions behind it are covered in the guide to what only leaders decide.

What should you avoid saying?

Avoid promises you cannot keep, vague reassurance, threats and silence. "Nobody's job will change" is rarely true and staff know it. "Use AI or be left behind" frightens people into hiding mistakes. And saying nothing lets the most anxious person in the room set the story for everyone.

Be careful with headcount language too. If the plan is to grow without hiring as fast, say so plainly. Staff can accept that far more easily than a vague hint they have to decode.

How do you involve staff in the change?

Involve staff by letting them shape how AI is used in their own work: sorting their tasks into what AI can do, what needs checking and what stays human, naming a champion in each team, and writing down methods that work with credit to the person who found them. People resist change done to them, not change they help design.

Leadership support makes a measurable difference. According to BCG, the share of employees who feel positive about generative AI rises from 15% to 55% with strong leadership support. That support is felt through time to learn, honest answers and visible use by leaders themselves.

Champions keep the conversation going after the announcement, because colleagues raise worries with a peer they would never raise with the founder. The guide to choosing AI champions covers the role.

A hands-on team workshop turns the abstract fear into concrete, discussable tasks.

What if AI really does change roles?

Say so early, explain why, and show what the business will do: retraining for new work, time to adjust, and fair treatment if roles disappear. Follow any consultation obligations in your award or agreement. Treating people well in a hard change protects trust with everyone who stays.

Directors are expected to watch this. The Australian Institute of Company Directors' 2026 guide to AI governance covers "oversight of the human impact of AI on employees, customers and broader stakeholders". So a board should ask how staff are affected, not just what AI saves.

Where a role changes rather than vanishes, say which tasks shift and which judgement work grows. Where it does not, be just as honest. Any plan involving redundancy needs proper employment advice before anyone is told.

Skein offers adoption as one of three ways in, alongside strategy and implementation; the AI leadership page covers the decisions to settle before the announcement. That suits a founder who knows staff are worried and wants to say something honest. A business planning redundancies needs employment law advice first.

Frequently asked questions

How do you tell employees about AI without scaring them?

Be specific and early. Explain which tasks AI will help with first, which work stays with people, how staff will be trained and supported, and what has not been decided. Use examples from your own business. Specific, honest information calms people far more than broad reassurance or silence does.

Should you promise employees that AI will not replace their jobs?

Only if you are certain it is true, which is rare. A broken promise destroys trust. Instead, say which tasks will change, what you know about roles today, what you have not decided and when you will share more. Honest uncertainty is easier to accept than reassurance that later proves false.

Do Australian employers have to consult staff about AI?

Many do, when a change is major and likely to significantly affect employees. Award consultation clauses generally cover major changes in technology, and enterprise agreements must contain a consultation term. Consultation means notifying, discussing, providing information and considering views. Check the award or agreement that applies, and seek advice.

Why are employees afraid of AI?

Most fear losing their jobs or having their skills devalued, often because they hear dramatic headlines and nothing specific from their own employer. Surveys show many workers feel worried or overwhelmed about AI at work. Fear is usually highest where change is biggest and communication is weakest.

How can employees be involved in AI adoption?

Let each team sort its own tasks into what AI can do, what needs a person's check and what stays human. Name a champion in each team, run hands-on sessions on real work, and write down methods that work with credit to whoever found them. Involvement turns resistance into useful judgement.

Related reading