Ask HN: How do you know if a tool is solving a real problem?
3 comments
It would be good to know in advance, but I think the best validation is when the problem recedes to the position of "solved".
You can't do much better than that.
So maybe you have to first make sure your approach will address a real problem to begin with, than consider how much of a complete solution it could possibly amount to.
You can't do much better than that.
So maybe you have to first make sure your approach will address a real problem to begin with, than consider how much of a complete solution it could possibly amount to.
If someone uses it without you prompting them, then tells a third person — that's usually the clearest signal. The hard part isn't measuring usage, it's whether it spreads without you pushing it.
I’m building a system that sits between application events and downstream consumers (analytics, decision systems, AI, etc.).
The goal is to make raw product events more structured and canonical, so deriving patterns, insights, and higher level signals becomes easier.
Before going deeper, I’m trying to sanity check the problem itself:
* How do you validate whether a tool like this is actually needed?
* Have you felt real pain around event schemas / analytics / telemetry?
* What tools already solve this well (or badly)?
* What would make you try a new solution here?
Not pitching, just trying to avoid building something nobody wants
Would love to hear your experiences.
Thank You