Should I tell my boss I'm anxious about AI?
A practical way to decide whether to raise AI anxiety with your manager, what to say instead of 'I'm anxious,' and a script for the conversation if you go ahead.
The question usually shows up the night before a one-to-one, not as "should I mention AI" but as "should I tell them what it's doing to me." Those are different questions, and mixing them up is what makes this feel riskier than it usually is.
Separate the feeling from the topic
You can raise AI at work without disclosing your anxiety about it, and you can manage your anxiety without ever raising it with your manager at all. Most people arrive at the question assuming it's one decision. It's two.
Raising the topic means asking your manager practical questions: which of your tasks the company expects tools to change first, what a pilot looks like, how success will be measured. This is a normal, even a good, thing to ask about. Nobody reasonable penalises an employee for asking where the rollout is headed.
Disclosing the anxiety means telling your manager how the uncertainty is affecting you — that it's costing you sleep, that you're finding it hard to concentrate, that you're scared for your role. This is a different kind of conversation, with different stakes, and it's worth deciding on purpose rather than blurting it out at the end of a meeting because the silence got uncomfortable.
You can do the first without the second. Many people who think they need to "tell my boss I'm anxious" actually need the first conversation, and the anxiety eases once they have real information instead of a vacuum.
What to disclose, if you disclose
The useful version of this conversation is specific and forward-looking, not a description of your inner state. Compare two openings.
"I've been really anxious about AI taking my job" tells your manager how you feel and gives them nothing to do with it. Most managers respond to this with reassurance they can't actually back up ("don't worry, you're fine") because they don't know what else to offer, and the conversation ends without changing anything.
"I want to make sure I'm developing in the right direction given where the team's using AI tools — can we talk about which parts of my role you expect to change, and what you'd want me to focus more on" tells your manager the same underlying concern, framed as something they can act on. It's honest. It just leads with the question that has an answer, rather than the feeling that doesn't.
If the emotional weight is heavy enough that you want your manager to actually know it's affecting you, that's a legitimate thing to say too — but it belongs in a sentence, once, not as the frame for the whole conversation. "This has been on my mind more than I'd like, so I wanted to ask directly" is enough. You don't need to narrate the 3am version of it at work.
Reading whether your workplace can hold this conversation well
Some managers and some cultures handle this well; some don't. A rough signal, before you decide how much to say: has this manager engaged seriously with other people's practical concerns before, or have concerns tended to get read as complaints? Is there any history of people being treated differently after raising a hard topic? You're not obligated to test this out on a guess — if you already know the answer, let it inform how much you disclose, not whether you're allowed to ask the practical questions at all.
What tends to go right
When this works, it's usually because the employee came with a specific, answerable question and left with something they could act on — a clearer sense of which of their tasks are changing, a request to be included in a pilot, or an explicit answer about what's valued going forward. The research on job insecurity is consistent that what wears people down is not the possibility of change but the duration of not knowing; a manager who gives you real information, even mixed information, usually reduces the load more than either silence or forced reassurance would.
What tends to go wrong
The version that backfires is open-ended and unspecific: raising the fear without a question attached, in a setting where the manager has no way to respond usefully, and leaving without anything concrete. That doesn't make you look bad so much as it leaves both of you stuck — you've said something true and gotten nothing back that helps.
A script, if you want one
"Can I ask you something about the AI rollout? I want to make sure I'm putting my energy in the right place. Which parts of my work do you expect tools to speed up first, and what would you want me spending more time on as a result?" Follow with whichever of these fits: "Is there a pilot group I could be part of?" or "How will we know if it's working?" or, if you want to name the weight of it once, "This has been on my mind more than I'd like, so I wanted to ask directly rather than guess."
Write down the answers the same day. In a month, reread them against what actually happened. That turns a vague "they're replacing us" into something you can check — which is most of what this conversation is for.
If you decide not to tell them
That's a reasonable call too, especially if you don't trust the workplace to hold it well, or if the anxiety is being managed fine on your own. Not disclosing doesn't mean not asking. You can still request the practical conversation — which tasks, what pilot, what's valued — without ever using the word anxious. The information helps either way; the disclosure is optional.
Frequently asked
Should I tell my manager I'm anxious about AI taking my job?
You can separate this into two decisions. Asking practical questions about the AI rollout — which tasks are changing, whether there's a pilot, what's valued going forward — is worth doing regardless. Disclosing the anxiety itself is optional and depends on whether you trust your manager and workplace to handle it well; if you do disclose, one honest sentence is usually enough, attached to a specific question rather than replacing it.
What should I say to my boss about AI instead of 'I'm anxious'?
Lead with a question that has an answer: which of your tasks they expect tools to change first, whether there's a pilot you could join, and what they'd want you focusing more time on. This gives your manager something to act on, which tends to reduce the uncertainty more effectively than a description of how you feel.
Will bringing up AI anxiety at work make me look weak or replaceable?
There's no research showing that asking practical questions about a rollout damages how employees are seen; most managers read specific, forward-looking questions as engagement. The version that tends to land badly is open-ended and unspecific, without a question attached, in a setting where the manager can't do anything with it.
What if my workplace isn't safe to talk about this in?
Then ask the practical questions without the disclosure. You can request the same information — which tasks are changing, what's valued — without naming your anxiety at all. If your read on the culture says disclosure carries real risk, trust that read; the information is still worth getting.
Sources
- De Witte, H. (2005). Job insecurity: Review of the international literature on definitions, prevalence, antecedents and consequences. SA Journal of Industrial Psychology, 31(4), 1–6.
- Sverke, M., Hellgren, J., & Näswall, K. (2002). No security: A meta-analysis and review of job insecurity and its consequences. Journal of Occupational Health Psychology, 7(3), 242–264.
- Wrzesniewski, A., & Dutton, J. E. (2001). Crafting a job: Revisioning employees as active crafters of their work. Academy of Management Review, 26(2), 179–201.