I thought I was building a news visualization tool. Users thought it was a catch-up tool.
I've been building a side project called NewsSphere (https://newssphere.app/).
The original idea was pretty simple: organize news around stories instead of individual headlines and help people understand how events evolve over time.
I thought I was building a news visualization tool.
After sharing it publicly and talking to users, something surprising happened.
Almost nobody talked about the visualization.
Instead, people kept saying things like:
- "Catch me up."
- "Help me understand what changed."
- "People miss the thread."
One user described the problem as seeing only fragments of a story over several days and losing the bigger picture.
Another pointed out that a single crypto story can generate dozens of headlines, but most people only see whichever headline their feed happens to show them.
The more feedback I collected, the more I started wondering whether the real problem isn't information overload.
Maybe it's context loss.
People don't seem to need more headlines.
They need help reconnecting the dots after they've missed part of the story.
This has probably been the biggest lesson from sharing NewsSphere so far:
Users rarely describe your product the way you do.
Sometimes the most valuable feedback isn't about improving the product.
It's about helping you understand the problem you're actually solving.
Has anyone else experienced users consistently describing their product differently than they did?
Had almost the same experience. I built My Rundown thinking the core feature was AI summarization. Users who stuck around described it differently: "I don't have to remember to open another app." The delivery model was the thing, not the AI.
Took me a while to stop leading with "AI summaries" and start leading with "your reading list shows up in your inbox." Same product, completely different framing.
Your catch up framing is probably the right one. "Help me understand what changed" is a much more specific job than "visualize the news."
This matches something I keep running into. Users don't categorize products by their architecture, they categorize them by the moment they reach for them.
You've already had the important realization — users named the job (catch me up) while you named the mechanism (visualization). That gap is the whole post and you read it correctly. So the useful thing now is what you do with it.
The reframe has direct consequences for everything downstream:
Positioning: "news visualization tool" describes how it works. "Catch up on any story in 30 seconds" describes what they get. Your users handed you the hero copy verbatim — "catch me up" and "what changed" are the literal words to put on the page. Stop translating them into your language.
Product priorities shift too. If the job is context-recovery, the visualization is a feature, not the point. The most valuable thing becomes "here's what you missed and why it matters," not "here's a pretty timeline." Some of what you built for the visualization vision might be polish on the wrong axis.
The wedge gets sharper by category. You mentioned crypto — a single story spawning dozens of headlines is the acute version of context loss. Crypto, politics, ongoing legal cases, sports seasons — fast-moving multi-headline stories are where "I lost the thread" hurts most. "Catch up on any story" is broad. "Never lose the thread on a developing [crypto/political] story" is a wedge with a specific audience who feels it daily.
On your actual question — yes, this is one of the most common founder experiences, and the ones who win are the ones who let users rename the product. The founders who lose argue with their users about what the product "really" is.
What's the catch-up moment people described — daily check-in, returning after a week away, or jumping into a story they never followed? Each is a different product.
What stood out to me isn't that users described the product differently.
It's that they may be describing a different problem altogether.
Those sound similar on the surface, but they can pull a product in very different directions once you start building around them.
That's a really good observation.
The more feedback I've received, the more I've been wondering about exactly that.
The original idea started with organizing news around stories rather than individual headlines, but many users seem much more focused on the experience of losing context and trying to catch up after they've missed part of a story.
Those sound related, but I agree they could lead in different directions.
At the moment I'm trying to resist jumping to conclusions and collect more evidence, but it's definitely one of the biggest things I'm thinking about right now.
Appreciate the perspective.
I think that's a sensible instinct.
The reason it caught my attention is that I've seen products end up in very different places depending on which of those explanations they build around.
Happy to send over the fuller thought if it's useful — just drop your email.
I'd love to hear it.
That comment actually resonated with me because it's something I've been thinking about since I started getting feedback from users.
Feel free to send it over. My email is [email protected]
Appreciate you taking the time.
Sent it over.