As a UX practitioner, one cannot satisfy each and every user
During the whole design process, sometimes it can get overwhelming to cater to each and every
user. It is important to keep in mind that design is always made such that it caters to the
majority of the population and unless a pattern in user responses emerge, we must not obsess
over user comments. Yes, we should think about the possibility of including their
suggestions/responses but if those scenarios have already been backed up by data and a reason
that certain features weren't included or done a certain way, then we must stick to them and
revisit later if need be.
Follow up on leads found in user interviews
When we first started our research, our aim was to help students with dietary restriction find
food at grocery stores. However, while interviewing few users during the initial stage, users
said that they had more issues finding meals at a restaurant. As we saw a pattern emerge, we
wanted to explore this area more and modified our interview questions to fit a broader scope. As
it turns out, many more users had issues finding meals at restaurant which led us to pivot from
our aim. This helped me remain relevant and actually solve a problem that users faced.
Sometimes an App is the best solution
When we started ideation phase, we really wanted to push more than a digital
solution because but during our brainstorming sessions, it started becoming clear that given
the problem space, an app ticks all the check boxes for solving various pain points. An app was
the most feasible and creative solution given the technology constraint. This was even verified
during the feedback session, as the one element of physical interaction that our solutions had -
using QR or AR camera was also rejected by users and deemed unnecessary.
When in doubt, always refer back to the data
This was particularly helpful when we were deciding on features for the app and helped resolve a
lot of conflicts before they turned ugly. Turning back to the data was also helpful as it showed
us at times, that we didn't have enough data to make a claim or that we didn't cover that aspect
in our feedback sessions. In these cases, we went back to the users and asked them more
questions before deciding on the final features.