Can AI replace your staff, and what actually gets displaced

What actually gets displaced, named plainly

Automation takes tasks, not titles. The tasks it takes have a recognisable shape: they repeat, the rules can be written down, and the input arrives in a form software can read.

Add up the hours those consume inside a single role and the total is usually larger than anyone expects, because none of them are scheduled. They happen between other things, which is exactly why they never appear on a job description and never get counted.

Some of this has only recently become possible. Customers in this market send voice notes and screenshots of a payment rather than typed text, and switch between English and Urdu inside one message. Work that needed a person purely because the input was messy is now work a system can at least prepare.

• Copying a value from one system into another so two records agree
• Answering the same handful of questions that arrive every week in slightly different words
• Sorting and routing: deciding which pile an enquiry, a document or a ticket belongs in
• Chasing. Reminding a customer, a supplier or a colleague that something is outstanding
• Assembling a recurring report from sources that have not moved since last month
• Turning a messy input into a structured one: reading an invoice, transcribing a voice note, pulling fields out of a form

What does not go, and is nowhere near going

The work that survives is the work where the rule cannot be written in advance, or where somebody has to be accountable for the outcome.

Two things about that list are worth noticing. None of it is junior work, and none of it is what people spend most of their week doing. Those two facts together are the entire argument for redeploying rather than reducing.

• Deciding what to do when the information is incomplete and the deadline is now
• Anything a person has to sign for, where a bank, an auditor or a regulator requires a named human
• Relationships. The supplier who gives you the last slot because of who asked for it
• Negotiating, where the other side is reading you as much as your offer
• Handling a customer who is upset, where the goal is not the fastest correct answer
• Deciding what the business should do next, which is not a task at all but the thing tasks serve

The roles that do shrink, said without softening

Any page on this subject claiming no role is ever affected is not being straight with you. Some roles are mostly the tasks in the first list, and when those tasks go the role gets smaller.

In most businesses this shows up as headcount that stops growing rather than headcount that falls. The work grows, the team does not, and the role that would have been advertised next year is quietly not advertised. That is a real effect on a real person, and it is better said than dressed up.

Where it does show up as reduction, it is usually a business that decided on reduction first and went looking for a tool to justify it. The technology did not make that decision, and it should not be allowed to carry the blame for it either.

• Pure data entry, where the job is moving information between two systems by hand
• First line response at low complexity, where the work is picking the right stock answer
• Manual reconciliation between two reports that could be joined automatically
• Roles created to bridge two systems that were never properly connected

Redeployment is where the value actually shows up

Businesses that get lasting value out of this move people rather than remove them, for a reason that has nothing to do with sentiment. The saving from removing a person happens once and stops. The gain from a person freed to do work only people can do keeps going, because that work is usually the work that wins the customer or keeps them.

There is a practical version. When automation takes the copying and the chasing out of an operations role, the person in it becomes the one who handles exceptions, owns the system and reads a sample of what it did. That is a better job, it is harder to replace, and it is a promotion in everything except the paperwork.

It also protects you from the failure nobody plans for. A team cut to the size the automation implies has no capacity on the day the automation breaks, and it will break. Something has to absorb that, and in a lean team that something is a customer waiting.

How to tell your team without lying to them

Staff work out that automation is coming long before anybody announces it, and the silence fills with the worst available guess. What follows is not a script. It is the four things people actually want to know, in the order they want them.

The thing not to do is promise that nobody will ever be affected. If that turns out to be untrue, everything else you said about the system goes with it, and the people whose cooperation the rollout depends on are the ones who stop cooperating.

• Which specific tasks are being automated, named, so nobody has to imagine the list
• What happens to the time that frees up, answered concretely rather than with a promise about growth
• Who owns the system afterwards, because that is a new job and somebody in the room could have it
• What the honest position on headcount is, said once and plainly, including if the answer is that a role will not be replaced when it next falls vacant

Situations where none of this applies

If your reason for buying is to cut headcount, the arithmetic rarely works the way a proposal implies and the project usually stalls. Automation takes tasks out of many roles rather than every task out of one, so the saving arrives as spare capacity spread thinly rather than as a vacancy. Businesses that buy for capacity get capacity. Businesses that buy for redundancies often get neither.

In a very small team none of this scales the way it is described. Where the same person does sales, dispatch and the accounts, there is nobody to redeploy anybody into, and the honest benefit is that the owner gets their evenings back rather than that the business gets cheaper. Worth buying, but a different purchase, and it should be sold as one.

And where the person doing the work is the product, leave it alone. If the customer is paying for that individual's attention, judgement or name, taking them out of the work removes the reason anybody bought.

How quickly a role changes, and the work that comes back to a person

Redeployment needs a timetable or it stays an intention. The audit takes the first week and it should produce a task list rather than a job list, which is the distinction this whole page rests on. One named piece is live inside a fortnight, and the person whose task it was should be the one trained on it during that fortnight rather than told about it afterwards. Doing it in that order turns the announcement into something people can see, and the silence described above is what otherwise fills with the worst available guess.

The work that comes back to a person is written into the build rather than left to judgement on the day. Anything published in the business's name, any pricing decision, any change to spend and any complaint that has turned serious wait for human approval, and a case outside the rules hands it to a person with the record attached. That part of a role grows rather than shrinks. Somebody has to read what came through the stop, and it is a considerably better use of an hour than the copying was.

The cheapest version of this is frequently your own team doing it. Where somebody in-house already automates things and understands which exception is real, the tasks in the first list are within reach, and the redeployment argument is far easier to make when the person building it is the person whose job is changing. Moiz Khan owns automation architecture at Wobble and decides what a system may do without a person. The published evidence for the redeployment case rather than the replacement case is Quillon, where a delivery line eating more than 65 per cent of revenue became a single audited automation and the business changed shape instead of shedding it.

Common questions

Will AI replace employees?

It replaces tasks far more readily than it replaces people. Automation is good at repeated work with writable rules and readable inputs, which is a portion of most jobs rather than the whole of them. Roles that consist almost entirely of that kind of work do shrink, and in most businesses the effect shows up as a role that never gets advertised rather than a person who gets let go.

Which jobs are most at risk from AI automation?

Roles built around moving information by hand: pure data entry, manual reconciliation between two reports, first line response where the work is choosing the right stock answer, and jobs that exist only because two systems were never properly connected. What they share is that the rules are writable and the input is machine readable.

Will AI take over customer service?

It takes the repeated part. The questions that arrive every week in slightly different words can be answered by a system, and answered faster than a person can at eleven at night. What does not transfer is the upset customer, the exception nobody wrote a rule for, and any case where the goal is not the fastest correct answer. Those still need somebody with authority to make it right.

Should we cut headcount after automating?

Rarely, and almost never as the reason for buying. The freed time usually arrives spread across several roles rather than concentrated in one, so there is no vacancy to remove. Cutting to the size the automation implies also leaves nothing to absorb the day it breaks, which it will, and the cost of that day is paid by whichever customer is waiting.

How do I tell my team we are automating part of their work?

Name the specific tasks, say what happens to the time, say who will own the system, and give an honest answer on headcount even if it is uncomfortable. People fill silence with the worst guess available. The one thing to avoid is promising that nobody will ever be affected, because if that proves untrue every other assurance you gave goes with it.

Does this mean we stop hiring?

It usually means you hire differently. The repeated part of a role is the part a system can take, so the job you advertise afterwards is smaller, better defined and easier to fill. Plenty of businesses use this to hire for judgement earlier than they otherwise could, because the admin that used to justify a junior post is no longer there to justify it.