The one piece of data that could actually shed light on your job and AI
The key technical gap is not whether AI can touch a task, but whether organizations can measure the downstream substitution effect. For enterprise teams, that means exposure scores are only a starting signal. What matters operationally is the interaction between automation quality, unit economics, customer demand, and staffing decisions across specific workflows. A task that is technically automatable may still be economically irrelevant if it sits inside a broader service chain that customers value for speed, trust, or compliance.
That shifts the architecture problem from model capability alone to instrumentation. Leaders who want defensible AI plans need workflow-level telemetry: task duration, exception rates, cost-to-serve, rework, queue depth, and the business outcome tied to each step. Without that observability, AI adoption is being managed with coarse exposure maps rather than evidence about where productivity gains actually convert into higher throughput, lower prices, or fewer roles.
There is also a maintainability trade-off. AI tools that speed up one function can create hidden dependencies elsewhere, especially when downstream systems, review gates, and approval chains were designed for slower human execution. In practice, faster code generation, content creation, or support triage may increase demand for QA, governance, integration, and incident handling. The enterprise consequence is that labor substitution and labor reallocation can happen at the same time.
For technical decision-makers, the useful question is not โCan AI do the task?โ but โWhat changes when the task becomes cheaper and faster?โ Answering that requires repeatable measurement across business units, not isolated pilot results. It also argues for treating AI programs like production systems: monitor adoption, price sensitivity, error recovery, and staffing impact together, or the organization will optimize the tool while missing the actual operating model shift.
This story originally appeared in The Algorithm, our weekly newsletter on AI. To get stories like this in your inbox first,ย sign up here.
Within Silicon Valleyโs orbit, an AI-fueled jobs apocalypse is spoken about as a given. The mood is so grim that a societal impacts researcher at Anthropic, responding Wednesday to a call for more optimistic visions of AIโs future, predicted weโll see a recession and a โbreakdown of the early-career ladderโ before eventually seeing upsides. Her less-measured colleague Dario Amodei, the companyโs CEO, has called AI โa general labor substitute for humansโ that could do all jobs in less than five years. And those ideas are not just coming from Anthropic, of course.ย
These conversations have unsurprisingly left many workers in a panic (and are probably contributing to support for efforts to entirely pause the construction of data centers, some of which gained steam last week). The panic isnโt being helped by lawmakers, none of whom have articulated a coherent plan for what comes next.
Even economists who have cautioned that AI has not yet cut jobs and may not result in a cliff ahead are coming around to the idea that it could have a unique and unprecedented impact on how we work.ย
Alex Imas, based at the University of Chicago, is one of those economists. He shared two things with me when we spoke on Friday morning: a blunt assessment that our tools for predicting what this will look like are pretty abysmal, and a โcall to armsโ for economists to start collecting the one type of data that could make a plan to address AI in the workforce possible at all.ย
On our abysmal tools: consider the fact that any job is made up of individual tasks. One part of a real estate agentโs job, for example, is to ask clients what sort of property they want to buy. The US government chronicled thousands of these tasks in a massive catalogue first launched in 1998 and updated regularly since then. This was the data that researchers at OpenAI used in December to judge how โexposedโ a job is to AI (they found a real estate agent to be 28% exposed, for example). Then in February, Anthropic used this data in its analysis of millions of Claude conversations to see which tasks people are actually using its AI to complete and where the two lists overlapped.
But knowing the AI exposure of tasks leads to an illusory understanding of how much a given job is at risk, Imas says. โExposure alone is a completely meaningless tool for predicting displacement,โ he told me.
Sure, it is illustrative in the gloomiest caseโfor a job in which literally every task could be done by AI with no human direction. If it costs less for an AI model to do all those tasks than what youโre paidโwhich is not a given, since reasoning models and agentic AI can rack up quite a billโand it can do them well, the job likely disappears, Imas says. This is the oft-mentioned case of the elevator operator from decades ago; maybe todayโs parallel is a customer service agent solely doing phone call triage.ย
But for the vast majority of jobs, the case is not so simple. And the specifics matter, too: Some jobs are likely to have dark days ahead, but knowing how and when this will play out is hard to answer when only looking at exposure.
Take writing code, for example. Someone who builds premium dating apps, letโs say, might use AI coding tools to create in one day what used to take three days. That means the worker is more productive. The workerโs employer, spending the same amount of money, can now get more output. So then will the employer want more employees or fewer?ย
This is the question that Imas says should keep any policymaker up at night, because the answer will change depending on the industry. And we are operating in the dark.ย
In this coderโs case, these efficiencies make it possible for dating apps to lower prices. (A skeptic might expect companies to simply pocket the gains, but in a competitive market, they risk being undercut if they do.) These lower prices will always drive some increase in demand for the apps. But how much? If millions more people want it, the company might grow and ultimately hire more engineers to meet this demand. But if demand barely ticks upโmaybe the people who donโt use premium dating apps still wonโt want them even at a lower priceโfewer coders are needed, and layoffs will happen.
Repeat this hypothetical across every job with tasks that AI can do, and you have the most pressing economic question of our time: the specifics of price elasticity, or how much demand for something changes when its price changes. And this is the second part of what Imas emphasized last week: We donโt currently have this data across the economy. But we could.ย
We do have the numbers for grocery items like cereal and milk, Imas says, because the University of Chicago partners with supermarkets to get data from their price scanners. But we donโt have such figures for tutors or web developers or dietitians (all jobs found to have โexposureโ to AI, by the way). Or at least not in a way thatโs been widely compiled or made accessible to researchers; sometimes itโs scattered across private companies or consultancies.ย
โWe need, like, a Manhattan Project to collect this,โ Imas says. And we donโt need it just for jobs that could obviously be affected by AI now: โFields that are not exposed now will become exposed in the future, so you just want to track these statistics across the entire economy.โ
Getting all this information would take time and money, but Imas makes the case that itโs worth it; it would give economists the first realistic look at how our AI-enabled future could unfold and give policymakers a shot at making a plan for it.
Update: This story was updated on April 8 with more context of a post by an Anthropic researcher.
Enjoyed this article? Sign up for our newsletter to receive regular insights and stay connected.
