Ask HN: How do you know if you have a product problem or a distribution one?
I keep building products, ideas etc that are I think are good and solve people's issues at least what I see them complain about but it doesn't result in any meaningful traction. When I ask people to use something its either non-existent or you just get ignored even though it solves the issue they describe.
Do I have a distribution/outreach issue or am I just building crappy stuff nobody wants ?
I do all the recommended steps of getting an ICP and then doing difficult things that don't scale but it goes nowhere.
8 comments
[ 0.21 ms ] story [ 2.2 ms ] threadThe reason why I take this approach is that - I have had personal experience building tools that didn't go anywhere, and same tools built by people with some online following gaining good traction. It could simply be a case of anecdotal experience, but distribution has always been harder for the tools I have built.
It means the world, you see taste makers based on their legacy and previous actions.
Never in time have there been a thinner line between average and genius.
So any product you build must not only solve the core problem but must require less skill than their existing workaround and make switching as easy as possible.
Distribution is a challenge even for the best among us, but in your case you seem to be hitting a snag earlier. My advice would be to not demotivate yourself by asserting you may be building crappy stuff, but instead try and see if you're optimising incorrectly? Good luck!