“No One Reads Anything.” And Yet We Keep Publishing

We keep telling ourselves that articles matter. That nuance still lives somewhere past the headline. But for most users, the headline is the story. Anything beyond that is already optimistic.

There is a product principle that gets repeated, usually with a half-smile: no one reads anything. Not documentation, not emails, not UI copy, and definitely not news past the headline. It sounds like a joke, but it is really a design constraint. The uncomfortable part is not that it is wrong. It is that it is just accurate enough to shape how we build.

Somewhere along the way, we accepted a contradiction. We produce more content than ever — articles, explainers, threads, summaries — while knowing most of it will not be read. Not in any meaningful way. At best, it gets scanned, skimmed, reduced to a headline and a vague sense of what happened. At worst, it is replaced by a two-line AI summary that sounds confident enough to pass for understanding.

Yet in newsrooms and product meetings, we still talk as if depth is the default. As if the average user is moving patiently from paragraph one to paragraph twelve, collecting nuance, context, and background along the way. It is a comforting fiction. Operationally, it does not hold up.

The so-called Miller Principle, or at least its modern version, forces a different perspective. If no one reads anything, every extra sentence is not just ignored. It becomes a liability. It is a bet that the user will invest attention they do not have. Most of the time, they do not.

Now, place this reality inside news consumption.

We expect users to understand geopolitical nuance, historical context, and conflicting narratives. We expect them to distinguish signal from noise, fact from framing, reporting from opinion. And we package all of this inside a structure that assumes time, focus, and patience. Then we act surprised when the headline becomes the story.

This is not a failure of the audience. It is a mismatch between product design and human behavior.

The uncomfortable implication is that the headline is not just an entry point. For many users, it is the whole experience. Any nuance not present there is not just hidden or delayed. It is lost.

This leaves us with a quiet editorial dilemma. Do we optimize for accuracy or for attention? The industry has been trying to do both and often ends up with neither: headlines too vague to inform, articles too long to be consumed.

Now add AI, and the problem shifts. It is no longer just about attention. It becomes a question of what users actually know.

AI does not just shorten content. It rewrites it into something that feels finished. A clean paragraph, a few confident statements, sometimes even a tidy conclusion. Ambiguity disappears. The user gets an answer, no effort required.

And that is precisely the problem.

When AI simplifies, it does not just remove words. It removes tension and uncertainty. It smooths out the messy edges where real understanding usually lives. What remains is a version of reality that is easier to process, and therefore easier to trust.

We are entering a phase where users are not just skipping the article. They are skipping the existence of the article altogether.

In this world, the role of a news product shifts. It is no longer just about publishing content. It becomes about managing how much of reality survives the process of compression.

This is where things get uncomfortable for product leaders. The trade-offs become harder to ignore.

If you take the ‘no one reads anything’ principle seriously, the answer is not to simplify everything. It is to design for selective depth. Accept that most users will stay at the surface, but make sure the surface is not misleading, and that moving deeper does not feel like a penalty.

Right now, depth often feels like a penalty. Long articles, dense paragraphs, context buried out of sight. The product signals: if you want nuance, you pay with your time. Most users do not take the deal.

The real challenge is not to make users read more. It is to make every extra second of attention disproportionately valuable. The goal is a system where understanding is layered, not hidden behind a wall of text.

But here is the tension. The more efficient the experience, the easier it is to consume a simplified version and move on. Efficiency and understanding do not always align. Sometimes they work against each other.

This leads to a slightly uncomfortable question.

If no one reads anything and AI explains everything, what are we actually optimizing for?

If the answer is speed, we are doing well. If the answer is understanding, we may be designing ourselves into a corner where users feel informed without actually being informed.

That is a much harder problem than low engagement or high bounce rates.

It is a product problem. It is an editorial problem. And increasingly, it is a trust problem.