The analyst handed me a 40-page PDF, and I knew it would never get a link in that form

The analyst handed me a 40-page PDF, and I knew it would never get a link in that form

A logistics company had real findings on shipping delays by region. The question was packaging: ship the full report, or distil it into a single interactive map.

We A/B-ed it across two pitch waves. The PDF went to ten reporters with a tidy summary email. Two replied, one covered it, and the link pointed to a gated download form — which the reporter's editor stripped, so we lost the link entirely.

The interactive map went to the next ten. It lived on one open URL, no gate, and let a reader click their own state and see local delay data. Seven reporters embedded it, every embed carried a link to the map's page, and three of them localized their whole story around their region's number — coverage we never could have gotten from a national PDF.

"I can drop your map straight into the article," one wrote. "That's why you got the link."

Lesson: a report is a document reporters read; a visualization is an object they can place in their own story, and embeds carry links by nature. If your data has a geographic, temporal, or comparative shape, the interactive nearly always out-earns the PDF. Gate nothing you want linked.