They Want Me to Train My AI Replacement — Should I Do It?

I saw a post on Reddit that i can't stop thinking about. The person had been told by their manager to spend the next three months documenting every aspect of their job — every process, every decision tree, every edge case — so that the company could build an AI system to handle it. After which, the implication was clear if unspoken: the person would no longer be needed.

They were being asked to build the machine that would replace them. And they wanted to know: should i actually do this?

The comments were split roughly down the middle. Half said "refuse, don't dig your own grave." Half said "do it, get your severance, leave with your reputation intact." Both sides had reasonable points. But the real answer, as with most workplace dilemmas, is more nuanced than either.

The awkward reality

Let me start with the uncomfortable truth: your company probably has the right to ask you to do this.

In most employment contracts, you're required to perform reasonable duties as directed by your employer. Documenting your processes is, on its face, a reasonable request. Companies document processes all the time for business continuity, quality assurance, regulatory compliance. The fact that this particular documentation will be used to build an AI system doesn't necessarily make the request unreasonable in a legal sense.

If you refuse outright, you risk disciplinary action for failing to follow reasonable instructions. That puts you in a worse position when the eventual redundancy comes, because you've given the company a performance issue to hang your dismissal on instead of a redundancy package.

So "just refuse" sounds satisfying but it's often a bad strategy.

That said, you're not powerless here. Not even close.

What you actually have: leverage

Think about what your company is telling you by making this request. They're telling you that they cannot build this AI system without your knowledge. Your expertise is literally the thing they need to make their plan work. That's not a position of weakness. That's leverage.

The company needs something from you. You need something from the company (specifically: a good severance package, a positive reference, and fair treatment on the way out). This is a negotiation, even if nobody has called it that yet.

The strategic approach

Here's how i'd think about it if i were in this position.

Step one: get clarity on your future. Before you document anything, have a direct conversation with your manager or HR. "I'm happy to help with this project. Can you tell me what happens to my role once it's complete?" Force them to be explicit. If they say your role will continue, get it in writing. If they hedge, you have your answer.

Step two: negotiate before you start, not after. This is the critical bit. Once you've handed over your knowledge, your leverage disappears. Before that, you have something they need. This is the moment to negotiate.

What should you negotiate for?

• Enhanced redundancy or severance. If your role is going to be eliminated, negotiate the terms now, before you do the work. "I'll commit fully to this documentation project in exchange for a redundancy package of X, an agreed reference, and Y months of notice."
• A transition role. Maybe you can negotiate a role managing or maintaining the AI system you're helping to build. You know the domain better than anyone. There might be a genuine need for a human who understands both the work and the technology.
• A timeline. Don't let the project be open-ended. Negotiate a clear end date with clear terms for what happens to you at that point.
• Retraining. If the company is willing to invest in AI that replaces your role, they should be willing to invest in training you for a different role. This is increasingly a legal expectation in some jurisdictions.

The severance negotiation guide has the specific tactics for these conversations.

Step three: do the work professionally. Assuming you reach acceptable terms, do the documentation work properly. This might feel like betrayal, but being professional about it protects your reputation and your reference. The people who remember you as cooperative and thorough during a difficult transition are the people who'll vouch for you at your next job.

Step four: document your own value. While you're documenting your processes for the AI system, also document your achievements, your contributions, and the complex decisions you make that can't easily be captured in a process document. This serves two purposes: it makes your CV stronger, and it subtly demonstrates the limitations of what an AI system can actually replicate.

The things AI can't capture (and why that matters)

Here's something your company might not have fully thought through.

You can document a process. You can create flowcharts and decision trees and if-then rules. An AI system can follow those. But there's a huge amount of what you do that doesn't fit into a process document.

The client who needs handling carefully because of a difficult history. The supplier you know is unreliable despite their good metrics. The internal politics of getting a project approved. The judgment call you make ten times a day about which emails need an immediate response and which can wait. The pattern recognition that comes from years of experience and can't be articulated as a rule.

When you document your job, you're capturing the explicit knowledge — the stuff that can be written down. But a huge portion of what makes you effective is tacit knowledge — the stuff that can't. The company's AI system will get the explicit part. It won't get the tacit part. And when things go wrong because the tacit knowledge is missing, which they will, your documentation won't be blamed. The AI system will.

This isn't a reason to sabotage the documentation. But it is a reason to be confident that the company is underestimating the complexity of what you do, and that confidence should inform your negotiations.

What NOT to do

Don't sabotage the documentation. Deliberately leaving out key information or inserting errors feels like revenge but it's career suicide. It gives the company a legitimate reason to discipline or dismiss you. It burns your reference. And it doesn't actually stop the AI replacement — it just means they build a worse version and blame you for the problems.

Don't do it quietly and hope for the best. The people who say nothing, document everything, and hope the company rewards their compliance are the people who get the standard redundancy package with a pat on the head. Companies don't reward passivity with generosity. They reward it with the minimum they can get away with.

Don't make it personal. Your manager probably didn't choose this strategy. HR probably didn't either. This is likely a decision made several levels above you. Being angry at the people delivering the message just makes the process harder for everyone without changing the outcome.

Don't assume you can't push back. "They told me to do it so i have to" is not accurate. You have to perform reasonable duties, yes. But you also have the right to ask questions, negotiate terms, seek legal advice, and raise concerns through formal channels. Compliance and advocacy aren't mutually exclusive.

The ethical dimension

I won't pretend there isn't an ethical question here. By documenting your work, you are helping a company eliminate jobs — possibly not just yours, but your colleagues' too. Some people feel strongly that this is wrong, and i respect that.

But I'd push back gently on the idea that refusing to cooperate is a meaningful act of resistance. If you refuse, the company will find another way. They'll hire a consultant, or assign a less experienced team member, or muddle through with worse documentation. Your refusal delays the process but doesn't stop it. And it costs you personally.

The more impactful form of resistance, if you feel strongly about it, is collective rather than individual. Talk to your colleagues. Talk to your union if you have one. Raise concerns about the broader impact through formal channels. Advocate for retraining programmes and transition support. These actions are more likely to change outcomes than individual non-cooperation.

The silver lining (sort of)

Documenting your job in exhaustive detail is genuinely useful for your career, regardless of why you're doing it. It forces you to articulate what you actually do, what skills it requires, and what value it creates. Most people can't do this clearly because they've never had to.

By the time you've finished, you'll have a better understanding of your own expertise than you did before. Your CV will be sharper. Your interview answers will be more specific. You'll be able to explain your value to a future employer with a precision that most candidates can't match.

That's not nothing.

The one thing to do today: if you've been asked to document your role for AI, don't start the documentation. Start the conversation. Ask your manager explicitly what the plan is for your role once the documentation is complete. And if you don't get a clear answer, book a consultation with an employment solicitor before you hand over anything.