Optimizing grocery shopping
Solo project
Fall 2023
Duration: 5 weeks
My role: lead designer
Tools: Figma
Optimizing grocery shopping
Solo project
Fall 2023
Duration: 5 weeks
My role: lead designer
Tools: Figma
Fall 2023
Optimizing grocery shopping
Duration: 5 weeks
My role: lead designer
Tools: Figma
In a preliminary survey, 8/10 young adults struggled with grocery shopping
It was time-consuming but also necessary
How might we…
How might we…
How might we…
make grocery shopping more time-efficient and organized?
make grocery shopping more time-efficient and organized?
make grocery shopping more time-efficient and organized?
I shadowed 7 shoppers in a grocery store and found lack of knowledge of stock and aisles were the main pain points
Even regulars had trouble finding things
Even regulars had trouble finding things
Even regulars had trouble finding things
Items can be moved, seasonal, or out of stock
Items can be moved, seasonal, or out of stock
Items can be moved, seasonal, or out of stock
Lack of route planning affects experience
Lack of route planning affects experience
Lack of route planning affects experience
Can be tedious if lugging a heavy basket
Can be tedious if lugging a heavy basket
Can be tedious if lugging a heavy basket
Unavailable items adds time to the shopping process
Unavailable items adds time to the shopping process
Unavailable items adds time to the shopping process
Frustrating and time-consuming to find a substitute
Frustrating and time-consuming to find a substitute
Frustrating and time-consuming to find a substitute
To solve these common pain points, shoppers needed help to
To solve these common pain points, shoppers needed help to
To solve these common pain points, shoppers needed help to
create a shopping list with real time stock information then find an optimal route
create a shopping list with real time stock information then find an optimal route
create a shopping list with real time stock information then find an optimal route
4 in-context usability tests informed a more accessible and versatile design
4 in-context usability tests informed a more accessible and versatile design
4 in-context usability tests informed a more accessible and versatile design
The final designs tackled key pain points
Arrive at the grocery store with a plan
Arrive at the grocery store with a plan
Arrive at the grocery store with a plan
Create a shopping list of things based on up-to-date stock information
Create a shopping list of things based on up-to-date stock information
Create a shopping list of things based on up-to-date stock information
Move through the store efficiently
Move through the store efficiently
Move through the store efficiently
Follow a route optimized to keep groceries fresh (icecream will not be melting as you shop)
Follow a route optimized to keep groceries fresh (icecream will not be melting as you shop)
Follow a route optimized to keep groceries fresh (icecream will not be melting as you shop)
Users' positive experiences translated into positive business impact
45% increase in online sales
34% increase in total sales
meaning the website made new sales possible as opposed to cannibalizing on pop-up sales.
Reflection
Reflection
I found conducting user interviews in-context was particularly helpful as it brought insights into what features were absolutely necessary and which were nice-to-haves. For example, I originally wanted users to be able to add new grocery items from the shopping screen. Observing shoppers in-context showed me that they had little need for it.
Identifying necessary vs. nice-to-have features is especially important in future projects if timelines are tight. It can allow for faster iterations which produces a product better fit for the user in a limited time frame.
I found conducting user interviews in-context was particularly helpful as it brought insights into what features were absolutely necessary and which were nice-to-haves. For example, I originally wanted users to be able to add new grocery items from the shopping screen. Observing shoppers in-context showed me that they had little need for it.
Identifying necessary vs. nice-to-have features is especially important in future projects if timelines are tight. It can allow for faster iterations which produces a product better fit for the user in a limited time frame.