3 ms·
I mean, if you're solving it for yourself first and foremost, it doesn't really matter either way. But if you intend the thing to be a business, with customers
by mindcrime 8y ago
I mean, if you're solving it for yourself first and foremost, it doesn't really matter either way. But if you intend the thing to be a business, with customers who pay you money, you should probably find out if there are actually other people who feel the same pain as you, and are looking for a solution like what you're building. Otherwise you risk spending a lot of time and energy on something and only then finding out that there's no market for it.
As for fragmentation... I get where you're coming from on that. But I think you can choose to incorporate the feedback you receive from others, or not. The simple act of talking to other people and receiving their input shouldn't, in and of itself, do you any harm. And if you find that there are people who want/need the "thing" you started out building, then the onus is on you to own the vision for it and to make sure it gets built properly. A big part of "product management" is, indeed, saying "no".
OTOH, you may find that nobody wants exactly what you plan to build, but that there's some minor tweak that would suddenly make it desirable to a huge market. If that happens, then you have the luxury of being able to decide which way you want to go... make it a viable business, or treat it as more of a work of art.