Where we start
Labour economics has one move that makes the AI argument tractable: stop talking about occupations and start talking about tasks. An occupation is a name on a payslip; a task is a thing that gets done, with hours attached, and a tool either does it, helps with it, or leaves it alone. Once the unit is the task, the evidence sorts itself. Three experiments since 2023 have measured what a generative model does to specific tasks, and they agree on more than the headlines suggest. None of them measured what happens to the person whose week those tasks were part of. That gap is not a flaw in the studies; it is the shape of the open question, and the page draws it rather than filling it in.
★ What you walk out with tonight. The task-versus-job distinction as a habit, the two arrows of displacement and reinstatement drawn on one line with the net left open, the three task-level figures with their exact units and evidence tiers, a scored task inventory for one role built in pandas with the scores labelled invented, and one sentence you can say in a planning meeting that is true: "X of Y weekly hours sit in tasks the studies measured, and none of the studies measured what happens to the role".
A job is a bundle of tasks
5 min liveTake any role and write down what its week is made of: the report, the questions in chat, the SQL, the cleaning, the meetings, the deciding, the mentoring. That list is the job, and the hours beside each line are how the job is weighted. A tool never meets the list. It meets one line at a time, and for each line there are only three outcomes: the tool does it instead of the person, the tool makes the person faster or better at it, or the tool is irrelevant to it. The first is substitution, the second is complementarity, and a single job usually contains both.
LiveTasks are what a tool touches; jobs are what a person holds3 min▶
The unit matters because the arithmetic changes with it. Say a tool halves the time a task takes. If that task is the whole job, the job needs half the hours. If it is three of eight tiles weighted by hours, the saving is whatever those three tiles were worth, and the other five tiles are untouched. Most real weeks are the second case. The habit is to ask "which tiles?" before "which jobs?", and to refuse to answer the second until someone has done the first.
Substitution is the tool doing the task instead of the person. The hours leave the person, and where they go is a decision someone makes: reassigned to other tiles, or removed from the payroll, or filled with tiles that did not exist before. Complementarity is the tool making the person more productive at the task. The hours stay and produce more, and a task that was a bottleneck can stop being one, which raises the value of the tiles around it. The same tool on the same job usually does both, tile by tile, and a sentence about "AI and this job" that does not say which tile it means is not yet a sentence.
Exposure is the word for "a tool could plausibly touch this tile". It is a statement about the tile, not about what happens next. A highly exposed task can be complemented rather than substituted, and a substituted task can free hours into work that was previously starved of them. Exposure is where the analysis starts. It is not where it ends.
Self-studyWhy the same tool substitutes for one person and complements another2 min▶
Two people hold the same job title and different bundles. One spends most of the week on the three exposed tiles; the other spends most of it on the five plain ones and picks up the exposed three for an hour a day. The tool arrives. For the first person, the exposed tiles were the job, and the outcome depends entirely on what management does with the freed hours. For the second, the tool takes an hour a day off tasks that were never the point, and the week gets better. Same title, same tool, opposite experiences, and a job-level statistic would average them into a number that describes neither.
This is also why the experiments in Part 3 report different effects for novices and for experienced workers on the very same task. The tool's contribution to a task is measured against what the person could already do. Where the person was already good, there is little to add; where they were new, the tool carries expertise the person has not yet built. Whether that narrows the gap between them for good or only for now is one of the contested questions, and the page leaves it contested.
The support desk that got measured. Brynjolfsson, Li and Raymond, "Generative AI at Work", NBER Working Paper 31161 (2023; later published in the Quarterly Journal of Economics, 2025), studied customer-support agents given a generative assistant. The task was one tile: issues resolved per hour. It rose by 14 percent on average, by 34 percent for novice and low-skilled workers, and minimally for experienced and highly skilled workers. Read it through the bundle: a tile got faster, most for the people who were slowest on it. What the company then did with the hours, and what happened to headcount, is not in the tile and the study does not claim it.
Two arrows on one line
5 min liveZoom out from one job to all of them and the task vocabulary still holds, with two forces instead of three outcomes. Acemoglu and Restrepo, "Automation and New Tasks: How Technology Displaces and Reinstates Labor", Journal of Economic Perspectives 33(2) 3-30 (2019), name them: the displacement effect, where machines take over tasks that labour used to do, and the reinstatement effect, where new tasks are created in which labour has an edge. Draw them as two arrows on one line. The net is the difference in their lengths, and nothing on the drawing fixes it.
LiveThe displacement effect and the reinstatement effect3 min▶
Displacement is the arrow everyone sees. A machine, or a model, takes over a task that a person used to do, and the share of tasks performed by labour falls. It is the mechanism behind every "jobs at risk" headline, and it is real; it is also only half of the paper. Reinstatement is the arrow that the headline leaves out: the creation of new tasks in which people have a comparative advantage over the machine. New tasks are hard to count because they do not exist yet when the forecast is made, which is why forecasts systematically see the first arrow more clearly than the second.
The paper's contribution is to put both on the same line and make the net a question about their relative sizes rather than a slogan. That is why the page cites the 2019 Journal of Economic Perspectives paper, "Automation and New Tasks: How Technology Displaces and Reinstates Labor", 33(2) 3-30, and not the 2018 American Economic Review paper by the same authors, which is a different model with a different argument. Getting the citation right is part of getting the claim right: the claim is two arrows and an open net.
For generative models specifically, the honest position is that displacement is being measured tile by tile (Part 3) and reinstatement is, by its nature, not yet countable. So the net is not known, and the page says so rather than picking a side.
Self-studyThe productivity paradox, and why measurement lags a technology2 min▶
Robert Solow, reviewing a book in the New York Times Book Review on 12 July 1987, is widely reported to have written that you can see the computer age everywhere but in the productivity statistics. The line is reported here, not read from the microfilm, and it names a pattern that has recurred with every general-purpose technology since: adoption is visible long before its effect on measured output is. Three reasons, none of them exotic. Firms adopt the tool before they reorganise the work around it, and the gain is in the reorganisation. The complementary investments, in training, in data, in new processes, are spent before they pay. And the statistics that would show the gain are built around the old tasks, so a new task that the tool created is measured badly or not at all.
The consequence for tonight is a warning in both directions. Early task-level gains, like those in Part 3, do not automatically show up in output statistics, so their absence in the aggregate numbers is not evidence that the task gains are illusory. And the task gains do not automatically become aggregate gains either, because the reorganisation between the tile and the economy has not happened yet. Both readings are open. Someone who tells you which one is right has more information than the statistics contain.
Self-studyWages: the disagreement, stated as a disagreement2 min▶
Whether a tool that complements a task raises or lowers the wage of the person doing it is contested, and the contest is not a failure of research; it is that the answer depends on things the task-level studies do not measure. If the tool raises the output of novices most, as the support-desk study found, one reading is that the wage gap between novice and expert narrows because the expert's edge is now partly in the tool. Another reading is that the expert's remaining edge, on the tasks the tool cannot do, becomes scarcer and more valuable, and the gap widens. Both are coherent, both have supporters, and the same experiment is compatible with each because the experiment measured a tile and the wage is paid for the bundle.
The professional norm is therefore to say what is measured and what is inferred, in separate sentences. "Novices resolved 34 percent more issues per hour with the assistant" is measured. "Therefore novice wages will rise" is inferred, and the inference needs an argument about the labour market that the study did not make. Keeping the two apart is most of what it means to read this literature well.
The forecast that only saw one arrow. Every decade produces a list of occupations "at risk" from the technology of the moment, and every such list is a displacement estimate: it counts the tiles a machine could plausibly take and sums them into jobs. The reinstatement arrow is missing from the method, not because the authors forgot it, but because it cannot be listed in advance. The right way to read an at-risk list is as one arrow drawn carefully, with the other arrow's length unknown. That reading is duller than the headline and it is the only one the method supports.
Three experiments, three task counts, zero jobs
5 min liveSince 2023 three experiments have put a generative model into a real or realistic task and measured the difference against a control group. They are the best evidence there is on the displacement arrow at the tile level, and each carries its figure, its unit and its evidence tier. Two things are true of all three: they randomised access to the tool, which is why their numbers are worth more than a survey; and they measured tasks in an experiment, not jobs in an economy, which is why their numbers do not answer the employment question, and do not try to.
LiveThe three studies, each with its figure, its unit and its tier3 min▶
Brynjolfsson, Li and Raymond, "Generative AI at Work", NBER Working Paper 31161 (2023; later published in the Quarterly Journal of Economics, 2025). Customer-support agents, a generative assistant, one task: issues resolved per hour. Up 14 percent on average, 34 percent for novice and low-skilled workers, minimal for experienced and highly skilled workers. Read at source; primary. The unit is a rate per hour, and the headline is the gradient by experience as much as the average.
Noy and Zhang 2023, Science 381(6654). Professional writing tasks, done with and without a model. Reported as about 40 percent faster with about 18 percent higher quality. The figures are reported here from the abstract as reproduced by a secondary index; the article itself was not opened in this build, so the tier is secondary and the page says "reported". The unit is time on a task and a graded quality score, both at the task.
Dell'Acqua et al. 2023, "Navigating the Jagged Technological Frontier", Harvard Business School Working Paper 24-013. Consultants given a model, on a set of tasks the authors chose to sit inside the model's capability and one task chosen to sit outside it. Inside: 12.2 percent more tasks completed, 25.1 percent faster, more than 40 percent higher quality. Outside: 19 percentage points less likely to produce a correct solution. Read from the working paper; primary. The two-sided result is the reason the study matters more than its good numbers: the same tool, the same people, and the sign flips with the task.
What the three share is the design. Each randomised who got the tool, so the difference is the tool and not the kind of person who chooses to use one. What the three also share is the unit. Every figure above is a task in an experiment. Not one is a job in an economy, and not one of the papers claims otherwise.
LivePercent against percentage points, on the number people most often misquote2 min▶
"19 percentage points less likely to produce a correct solution" is a gap between two rates: the share of the tool group who got it right, minus the share of the control group who did. A percentage point is one hundredth of the whole, subtracted. "19 percent less likely" would be a proportion of the control group's rate, multiplied. They are only the same number when the base rate is 100 percent, which it never is.
Make it concrete with an invented base rate, used only for the arithmetic and not the paper's own figure: if the control group got 80 of 100 right, 19 points takes the tool group to 61 of 100. Nineteen percent of 80 is about 15, which would take the tool group to about 65. The misquote understates the finding by four people in a hundred on that base rate, and by a different amount on any other base rate, which is exactly why the unit has to travel with the number. The paper says points. Say points.
Self-studyWhat a task study cannot say, and why that is not a criticism2 min▶
A task study holds the job fixed and changes the tool. It cannot see what the firm does with the freed hours, because in the experiment the firm did nothing yet; it cannot see whether the task still exists as a human task a year later, because the experiment ran for weeks; and it cannot see reinstatement at all, because a task that does not exist cannot be randomised. These are not gaps a better experiment would close. They are the boundary of what a task experiment is, and the papers state their boundary plainly.
The open question therefore has a precise shape: given that these tiles got faster or better, what happens to the bundles that contain them, and to the people who hold the bundles? Answering it needs data on jobs over time, which is a different kind of evidence with different problems, and the results so far do not agree with each other. The professional stance is to carry the task figures with their units and their tiers, to carry the employment question as a question, and to notice when someone joins the two with a "therefore" that no study supplied.
The consultants who could not see the line. In the Dell'Acqua experiment the tasks on either side of the frontier were chosen to look comparable to the people doing them. On one side the model made them faster and better; on the other it made them 19 percentage points less likely to be right. The lesson for a team adopting a tool is not "use it less". It is that the frontier does not announce itself, so a team needs a way to find out which side a task is on before trusting the output, and that finding out is itself a new task, sitting in someone's bundle, that did not exist last year.
A task inventory for one role, scored
★ 22 min · everyone buildsFive short steps in pandas. The role is a reporting analyst on a marketing team, and every hour and every score below is invented to show the arithmetic; the only real column is which published study measured a task like it. Replace the rows with a role you actually know, keep the scores honest about being guesses, and the sentence at the end will still be true of whatever you typed. Your numbers will differ, and they should.
Write the inventory as data. One row per task, hours per week, and an exposure score between 0 and 1 that is your guess at how much of the task a tool could plausibly touch. The scores are the honest part of the exercise only if you admit they are guesses.
Attach the study, or "none". This is the one column that is not a guess: for each task, name the published experiment that measured a task like it, and leave it empty when none did. The mapping is a judgement and the page says so; the point is that the judgement is written down.
Sum the hours two ways. Measured hours are the hours in tasks a study touched, whatever it found. Exposure-weighted hours multiply each task's hours by its score, which is a softer number and a more honest one, because it carries the guess with it.
Keep the sign with the study. "Measured" is not "helped". One of the four measured rows maps to the outside of the frontier, where the tool made consultants 19 percentage points less likely to be right. Split the measured hours by which side of the frontier the study put them on, so the inventory never quietly counts a wrong-way result as a gain.
Write the sentence. The output of the build-along is one line of prose that is true of the numbers you typed, and that stops exactly where the evidence stops. Print it, paste it into the planning document, and let the next sentence be a question.
Keep the exposure scores visibly invented. The moment a column of guesses is saved without the word "constructed" in the filename, it will be read back in a month as a measurement. The studies measured tiles; the inventory guesses at which tiles those were in your team. Both are useful, and they are not the same kind of number, so they should never share a filename without the label.
Before deep-dive session 8
30 min- Inventory a role you actually know, yours or a teammate's, with real hours from a real week. Score exposure honestly, mark each score as a guess, and print the sentence.
- Draw the frontier for that role. For each measured task, write whether you believe it sits inside or outside the tool's frontier and why. Then write how you would find out, because the Dell'Acqua consultants could not tell from the task itself.
- Find one misquote. Search for a news write-up of the Dell'Acqua result and check whether it says percent or percentage points. Write down which, and what the difference would be on an invented base rate.
- Write both arrows. For the role, one task the tool now does instead of the person, and one task that exists because of the tool and did not last year. If the second line is empty, that is a finding too.
Three questions
Clear all three and deep-dive session 7 gets stamped in your passport.
1 · The support-desk study found issues resolved per hour rose 14 percent on average with the assistant. A colleague concludes that support headcount can fall by 14 percent. What is wrong with the step?
The study did randomise access, which is why the 14 percent is worth more than a survey. Its unit is still a task. The gain was 34 percent for novices and minimal for experienced agents, and whether a firm reassigns, retrains or reduces is a decision the experiment did not observe.
2 · Dell'Acqua et al. report consultants were 19 percentage points less likely to produce a correct solution on the task outside the frontier. Using an invented control-group rate of 80 in 100 for the arithmetic only, what does the finding say about the tool group?
Points subtract; percent multiplies. On this invented base rate the misquote understates the gap by four people in a hundred, and by a different amount on any other base rate, which is why the unit has to travel with the number. The paper says points.
3 · Acemoglu and Restrepo (2019) draw displacement and reinstatement as two effects on labour's share of tasks. What does the drawing, on its own, say about the net effect of generative models on employment?
The paper's contribution is to put both effects on one line and make the net an empirical question about their relative sizes. The page cites the 2019 Journal of Economic Perspectives paper, 33(2) 3-30, and makes no claim about total employment because the evidence does not hold one.
What this session teaches, and where it came from
Every fact on this page, and its verification tier, is recorded in the course's source map.
Deep-dive session 7 cheat sheet · pin this
Tonight's frontier had a problem the consultants could not solve from the task: which side a piece of work sits on is not visible before the output is checked. Deep-dive session 8 makes that invisibility the subject. A model, or a dataset, is a good whose quality cannot be observed before purchase, which is Akerlof's lemons problem wearing a model card. Benchmarks and evals are the signals sellers send, Goodhart says what happens to any signal that becomes a target, and inside the ML team the same problem shows up as a metric between a principal and an agent. The build-along reads a real model card as a signal and asks what it can and cannot tell you.