AI does tasks, not jobs

The calculation sounds clean. An AI works around the clock, never falls ill, asks for no bonus and, in many clearly defined tasks, makes fewer mistakes than a human on a bad day. Anyone doing that maths quickly concludes that headcount can be cut. The thought is understandable. It is still misleading.

The flawed assumption

The error is an equation. Technical replaceability is not the same as organisational capability. An AI can take over a task without taking over a job. A job is more than the sum of its tasks. It contains judgement in unclear situations, context knowledge documented nowhere, the ability to escalate when something is wrong, and responsibility someone actually carries.

In many jobs, part of the work is routine and pattern recognition, and there AI is strong. Another part is judgement, exception and context. That is often where the real value sits, and that is where things can break when people are cut first. How large each part is differs from job to job.

The pattern is observable

Companies have already gained experience with this.

Ford expanded its automated quality systems substantially. Because its quality targets were not met that way, the group brought in around 350 experienced technical specialists over three years, through rehiring, new hiring and promotion. The automation did not become worthless, but quality only improved through the interplay of people and system: the group has since reported falling warranty cases and recall costs, according to its leadership in the hundreds of millions.

Klarna went the same way earlier and more visibly. The company had largely automated customer service and, by its own account, pushed the fully automated line too far. Today it runs a model in which AI handles volume and people handle the cases that require judgement and relationship.

IBM automated certain repetitive back-office work, including in HR, while investing and hiring in other areas at the same time. According to its leadership, the overall workforce grew, above all in software development and sales. This does not show that roles requiring judgement are generally protected from automation. It does show that automation and growth can happen at the same time.

These cases are not an argument against AI, nor proof of a general rule. They do show a risk: whoever automates execution while cutting the people who exercise judgement may save in the short term and pay more in the medium term.

The effect that only becomes visible later

Entry-level and routine work is not just a cost item, it is the training ground. Experts emerge through practice, mistakes and growing responsibility. Automate that stage away entirely and you dry up the source from which the seniors of the day after tomorrow come. The well does not run dry immediately. But it runs dry.

The right question

The real question is therefore not whether an AI completes a task faster. It often does. The question is how a company automates without losing the judgement and the knowledge that keep it steerable.

Value does not come from replacing capacity with machines, but from keeping knowledge inside the company, making decisions traceable and connecting them to execution. That is exactly where I come in. Sensible automation does not mean maximum automation, but automation under human leadership, where people still understand goals, context and consequences and can intervene when it matters.

Before you cut a role

A sober calculation pays off. What does it cost if you have to bring that experience back in twelve months, and will you even find it then. What does the standstill cost when nobody is left who notices that the system is giving the wrong answer. These numbers rarely appear in the first business case. In the end they decide the outcome.

This is the first of three articles. The second looks at why AI recommends surprisingly similar things on strategy questions and how to use it well. The third at what digital sovereignty concretely means for an SME.