Your expertise just became a project
The request sounds harmless. Record your screen. Explain the awkward cases. Write down the steps you normally carry in your head. Help the new AI tool learn how the team works.
Then the obvious question lands: am I helping build something that makes my own job disappear?
You deserve a straight answer. Start by asking what the company plans to change. A vague promise that everyone will do more valuable work tells you nothing about your next pay cheque, workload or place in the team.
What does “train the AI” actually mean?
Ask the project owner to describe the task without the sales pitch. You might be writing instructions for colleagues, adding documents to a searchable knowledge base, testing an assistant or helping automate a complete process. Those activities can affect your work in different ways.
Uploading a procedure does not necessarily mean an AI provider is changing its underlying model. The employer could be giving an existing system information to use when answering questions or completing tasks.
Get a concrete example: what will the system do on its own, what will it suggest and where must a person approve the result? A demo that drafts an email is a different commitment from a system authorised to send it to a customer.
Data privacy does not settle job security
Anthropic’s commercial data policy says inputs and outputs from products such as Claude for Work and its API are not used to train its models by default. It describes exceptions when customers provide feedback or choose to allow that use. Consumer plans have a separate policy.
That policy concerns the provider’s model training. Your employer can still use an AI tool to redesign its own workflow. Ask your company which account, settings and approved data rules apply to the project.
“The vendor does not train on our data” leaves your staffing question unanswered. Bring the conversation back to the work being moved and the people expected to do what remains.
The fear is real. The outcome is still unknown
In research published by Adaptavist in November 2025, 35% of surveyed knowledge workers reported holding back knowledge because they feared being replaced. Attest surveyed 4,000 knowledge workers in the UK, US, Canada and Germany in August 2025.
That was a survey of reported attitudes, commissioned by a technology consultancy. It does not establish that those workers were later replaced or that your employer has decided to cut your role.
If the fear has spread beyond this project into everything you do, read our guide to AI job anxiety and fear of becoming obsolete. For this conversation, focus on the specific request sitting in your inbox.
Watch the staffing decisions
A documentation request on its own gives you limited information. It deserves closer attention when the team also stops replacing leavers, transfers your main responsibilities or sets a final handover date without explaining your next assignment.
Look for decisions you can verify. Has a vacancy been cancelled? Has your manager confirmed a smaller team? Does the project brief promise to remove roles, or does it promise to reduce a backlog? Record the wording and date in a place your employer permits.
Several changes together justify direct questions. They still cannot tell you which person will lose a job. Avoid turning office rumours into a personal countdown.
Ask who owns the work afterwards
Try this in your next meeting: “Once this system is running, which responsibilities will stay with me, and who will own the decisions it cannot handle?”
Listen for a defined role, a manager and actual work. “You will be more strategic” needs a follow-up. Ask which decisions, customers or projects that means and when the new responsibilities start.
Ownership matters because someone will have to handle mistakes, changing rules and cases the demonstration never covered. Find out whether that person is you, another team or a supplier before you agree to an open-ended support role.
Put the headcount question on the table
A calm, specific question is enough: “Does the approved plan assume fewer positions, fewer contractor hours or no replacement hiring after this goes live?”
Your manager may not know. Ask who can answer and when the staffing plan will be reviewed. Keep “not decided” separate from “no cuts planned.” They mean different things.
If you receive reassurance, ask what it covers. It could describe the pilot team this month while leaving the wider rollout undecided. You need the scope of the answer as much as the comforting words.
Here is what a useful answer looks like
Consider a fictional example. Nadia handles customer billing problems. Her manager asks her to teach an assistant how to answer routine questions. The initial explanation is that AI will free her for harder work.
Nadia asks what that work includes. The manager identifies disputed charges and complex account changes, names the team that will receive routine enquiries and confirms that Nadia will review failures during a six-week pilot. They also agree to review her workload before a wider launch.
That answer gives Nadia something she can check. It does not guarantee her job. If the manager cannot identify any responsibilities beyond the handover, Nadia has a clear reason to keep asking and prepare other options.
Make room for the project
Explaining years of work takes time. So does checking whether the system followed the instructions correctly. If your normal targets stay untouched, the AI project can become a second job squeezed into the first.
Set out the trade-off plainly: “The testing and documentation need six hours this week. Which existing deadline should move so I can do that properly?” Use your actual estimate, then adjust it as the work becomes clearer.
Agree who handles maintenance after launch. A project can finish on paper while you keep fixing the outputs every afternoon. Our guide to the AI productivity trap covers what happens when the promised time savings turn into higher targets.
Make your contribution visible
Ask for your project work to appear in the agreed goals and performance review. Describe what you built, which decisions required your judgement and what changed after testing. Use approved measures that show quality as well as speed.
A wider role also deserves a conversation about title, training, pay and authority. You can ask for those terms without claiming that taking part automatically earns a promotion.
Keep evidence in approved company systems and retain only records you are entitled to keep. A future CV can explain your contribution without customer files, confidential prompts or internal financial data.
Do not let the demo hide the failures
Make unusual cases part of the test. A system that handles a clean example can still struggle when information is missing, instructions conflict or a customer needs an exception.
Record the failed task and its effect in the project’s normal reporting process. Explain who had to correct it and how long that took. Stick to what happened; a dramatic prediction will weaken useful evidence.
Deliberately giving the system bad instructions can damage customers, colleagues and your own position. Raise concerns openly through the appropriate project, security or employee channels. Your strongest contribution is an honest account of what the system can handle.
Prepare for a role change
Ask for training that connects to a named responsibility the company expects to fund. A course badge is thin comfort if nobody can explain where the new skill will be used.
Update your CV while your recent achievements are easy to remember. Check outside roles against your actual skills and arrange conversations before a rushed announcement leaves everyone chasing the same openings.
If the rollout becomes a formal restructuring and staff must compete for new positions, use our guide to reapplying for your own job. That is a separate selection process, with its own criteria and deadlines.
Quiet Power: send the recap
After the meeting, send a short recap through your normal work channel. Confirm the agreed deliverable, time allowance, responsibility after launch and the date of the next staffing discussion. Invite your manager to correct anything you misunderstood.
Keep it factual. You are making the work clear enough to manage. A written recap also makes it harder for an unresolved question to disappear behind another upbeat project update.
Check your risk beyond the AI project
Start with the free Job Threat Check to review the warning signs around your own role. Use it to identify questions worth raising; it cannot reveal a confidential staffing decision or promise that your job will survive.
Look up your employer in the Layoff Tracker and Corporate Stress Index for public company signals where coverage is available. Compare that wider picture with the project and hiring decisions you can verify inside your team.
Follow the Weekly Layoff Intelligence Report to keep up with layoffs, restructuring and pressure on workers. It gives you a regular reason to review your options before a handover turns into a hurried job search.
The Grind Hotline Read
A company asking for your knowledge should be able to explain the project it wants you to build. Press for clear responsibilities, paid working time and an honest answer about staffing.
You can cooperate with the work and still ask where it leaves you. Curiosity about your own future is a reasonable response when someone starts redesigning your job.
Sources and context
Sources were checked on September 5, 2026. The Adaptavist findings describe August 2025 survey responses. The commercial privacy policy concerns provider data use. Neither source predicts an individual worker’s employment outcome. Nadia’s scenario is fictional and illustrates the questions in this guide.
About The Grind Hotline
The Grind Hotline is an independent, two-time award-winning business podcast and worker-first media platform covering layoffs, restructuring, AI pressure and workplace survival in plain English. Its reporting and free tools reach readers in more than 100 countries.
Its awards include the 2026 dotCOMM Platinum Award for Content Strategy, confirmed by the official dotCOMM winner record, and 2026 MUSE Creative Awards Silver for Branded Content, Cause/Awareness, confirmed by the official MUSE winner record.
The Host brings nearly two decades of corporate and commercial experience as an ex-banker, former Fortune 100 and Fortune 500 global sales leader, author, entrepreneur and corporate-survival strategist.
After losing his job twice in five years, The Host built The Grind Hotline. One layoff came at 7:30 in the morning. He is also the founder of CallTeam, a B2B outbound calling and sales-execution company.
For individual support, explore Layoff Career Counselling. Read our Media and Editorial Standards.
Important Disclaimer
This article provides general workplace information and career strategy. Employment duties, data rules and rights depend on your location, contract and circumstances. Seek qualified local advice before refusing an instruction or making a decision that could affect your employment.