If I need to get feedback on a feature, I build a prototype, and then show it to one or two people (friends, family, customers that sent feature requests). I te

If I need to get feedback on a feature, I build a prototype, and then show it to one or two people (friends, family, customers that sent feature requests). I tell them roughly what they should do, and watch if they can figure it out. Then I change things as necessary, and show it to the next person. Usually a handful of people are enough to find the the major issues. - don't "burn" beta testers. show a prototype to one or two people, and don't show it to more people before you fixed the issues that have come up. otherwise you just get duplicate feedback - ask people personally. Emails to a group of people are ignored by 99% of recipients - feel free to ignore advise from testers. everyone always wants to give advise, but that is irrelevant. the important part is: did the tester manage to complete the task? - do not ignore people struggling with your app. the natural reaction to people failing to use your app is to think they are stupid. they aren't. most of the time your ui is stupid and you need to fix it. it doesn't matter how brilliant you think the ui is, if testers can't use it, change it. - sometimes the answer is that what you built doesn't work and you just wasted a lot of time and you need to throw it away and start over. do not ignore this possibility