PROJECT
PREPARE: A Recipe App
ROLE
Lead UX Designer, from conception to delivery
DURATION
2022, 6 Months
PROCESS DECK
LOW-FIDELITY PROTOTYPE
HIGH-FIDELITY PROTOTYPE
PREPARE:
A TRAINING SITE
PROJECT VISION
PREPARE: A Recipe App, was created specifically for the restaurant, bakery, café, and bar industries, to break accessibility barriers and to support the needs of line cooks, chefs, bakers, bartenders, new hires, etc., during their chaotic and busy shifts.
PROBLEMS
-
Busy schedule doesn't leave time to step away without falling behind.
-
Language barriers between front and back of house regarding how an item is made. Also, general recipe inconsistency.
-
Turnover from disorganization and poor training.
-
Recipe books are old, not updated, sticky/gross, hard to find, or non-existent.
RESEARCH CONDUCTED
For this project, qualitative research was key. I conducted interviews, competitive audits, a survey, empathetic storyboards, and eventually multiple usability studies to identify the needs of my target users, which are: line cooks, chefs, bakers, bartenders, new hires, etc. At the start of the project, I assumed I’d need to create an app where users can quickly find recipes but I learned so much more.
Research confirmed the idea of finding recipes quickly since users expressed having a limited amount of time to search for recipes. It also revealed hot and messy environments, word-of-mouth recipes being inconsistent, high turnover because poor training, and language barriers.
?
What are the user’s current problems that this app can solve?
?
What common behaviors, experiences, and scenarios my product is trying to address?
?
What is the emotional state of a chef or line cook during a busy and fast paced shift?
?
What are restaurants needs and frustrations?
?
What is a day in the life of a chef or line cook?
?
What is the most efficient and time saving way to search an app?
After conducting a usability study, I gathered key information to form actionable insights around the apps usefulness, navigation, usability, expectations, and more..
INSIGHTS
There needs to be clearer clues on what a user can select.
Another accessibility icon that is more intuitive would help users to understand where to change language.
Some users need more information on the value of certain features such as focus view and toggling images.
Provide better details to users on what page they’re on.
THE USERS
.png)
.png)
.png)
COMPETITIVE ANALYSIS
I've researched several competing companies. None were true direct competitors since the app I've created would be found in restaurants, bars, bakeries, cafés, and the like--not for at home personal use. But while conducting interviews, I came to learn that if a chef was not able to get clear recipe directions, one option would be to search online on platforms open to the public.
Gaps:
-
Too many features
-
Minimal or no accessibility options
-
Minimal language options or just english
-
-
Not much diversity
-
No ability to customize
Opportunities:
-
Allow users to customize homepage to fit their accessibility, dietary, and other personal needs
-
Have a search function with filtering options so users can find exactly what they want
-
Be clear and concise with directions/navigation
-
Take the least amount of clicks to get the information they want
THE JOURNEY
One user flow I created mapped the journey of a user searching for a "Seasonal Meal," as quickly as possible. "Seasonal Meal" is later referred to as "dish" and then "recipe" in the final design.
COMPETITIVE ANALYSIS
I've researched several competing companies. None were true direct competitors since the app I've created would be found in restaurants, bars, bakeries, cafés, and the like--not for at home personal use. But while conducting interviews, I came to learn that if a chef was not able to get clear recipe directions, one option would be to search online on platforms open to the public.
Gaps:
-
Too many features
-
Minimal or no accessibility options
-
Minimal language options or just english
-
-
Not much diversity
-
No ability to customize
Opportunities:
-
Allow users to customize homepage to fit their accessibility, dietary, and other personal needs
-
Have a search function with filtering options so users can find exactly what they want
-
Be clear and concise with directions/navigation
-
Take the least amount of clicks to get the information they want
THE JOURNEY
One user flow I created mapped the journey of a user searching for a "Seasonal Meal," as quickly as possible. "Seasonal Meal" is later referred to as "dish" and then "recipe" in the final design.
"PAPER" WIREFRAMES
To save paper, I used an illustration program to draw my paper wireframes. Brainstorming and creating in this way made it easier to visualize what my digital wireframes could potentially look like.
THE WIRE FLOW
The wire flow is based on the simple user journey created above. These visuals helped to determine what areas I needed to improve on and what was and wasn't needed. I dedicated a lot of time iterating on intuitive icons and easy navigation before remembering what generation phone screen I was designing for. From there, I need I had to tweak the layout to accommodate for the screen size.
ITERATION & USABILITY FINDINGS
The prototype was created with the idea that there'd be one interface all users would interact with and those in managerial positions can update and add recipes when necessary.
After creating a prototype based on my low-fidelity wireframes, I created a 17 question participant screener survey to gather a diverse range of users to test my prototype. Although the participants were baristas, former bartenders, sous chefs, restaurant owners, and those in between, they had common pain points and issues with the food and drink industry in general. Between the screener and the two rounds of moderated usability studies, all feedback gave me actionable insights.
THE "A" IS NOT OKAY
An "A" icon and a stick figure was used to represent the accessibility tab in early designs, but most users had to guess or use the process of elimination to determine what the icon was for.
THEY SAID, HE SAID, SHE SAID
Language barriers between front and back of house along with, biases, guesses, and a quick search of the internet has led to frequent recipe inconsistencies.
WASTE NO TIME
I wanted navigation to be quick and simple--to take the least amount of clicks to get to the information users need since in most cases, they don't have much time and can easily fall behind on orders.
IS IT THIS OR THAT?
Some users weren't sure what to select when asked to view a dish [recipe] in "focus view" from the listed category section.
PROBLEM #1: TURN OVER
There’s high turnover in this industry because of poor training due to lack of time and or care. Workers are not always confident in their task and are afraid to ask for help.
Gathering this insight allowed me to pivot in my design choices. Before, only managers could log in. Now, individuals can log in and pin recipes they need help with most.
PROBLEM #2: ACCESSIBILITY
In house recipe books are old, not updated, sticky/gross, hard to find, or non-existent and unless the establishment is diversely owned, are only in english. English is not the first language for a lot of cooks and chefs.
PROBLEM #3: TIME & WORK FLOW
In house recipe books are old, not updated, sticky/gross, hard to find, or non-existent and unless the establishment is diversely owned, are only in english. English is not the first language for a lot of cooks and chefs.
PROBLEM #4: INCONSISTENCY
If a recipe book is not updated, hard to find, or non-existent, cooks and chefs tend to search the internet or ask each other how something is made. Because of this, there is a greater chance for inconsistency.
Users now have a platform that allows them to pin recipes, be notified of updated recipes, and customers can confidently purchase the same dish twice, knowing it'll be the same as before.
STICKER SHEET
TAKEAWAYS
Although I've been designing for many years this was the first time I've ever created an app. I thoroughly enjoyed the process and was able to realize skills I have always had but never had the chance to use. When I set out to design a recipe app, I truly didn't know what I was getting into. I probably was hungry at the time I decided on this prompt.
What surprised me was my lack of patience. I was so eager to continue the project that waiting on participant responses to emails made me a bit antsy--especially because their feedback was the most important part of the process. I can't design with the user in mind without their input. But next time, I'll know what to expect and can plan accordingly.
This project helped me to dig deeper as a designer, define ideas and elements that I couldn't put names to before because I was self-taught, and most importantly help others. I wanted to created an app that would make people more confident in themselves which would have a positive domino effect throughout the industry. Designing with accessibility in mind felt like second nature to me because of my writing background with championing diverse stories and being a sensitivity reader for underrepresented characters that share the same culture and experiences as me.
