PitchIn
Case Study
Website and app for volunteering
Research | Users | Wireframes | Usability Test | High-Fidelity Prototype | Design System | Next Steps | Lessons Learned
Meal planning can often be a source of stress and conflict in many households. It is time-consuming to sort through recipes and leaves uncertainty as to whether or not the meal will satisfy each person’s tastes and preferences. How can we relieve this stress and save time on meal planning?
Create an app that streamlines the process of planning weekly meals and compiling a grocery list. This app should reduce the timeframe and stress it takes to create a weekly meal plan by allowing users to rate meals and create a meal plan based on meals that were approved by all participating parties.
Before even thinking about design, I wanted to get a feeling for what products were already out there. I analyzed 5 apps and websites that assist with meal planning and found this:
With some initial information gathered, I was ready to start getting to know my users and learn about their experiences.
I began by talking to people who make meals for their family at least 4 times a week.
I asked about their schedules, eating habits, typical dinners, and challenges they face
when planning meals.
Based on the research and empathy exercises, I created my wireframes. My research showed me that the design should include solutions that save the user time, easily allow users to share and compare recipes with loved ones, and should include a way to quickly compile grocery lists. View wireframes in-depth.
Using my low-fidelity prototype, my usability study consisted of 5 participants who cook on average 4 nights a week and often makes dinners for multiple people (spouse, children, roommates, etc.). I asked them each to complete the following:
After organzing and grouping the feedback, it was clear that these areas needed improvement: the matching process, overall navigation, results page, potluck lists processes, and overall wording.
After organzing and grouping the feedback into an affinity diagram, it was clear that three of the main processes needed some improvement:
matching process
overall navigation
results page
potluck lists processes
overall wording
Based on patterns identified through the affinity diagram, some key elements were incorporated into the design:
Users need a more streamlined or reimagined process for voting and picking out meals
Improvements:
Users need buttons to be updated to include larger sizing, additional spacing, and clear communication
Improvements:
Users need wording to be more descriptive and clear to find their results easily
Improvements:
Users need the setup for potluck lists to be simplified and potentially pull in information from their account to reduce repetition
Some users need clearer language and more direction on how to proceed through creation process
Improvements:
Most users need the navigation to be simplified and easier to follow
Improvements:
For some users, these two functions need to be consolidated or offer more variety to justify two separate pages
Improvements:
Track the following KPIs to identify success and areas for improvement:
Use this data to identify data-driven areas for improvement
Partner with grocery stores to allow participants to order their grocery list for pickup or delivery
The idea for this case study was an exciting one for me, but I got a little too enthusiastic about the idea. This led to adding too many features from the get-go creating a design that was choppy and difficult to follow.
Start small and make sure the key features are well designed before trying to add more. Without a strong foundation, the app won’t be able to grow.
When designing this app, I thought it would be very easy to follow as it is inspired by popular dating apps that millions of people use. However, that was not the case and the feedback I got during my usability test consisted mainly of confusion.
Just because a process is simple to follow with one topic, that does not mean it will translate well and work well with other topics. Each process must be customized and fitted for the specific topic, product, or service.
After this usability study, I truly understood how differently wording can be interpreted by different people. Not just based on education level, but based on context and past experiences.
Testing your wording is just as important as testing the design. Without clear instruction, your design cannot always be interpreted as you want it to. UX writing is such a vital part of UX design.