By Yuil Tripathee (650 7050 3480)
- Activity Overview for Week 8:
Conducting User Interviews
Reasons to conduct user interview:
- Cheap and easy way to get valuable insights of product and user environment
- Make better product design decision
- Realistic feature set can be delivered to users (being relevant -> PACT Context part)
- Suggestions and improvement can be brought in
- Need and requirements of the product can be properly analyzed
- FEEDBACKS can be gained as an insight and as a valuable insider data
It is a great way to extract information and to understand user interface. Still, there are some shortcomings of this technique:
- False intel provided by people
- Memory issues, human error can lead to bad product decisions
- Users are yet not the designers. So, we should take it seriously but not as a whole.
- Wider demographics would want extensive feature sets tailored to their need.
<aside>
💡 Don’t get colored by the opinion of others until you’ve finished the product envisioning. Then you can compare the intel from external source and evaluate with your team if their idea works. Otherwise, the world would be deprived of having your noble idea coming to reality just because of someone’s prejudice.
</aside>
Source of quote: I know him personally as a mentor. Can’t disclose the source here.
7.1 User Interview Techniques:
One of the famous techniques involved is notetaking. The variants are: