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 &quot;approval&quot; answers. It&#x27;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 &quot;correct&quot; way to align the response.<p>Separately:<p>&quot;If I made a new service x would you like it&quot; is not the same as &quot;if I said it would cost you $5 to use new service x would you use it&quot; is not the same as &quot;do you think new service x would be useful&quot; is not the same as &quot;do you think anyone else wants new service x&quot;<p>It&#x27;s very easy to mistake these for &quot;the same&quot;<p>I am personally very skeptical of NPS and satisfaction scores in small communities. They may work for google scale entities, I don&#x27;t think they do for &lt;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.