Why Hasn’t AI Increased Unemployment?  🔗 **Source:** [Why Hasn’t AI Increased Unemployment?](https://twitter.com/PeterMcCrory/status/2079979321607745905/?rw_tt_thread=True) > [!note]+ Document Notes > tags: [ai-labor-market, labor-augmentation, occupational-change, productivity, human-expertise] > author: "Peter McCrory" > source: "https://x.com/p_mccrory/status/2014281227663524038" > reference: "01ky8rcpvrc9kds4q1n04emz23" > date created: 2026-07-24 > > # 🏷️ Title: Why hasn’t AI increased unemployment? > <!-- deep-read:sections start --> ## 🧭 Table of Contents Summary; main content and notes; references; paraphrase; newsletter; action items; hypotheses; methodology; questions; future research; implications; learning, accessibility, DEIB, logic, DARVO, conclusion; refactor appendix; template library. ## 🔗 References - Source: https://x.com/p_mccrory/status/2014281227663524038 - Reader document: 01ky8rcpvrc9kds4q1n04emz23 ## 📝 Summary The essay argues that recent US labor data does not yet show a material AI-driven rise in unemployment. AI remains skill-biased and labor-augmenting because jobs contain mixed tasks, model capability is uneven, and expert oversight still determines outcomes. The evidence supports caution about present claims, not certainty about the future. ## 📖 Main Content The author cites stable unemployment, roughly balanced openings, growing but incomplete firm adoption, modest productivity changes, limited occupational churn, and no occupation whose full task bundle is handled by the cited model. Software examples show experts planning, reviewing, and recovering from failures. Weak links constrain end-to-end gains even when code output rises. ### 🗒️ Notes - Claim: Task automation does not imply full job automation because jobs contain linked responsibilities. - Mechanism: Uneven model capability raises the value of expert oversight and recovery. - Verification focus: Weak links cap system-level productivity even when one production metric jumps. - Scope: This analysis covers the captured source body. It does not treat linked claims as independently verified unless the source supplies direct evidence. ## 📚 References - Primary source: https://x.com/p_mccrory/status/2014281227663524038 - Follow linked primary documents before using numerical, legal, medical, or policy claims in publication. ## 🗣️ Paraphrase AI can perform parts of jobs while leaving planning, context, coordination, and recovery to people. Jobs then change through task rebundling. Aggregate data has not yet separated a large AI unemployment effect from macro conditions, though weaker hiring among some young exposed workers deserves study. ## 📰 Newsletter **Why this matters for WordPress:** The essay argues that recent US labor data does not yet show a material AI-driven rise in unemployment. AI remains skill-biased and labor-augmenting because jobs contain mixed tasks, model capability is uneven, and expert oversight still determines outcomes. The evidence supports caution about present claims, not certainty about the future. For teams building open web software, the useful move is to convert the source’s central claim into a small test, publish limits, and keep the people affected by the decision in the review loop. [Read the source](https://x.com/p_mccrory/status/2014281227663524038). ## ✅ Action Items - DevRel: turn claims into testable demos; OSPO: track governance and dependency effects; Community: invite affected groups into review; WordPress — Core: assess platform impact; Core Performance: measure cost and latency; Core AI: define model-specific tests; Core Program Team: coordinate milestones; Mobile: test small-screen use; Playground: build a reproducible demo; Community: gather contributor feedback; Training: create a lesson; Marketing: state limits; Support: collect failure patterns; Design: review workflows; Documentation: record behavior and caveats; Photos: not applicable unless visual assets are needed; TV: consider a short explainer; Polyglots: plan translation context; Accessibility: test WCAG 2.2 AA; Meta: review site and API effects; CLI: expose repeatable checks where relevant; Hosting: test deployment constraints; Tide: add automated quality checks where applicable; Openverse: review open-asset implications; Themes: test presentation effects; Plugins: publish compatibility guidance. The WPOCC: consider community-governance effects. FAIR: note implications for federated open-source collaboration. ## 🧪 Hypotheses 1. If task automation does not imply full job automation because jobs contain linked responsibilities., teams will observe a measurable change in decision quality or failure rate. 2. If teams test the mechanism in a bounded pilot, results will differ by task complexity and user expertise. 3. Publishing limits beside outcomes will reduce overgeneralization in later decisions. ## 📊 Methodology Use a preregistered comparison with a baseline, clear unit of analysis, task-level outcomes, failure categories, cost and time measures, and interviews with affected users. Preserve raw inputs and report null results. For a short announcement, first obtain primary documentation and reproduce the stated behavior. ## ❓ Questions - Which claim would change the decision if it proved false? - What is the correct unit: task, job, team, organization, or ecosystem? - Which groups bear costs that the source does not measure? - What evidence would distinguish adoption from dependable outcomes? ## 🔮 Future Research Replicate across organizations and user groups; compare short- and long-term effects; measure distributional impact; test alternative explanations; and track whether early gains survive operational use. ## 💡 Implications Practice: use bounded trials. Policy: require traceable evidence for high-impact claims. Security: inspect failure paths and dependencies. Education: teach evaluation, not tool loyalty. Funding: tie continued spending to measured outcomes and public limits. ## 🧠 Learning Styles Assessment - Visual: add a claim-to-evidence diagram. - Aural: discuss the argument and counterargument aloud. - Verbal: rewrite the thesis in plain language. - Kinesthetic: run the proposed pilot. - Logical: map premises, mechanism, evidence, and conclusion. - Social: compare interpretations in a small group. - Solitary: keep a prediction and error log. - Naturalistic: examine resource and environmental effects. - Reading level: approximately grade 10–12; technical or institutional terms need definitions. ## 📊 Accessibility Assessment - Perceivable: provide alt text, captions, sufficient contrast, and text equivalents (WCAG 1). - Operable: support keyboard access, visible focus, and adequate target sizes (WCAG 2). - Understandable: use clear headings, definitions, and consistent navigation (WCAG 3). - Compatible: use semantic markup, valid names, roles, and values (WCAG 4). - Cognitive: shorten dense passages and expose the argument structure. - Motion and media: avoid forced motion; provide controls and transcripts. - Testing: combine automated checks with keyboard, screen-reader, zoom, reflow, and cognitive review against WCAG 2.2 AA. ## 🌍 DEIB Assessment - Cultural breadth: identify the source’s geographic and institutional scope. - Inclusive language: separate groups from stereotypes and avoid universal claims. - Neurodiversity support: provide summaries, headings, examples, and predictable structure. - Representation: seek evidence from people affected by the proposed change. - Psychological safety: invite dissent without requiring public disclosure of harm. ## ✅ Logical Validity The essay uses several independent indicators and states uncertainty. Limits include US scope, short observation windows, internal-company evidence, exposure measures that may not match real adoption, and confounders such as interest rates and remote-work shifts. - Strong reasoning: the source offers a clear thesis and at least one mechanism. - Fallacy check: watch for hasty generalization, selection bias, false cause, motive attribution, and analogy used as proof. - Fix: add comparison data, definitions, uncertainty ranges, and counterevidence. - Tone: explanatory and persuasive. ## 🛡️ DARVO Analysis No complete DARVO sequence is established by the captured source. Where conflict appears, separate denial, criticism, and claims of harm rather than assigning a pattern from rhetoric alone. ## 🎯 Conclusion Task automation does not imply full job automation because jobs contain linked responsibilities. Next, test the mechanism against a baseline and preserve the source’s stated limits. ## 🧱 Refactor Appendix ### Literature Split Pad - Source claim: The essay argues that recent US labor data does not yet show a material AI-driven rise in unemployment. AI remains skill-biased and labor-augmenting because jobs contain mixed tasks, model capability is uneven, and expert oversight still determines outcomes. The evidence supports caution about present claims, not certainty about the future. - Evidence state: captured source analyzed; linked claims need primary-source checks. - Cross-links: [[ai-labor-market]] [[labor-augmentation]] [[occupational-change]] [[productivity]] [[human-expertise]] #### Atomic Split Pad - Task automation does not imply full job automation because jobs contain linked responsibilities. - Uneven model capability raises the value of expert oversight and recovery. - Weak links cap system-level productivity even when one production metric jumps. #### Fleeting Queue - What observation would falsify the central claim? - Which existing vault note should receive each atom? - Revisit after new evidence or a material product change. <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Tweets/Why Hasn’t AI Increased Unemployment.md|Why Hasn’t AI Increased Unemployment? by Peter McCrory]] ## Highlights - I thought I’d share a few high-level reflections and a framework that helps me make sense of why we (so far) don’t see significant impact of AI on the US labor market. I focus on the US because (a) AI adoption is high here, (b) it’s the world’s largest economy, (c) [compared to Europe](https://www.ecb.europa.eu/pub/pdf/sintra/ecb.forumcentbankpub2025_Schoefer_paper.en.pdf), our labor market institutions historically facilitate faster adoption of labor-displacing technologies, and (d) we have an unusually rich array of labor market statistics for understanding current conditions. I shared these thoughts recently within Anthropic. ([View Highlight](https://read.readwise.io/read/01kya5qs4ngfxgktg9awv6w2g8)) - Note: Central claim captured during deep read. - Tags: labor-augmentation, ai-labor-market - First, AI adoption is high in the US. So it’s reasonable to look for its effects on productivity, or on unemployment. Labor productivity growth has been strong in recent years, and there’s suggestive evidence that AI has partly contributed. ([View Highlight](https://read.readwise.io/read/01kya5qt2268c2nvccevrf7w1n)) - Note: Supporting mechanism or evidence captured during deep read. - Tags: ai-labor-market, labor-augmentation - Now, the future is still quite uncertain. Model capabilities are advancing rapidly, and AI systems may soon be able to [autonomously develop](https://www.anthropic.com/institute/recursive-self-improvement) their own successors. More generally intelligent AI systems could lead to labor displacement that hasn’t yet materialized. Whether that might happen (and how quickly) is an open question, one my team is working to understand. ([View Highlight](https://read.readwise.io/read/01kya95ts2j3jafdr21gy3stg7)) - Tags: 👻 ai highlighted - **So far, AI is both *skill-biased* and *labor-augmenting*.** It complements domain expertise. It relies on humans in the loop to direct and evaluate the most complex work. And it rewards AI proficiency. Model capabilities are improving fast, but remain [stubbornly jagged](https://helentoner.substack.com/p/taking-jaggedness-seriously). To fill in the pockets of the jagged frontier, expert oversight is needed to steer incredibly capable AI systems, and to recover when they falter. ([View Highlight](https://read.readwise.io/read/01kya95tsvm8pb4qtwnqxcejeh)) - Tags: 👻 ai highlighted