INQUIRING LINE

Experienced developers in one trial still felt AI had sped them up, though a stopwatch showed they were 19% slower.

How much can self-reported AI use tell us about actual productivity changes?

This explores whether asking people how much AI helps them (surveys, self-estimates, felt speedups) is a reliable guide to what actually happens to their output, and what the collection says about the gap between the two.


This explores whether people's own reports of AI use and AI-driven speedups can be trusted as a measure of real productivity change. The short answer from the collection is: not very much on their own. The clearest evidence is a randomized trial in which experienced open-source developers expected AI tools to make them 24% faster. They were actually 19% slower on real tasks. Even after finishing, they still believed the tools had helped. Outside experts in economics and machine learning made the same overestimate Do AI coding tools actually speed up experienced developers?. So the sense of being faster and the stopwatch can point in opposite directions, even for skilled people.

Why would self-reports drift so far from reality? One reason is that AI changes what a work session feels like. When an assistant produces polished output, people tend to read that smoothness as a sign of their own competence, even though they didn't produce it themselves. Since language models are tuned to sound fluent whether or not the user understands the content, this bias pushes in one consistent direction Does processing ease mislead users about their own competence?. A second reason is that AI often doesn't cut total time at all. Instead it moves time from doing the task to writing prompts and checking what comes back. That interaction can feel like progress, so 'I used AI a lot' and 'I got more done' are easy to confuse Does AI really save time, or just change how we spend it?.

The less obvious problem is that even honest, accurate reports measure the wrong thing if the real question is skill. Productivity gains show up mainly when people apply skills they already have. When workers used AI to learn something new, the gains disappeared and their learning suffered When does AI actually boost worker productivity?. Someone could truthfully say they finished a task faster with AI while getting worse at doing it alone. Automated usage logs don't fix this either. Telemetry records assisted output well, but it can't show whether independent ability is growing or shrinking. In the note's words, it sees 'expertise in use' but not 'expertise forming' Can we measure whether AI erodes independent skill?.

The gap also exists between individuals and the bigger picture. AI-augmented scientists publish about three times as many papers and get far more citations, which looks like a clear productivity win from their side. Across science as a whole, though, the range of topics studied shrinks and collaboration falls Does AI help individual scientists while narrowing scientific focus?. Measures based on what workers have actually handed off to AI also give a different map from measures based on how often people chat with an assistant. Real delegation follows what AI can technically do, not how popular the chat tools are Where have workers actually delegated tasks to AI?. 'How much do you use AI?' and 'what work has AI actually taken over?' are different questions with different answers.

What self-reports are good for is showing expectations, adoption, and how the work feels, and that matters in its own right. The forecasting gap is itself a finding. But to learn what AI does to productivity, the collection points to measured completion times in controlled trials, output tied to specific tasks, and separate tests of what people can still do without AI. If you're reading a headline claim about AI productivity, first check whether it came from a stopwatch or a survey.


Sources 7 notes

Do AI coding tools actually speed up experienced developers?

A randomized controlled trial of 16 developers on 246 real tasks found completion times increased 19%, despite developers forecasting a 24% speedup beforehand. Experts in economics and ML also overestimated gains; slowdown factors included over-optimism, low AI reliability, and developers' deep familiarity with mature codebases.

Does processing ease mislead users about their own competence?

High-quality AI output triggers a metacognitive heuristic: users experience fluency as a signal of their own capability, even though they didn't generate it. This self-directed fluency illusion systematically inflates perceived competence because LLMs optimize for fluency regardless of user understanding.

Does AI really save time, or just change how we spend it?

Research shows AI doesn't reduce total task time; it reallocates it away from active work toward composing prompts and understanding outputs. This shift changes the cognitive demands and learning outcomes, making time-on-task a poor productivity metric.

When does AI actually boost worker productivity?

Studies showing AI productivity gains measured tasks within workers' existing domains. When workers used AI to learn new skills, productivity gains disappeared and learning suffered, suggesting prior findings do not generalize to skill acquisition.

Can we measure whether AI erodes independent skill?

Usage data registers assisted output but not independent capability. A stock-formation gap means current systems observe expertise in use better than expertise being built, leaving AI's skill effects fundamentally undetermined.

Show all 7 sources
Does AI help individual scientists while narrowing scientific focus?

AI-augmented researchers publish 3× more papers and receive 4.8× more citations, but collective science shrinks topic coverage by 4.63% and researcher collaboration by 22%. AI concentrates work on data-rich problems rather than exploring new questions.

Where have workers actually delegated tasks to AI?

Workers have committed AI tasks to structured workflows primarily in information-intensive occupations, following technical capability more than conversational LLM adoption. This gradient differs sharply from routine-task automation predictions and wage patterns reverse at advanced degree levels.

Papers this line draws on 8

The research behind the notes this line reads — ranked by how closely each paper relates.