Are you sure most existing solutions really solve someone’s problem well? 👀
1. Guys, I’ve been noticing more and more often in the comments something along these lines: «This problem was solved many years ago, here’s a solution I found on Google in 1 minute».
2. Yes, most often, a problem you see on ProblemHunt at first glance seems to be already solved. And I fell into this trap myself. For example, for one of the problems on PH that I wanted to solve, I found at least three solutions in my search, one of which was created as much as 4 years ago. BUT after a call with the person experiencing the problem, it turned out that the existing products solved it at most 20–30%, and a lot still needed to be improved.
3. Even for one of my own problems, which I published a few months ago, I received comments like this: «Why solve this problem and create a new solution if this product already exists?». Without understanding the depth of my problem, the specifics of my work, and other nuances, they simply advised me to «forget about it» and do things differently, which ultimately didn't solve my problem but only created additional difficulties and friction.
4. Yes, you might indeed come across problems for which ready-made solutions exist that the user might not have been aware of — for example, because they simply didn't search well enough for a solution. But such people, in my observation, are in the minority. It's just that most problems require deeper research, and without personal communication with the people experiencing them, you will only see the tip of the iceberg. Dig deeper, otherwise you risk missing something valuable.
5. This is precisely why ProblemHunt provides direct contacts of the people who shared the problem. 😊
P.S.: One of the most striking examples is Dropbox. Before Dropbox, there were dozens of solutions, but none of them solved the problem properly, so people didn’t use them.
Replies
vibecoder.date
It all comes down to, you don't know what you don't know.
If all I hear is you need a cloud storage solution I know 10 products off the top of my head, but they cover different things, I don't know the size of the data, availability requirements, regulatory ones, etc.
Only you can communicate the needs based on your domain expertise. And that's what gets missed, we place products into categories and we exalt them as law when in reality they are mere labels, linguistic shortcuts.
When you truly understand a problem, you know exactly how the existing solutions are lacking.
The fundamental issue is that most of us are too busy or preoccupied to think deeply about the problems we wish to solve. As an example, I've been itching to build a coding tool, a agentic coding harness. My needs are specific, they are so distinct from products I have seen out there. Claude code gets close but it's 60% at best.
What I require to move as fast as I know I can is too complex to dive into here, Suffice to say I have been planning and researching how to achieve it, the logic I need, the capabilities I want. Because of this effort and thought I have come to understand the different offerings and products out there.
But in trying to articulate my exact needs here, would I be successful? I don't know what I don't know, but perhaps more importantly, I don't know what you know know. I am ignorant of the baseline assumption the reader or listener might have.
So we must be explicit and specific as much as it pains us, it's the price of clarity. (And know how much I mean that since I loathe the buzzword)
We must be willing to approach the problem scope naively, assumptions often hold us back unless they have proven useful.
ProblemHunt
@build_with_aj Thank you for such a thoughtful and well-articulated response — you put into words exactly the nuance I was trying to highlight.
I especially liked how you framed the idea of “not knowing what we don’t know” and the danger of reducing problems to labels and categories. That gap between a surface description (“we need X”) and the real, domain-specific constraints is precisely where most existing solutions quietly fall apart.
Your example with agentic coding tools resonates a lot. From the outside it looks like “this already exists,” but once you’ve done the hard thinking and lived with the problem long enough, you can see very clearly where current products only cover 20–60% of what’s actually needed.
That’s exactly why I believe conversations with real users matter so much — without them, we only ever see the tip of the iceberg. ProblemHunt is my attempt to make those deeper conversations easier to start.
Really appreciate you taking the time to write this — comments like yours are what make the discussion valuable. 🙏
ProblemHunt
Guys, I’m interested to hear your opinion on this :)