MAIE5103 Chap.13 Automation, Work and Productivity Evidence
Automation, Work and Productivity Evidence
Capability, adoption and job loss are three different things
The labour section of the automation lecture starts with a 2014 video argument that machines will replace human workers as they replaced horses, and treats it as a provocation to examine rather than a forecast.
Its central warning is that a machine being able to do a task does not mean it will be adopted, and adoption does not mean a job disappears: demand, costs and institutional choices sit in between.
An ILO working paper of May 2025 makes the same distinction with numbers, estimating that about one in four workers worldwide has some exposure to generative AI and 3.3% of employment is in the highest-exposure group, while judging transformation more likely than replacement.
Reading a controlled experiment
The coding study by Peng and colleagues is a careful experiment with a narrow scope.
In 2022, 95 professional programmers were split into an assisted group of 45 and a control group of 50, and each built one JavaScript HTTP server from skeleton code. Among those who finished, the assisted group was 55.8% faster, with an interval of 21% to 89%, but the gain in task success was not significant.
The lecture lists what the study could not measure: code quality, security, learning, maintenance, wages or headcount.
Reading a company's claims
The Klarna case shows how to audit a company announcement. Its 2024 release reported conversation counts, a workload equal to 700 full-time agents, faster resolution and steady satisfaction, all company-reported and unaudited.
The lecture separates what each claim establishes from what it must not be stretched to mean, uses Autor's task framework to explain why no net-employment conclusion follows, and notes that a stated human option is not a tested hand-off.
What this chapter covers
- 01
The substitution argument and its hidden assumptions
- 02
Occupational exposure to generative AI
- 03
Task exposure, adoption and job loss
- 04
The 2022 coding-assistant experiment and its limits
- 05
Intervals, completers and non-significant results
- 06
Auditing a company claim package
- 07
Substitution, complementarity and output demand
- 08
A human option against a documented hand-off
Worked example · free
Bound the claims a productivity study can support
- 2State the result the trial supports, with its interval.
- 2Name two outcomes the trial did not measure.
- 2Explain why the staffing claim does not follow.
Key terms
- Task Exposure
- The extent to which the tasks in an occupation could be performed or changed by a technology, which is not the same as adoption or job loss.
- Workload Equivalence
- An estimate expressing automated output as the number of full-time staff it would take, which is not a count of jobs removed.
- Claim Package
- The set of figures a company publishes about its own deployment, each of which needs attribution and a statement of what it does not establish.
- Task Framework
- Autor's account of automation as substituting for some tasks, complementing others and changing demand for output, so that net employment cannot be read from one channel.
- Hand-off Route
- The documented path by which a person moves from an automated service to a human, including routing rules, availability, wait times and outcomes.
Automation, Work and Productivity Evidence FAQ
Does exposure to generative AI mean jobs will be lost?
No. Exposure measures how much of an occupation's tasks a technology could affect, not whether it will be adopted or whether anyone will lose work. The ILO working paper the lecture cites estimates that about one in four workers globally has some exposure and 3.3% of employment is in the highest-exposure group, and it judges transformation of jobs more likely than wholesale replacement.
What did the GitHub Copilot productivity study actually find?
In a 2022 experiment with 95 programmers, those using the completion assistant finished one standardised JavaScript task 55.8% faster among completers, with a 95% interval of 21% to 89%, and the result held when four slow control outliers were removed. The difference in task success was not significant. It did not measure code quality, security, learning or employment.
How should a company's AI productivity claims be evaluated?
Attribute each figure to the company, say what kind of measurement it is, and state what it does not establish. Ask for counting rules, denominators, time windows, task mix, score methods and a causal comparison, and do not convert a workload-equivalence figure into a count of jobs removed.
To claim shared gains, compare outcomes for contacts the AI closed alone, contacts where it supported a person, and contacts people resolved themselves.
Assessment move
Keep a one-page ledger for any productivity or labour claim you meet: the figure, who reported it, what kind of measurement it is, and what it does not establish. Fill it for the coding study and the Klarna release from memory, then check against this chapter. The ledger is the fastest way to write the evidence paragraph of a news presentation without overstating the source.
Working through Automation, Work and Productivity Evidence in MAIE5103? Sia is AskSia’s AI Arts and Humanities tutor — ask any MAIE5103 Automation, Work and Productivity Evidence question and get a clear, step-by-step explanation grounded in how MAIE5103 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.