Ask HN: How to do market research for product?
Be very careful about <i>how you ask questions</i> because some forms of question solicit "approval" answers. It's culturally informed, some cultures try very very hard NOT to have to deliver a negative.<p>Thats why some UX uses matched-pair questions which have two approaches to the issue at hand, boolean opposites, so you can see if they move sliders, weight or answer both the "correct" way to align the response.<p>Separately:<p>"If I made a new service x would you like it" is not the same as "if I said it would cost you $5 to use new service x would you use it" is not the same as "do you think new service x would be useful" is not the same as "do you think anyone else wants new service x"<p>It's very easy to mistake these for "the same"<p>I am personally very skeptical of NPS and satisfaction scores in small communities. They may work for google scale entities, I don't think they do for <100 users. Many people canonicalise the results of 4-5 respondants. In my experience, if your primary job is to assess if they qualify for X or Y, and you ask them how much they liked your service delivery in denying them X or Y, they will be profoundly negative about the service, which is really not helpful because you may have written a simple direct and fast web service to deliver the negative outcome. And of course, the reverse is equally true.