6: AFFINITY MAPPING
A useful way to visualize and organize wants and needs from multiple users is to sort them and re-sort them until some commonality emerges.
7: COMPETITIVE ANALYSIS
My interviews revealed a few solutions that users are already familiar with. I want to know what strengths and weaknesses each one has, this will come in handy downstream when I start to craft a feature set.
7: COMPETITIVE ANALYSIS
Through detailed analysis of these existing solutions, I am able to categorize them into four distinct types, each having their own respective properties.
8: PERSONA
As I move forward, it’s important to craft a persona that represents the general wants/needs revealed in the interview process. This allows me to have a touchstone that I can come back to as I verify experiences during development, and is also very useful in relaying what’s important to other stakeholders on the team.
9: STORYBOARD
It’s important to remember that the experiences that we are crafting do not occur in a vacuum. The real world is chaotic, messy, and our attention is often divided. I observed people choosing produce at the market, and crafted a simple narrative for how the experience could be improved, in this case by showing how a user could easily access info on how to select an avocado.
10: PROBLEM STATEMENT
Young adults need a way to know how to select produce because it’s hard to know how to eat “better” even if you want to.
11: HYPOTHESIS
I believe that by making produce easier to learn about and choose produce for young adults, we will achieve more satisfying relationship with food. We will know this to be true when users can choose ingredients with more confidence.
12: HOW MIGHT WE?
How might we make produce easier to choose? How might we make learning about food more convenient? How might we make trying new foods less intimidating?
13: FEATURE PRIORITIZATION
Through observation, research, and brainstorming, I amassed a healthy list of features that could be incorporated into the app. It’s easy to shoot for the ultimate version of your product, but feature creep can easily turn a good idea into one fraught with usability pitfalls that becomes a development nightmare. Through analysis, I want to determine what is the minimum viable product that will satisfy the hypothesis. Additional features can always be implemented once real user feedback is obtained after launch.