Most “news” is a summary of a summary. Here’s what I found when I went back to the origin.
A few months ago, I caught myself reading the same story for the fourth time.
Same company. Same announcement. Four different articles, each a slight rearrangement of the same handful of sentences. I had spent twenty minutes reading four versions of one thing, and I still couldn’t remember the actual numbers.
That was the moment I realized: I wasn’t reading news. I was reading summaries of summaries.
The chain of whispers
Most of what we call “news” today is structured like a very polite game of telephone.
A company publishes a press release or a research paper. A reporter reads it, condenses it, adds a framing angle. An aggregator reads the reporter, condenses that further, adds a headline. A newsletter reads the aggregator, condenses that, adds emojis. A Twitter account reads the newsletter, condenses it to 280 characters, adds a take.
By the time the story reaches me, it has passed through four filters, each one stripping nuance and adding opinion. I’m not reading what happened. I’m reading what five different people, each with their own incentives, thought I should know about what happened.
This is not a conspiracy. Each link in the chain is doing honest work. The problem is the chain itself.
What happens when you go to the source
One evening, instead of opening my usual news feed, I decided to do an experiment. I picked three topics I cared about — a specific competitor, a regulatory area, a research field — and I went directly to the source.
I bookmarked the competitor’s blog and press page. I bookmarked the regulator’s announcements page. I found the journal where the research gets published.
The first thing I noticed: the primary sources are not hard to find. They’re just not optimized to be found. A press release doesn’t have a click-bait headline. A regulatory notice doesn’t have a hot take. A research paper buries the interesting finding on page eleven.
The second thing I noticed: they’re longer. A press release might be 800 words. A research paper is thousands. Reading the source takes five to ten times longer than reading the summary.
The third thing I noticed: it was worth it.
When I read the press release, I understood the actual announcement. The specific numbers. The specific product. The specific language the company used, which often revealed more than the language the reporters used.
When I read the research paper, I saw what the authors were actually confident about, versus what a headline had turned into a confident claim.
When I read the regulator’s notice, I saw what was binding, what was advisory, and what was still in comment period — distinctions that almost never survive a news article.
I was getting better information. I just wasn’t getting it often.
Become a Medium member
The problem with “primary source reading”
Here is the honest trade-off: reading primary sources is slow. It requires visiting different sites, checking different RSS feeds, learning which pages get updated and which don’t. Some press pages don’t have RSS. Some research journals lock everything behind paywalls. Some regulators publish on platforms built in 2003.
After a month of doing this manually, I had a clearer understanding of my topics than I’d had in years — and also, I had stopped doing it. The overhead was too high. The news feed, for all its flaws, was easier.
This is the gap I ended up building into.
What I built, and why I built it the way I did
I built OriginBrief because I wanted the quality of primary-source reading without the overhead of primary-source monitoring.
A few deliberate choices:
Weekly, not daily. Most “research tools” push updates constantly. But primary sources don’t move that fast, and the point of reading primary sources is that you’re not reacting to every tremor. One thoughtful weekly report beats fifty push notifications.
Cited, not summarized away. Every claim in the report links back to the source document. You can always verify. You can always read the original. The AI does the monitoring and structuring; the judgment stays with you.
Themes, not keywords. You don’t register “Tesla” or “autonomous vehicles.” You register a research theme — the thing you actually care about — and the system figures out which sources are relevant. A theme can have 5 or 15 sources, and you choose.
Focused, not exhaustive. The product only offers two plans: two themes or five. Not fifty. Because focus is the point. If you have fifty research themes, you don’t have research themes — you have a feed.
What I learned in the process
Building this taught me something I didn’t expect: the reason “news” feels bad isn’t that there’s too much of it. It’s that most of it isn’t actually telling me anything new.
When I started reading primary sources, the volume dropped dramatically. A week of real information was maybe ten or fifteen documents, not five hundred tweets. And yet I felt more informed, not less.
This is, I think, the real signal-to-noise problem. It’s not that the signal is hard to find. It’s that we’ve built an entire industry around packaging the noise to look like the signal.
A small reflection
I don’t think everyone should stop reading the news. I still read it — for breaking events, for context, for entertainment. I just don’t rely on it for understanding anymore.
For the topics I actually need to understand, I go to the sources. And I built a tool to do the going-to-sources part for me, because that’s the part I kept failing at.
If this resonates with you, you can try OriginBrief at originbrief.app. Starter is $33/month, with a 7-day trial. If it doesn’t, that’s fine too — I hope the rest of this essay was useful anyway.
Either way: the next time you find yourself reading the same story for the fourth time, consider going one link up the chain. You might be surprised what you find when you reach the origin.
— Aritomo
https://www.originbrief.app?utm_source=dev.to&utm_medium=blog&utm_campaign=news
Top comments (0)