For decades the assumption was that automation would climb from the bottom up — first the repetitive and manual, then, one day, the intellectual.
It happened the other way around. McKinsey's 2023 study, The economic potential of generative AI, showed the shift in numbers: the automation potential of the activity "processing data" rises from 73% without generative AI to 90.5% with it; that of "applying expertise" jumps from 24.5% to 58.5%. Occupations in “Educators and workforce training” and “Office support” record significant increases in automation potential when powered by generative AI — the source does not break out a percentage for them.
These numbers are worth reading for what they are: automation potential for activities, not for jobs. Nobody lays off an activity.
The reason for the inversion is mundane. Manual tasks demand physical dexterity and adaptation to a messy world, something robotics still struggles to replicate. Knowledge work is already digital end to end — it did not have to be converted in order to be reached.
Capacity is not output
A common mistake — treating productivity as an automatic consequence of capacity. If the machine does the work, the work comes out.
It does not. A team where half of it never sleeps does not become more productive on its own. It becomes busier, which is a different thing, and the difference shows up in the first week: reports nobody asked for, three versions of the same material, excellent work done on the wrong priority.
What converts capacity into results is banal and old: someone defines the deliverable, the deadline and the scope, follows what was done and assesses it. That is management. It always was.
This gets concrete in what we observe: an AI worker with no current work plan does work — but its work belongs to no deliverable. It produces, and nobody can add it up. The worker itself is instructed to declare this in its report, because orphan output presented as progress is worse than no output at all.
Supervising is not surveillance
"Supervision" tends to be heard as distrust, which is why it is done badly. Supervising is four things, and none of them is looking over someone's shoulder:
- Scope
- saying which deliverables that worker answers for in the period — and what is left out.
- Deadline
- saying when, with a date somebody took on, not a vague expectation.
- Evidence
- having a way to know what was done without asking. It is not the executor's promise; it is the record.
- Assessment
- closing the period with an explicit judgement, with justification, that stays on the record.
A human gets all four out of company habit. An AI gets none of them by default — and that absence is the explanation we see most often for AI pilots that impress in the demo and vanish by the next quarter.
The role that changes most is not the executor's
When an organization puts AI to work executing, the work that appears immediately is not the executor's — it is the work of whoever defines what it does, reviews what it produced and answers for the result.
Notice what this does to a manager's career. The mechanical part of the role — chasing status, compiling the report, remembering who owed what — is exactly the part the machine takes. What is left is scope, priority, exception and judgement. In other words: the role does not shrink, it concentrates on what has always been its reason to exist.
And it becomes scarcer, not less so. Someone has to sign the plan, decide the exception and assess the cycle. That someone is human. (We wrote separately about what this does to the management layer in Managers are not becoming obsolete. Manual management is.)
The same artifacts, for those who sleep and those who don't
The rational choice is deliberately unoriginal: an AI worker should go through the same ritual as a human, in the same artifacts, on the same screens. No parallel "AI" dashboard, no logs and traces as a form of accountability.
It has a name, a role description written by you, a closed set of tools, a work plan tied to a team, accountability cycles and an assessment at the end of each cycle.
In the execution of the work, a person who breaks the rule usually has a legitimate reason and answers for it; an AI agent has no such judgement — and a worker nobody can hold to account is the worst possible combination.
The same principle governs what the worker can do in the world. Every action is classified by code before it happens and routed down one of three paths: it runs on its own, the AI manager reviews it and tells you, or it is held waiting for you.
What this does not solve
A legitimate goal would be for AI to become reliable enough to do without someone supervising it. Our thesis is the opposite: AI becomes part of the team because it becomes supervisable, and supervision is human work that still gets paid for.
Daily autonomous execution — the worker waking up, pulling the next task from the plan and working without anyone asking — is in gradual rollout, enabled organization by organization. Outside of it, it works when it is called on.
Conclusion
The question "will AI take the jobs?" presupposed a swap — a chair changing occupant. What you see in operation is something else: a team that gains a kind of participant that does not sleep, does not forget and does not know on its own what the priority is.
That participant does not replace the management structure. It makes it mandatory. The first job AI creates is supervising it — and the role that changes most is not the executor's, it is the manager's.
