Low Fidelity Rapid Prototyping Using Marvel
For our first project in the General Assembly UX Design Immersive, we were presenting an interacting prototype that we created and tested. To do this, we had to utilize our newly-acquired user interview and rapid prototyping skills.
Timeframe
We had 4 days to complete our project.
Limitations, Parameters, Resources, and Materials
For sketching, we used pens/pencils, paper, and templates. We then used Marvel to create our interactive prototypes.
Assumptions When Entering Project:
- Very few people know everything they have in their kitchen
- Organized people would like an inventory
- Some people may find this unnecessary
Original Problem Statement:
When people are grocery shopping, sometimes it is difficult to remember what they do/don’t have at home.
How might we provide shoppers with an efficient way to keep track of their grocery needs?
User Interviews
I conducted 5 user interviews for this project using the following guide:
1)Do you consider yourself an organized person? How organized/what are examples?
2) How do you feel about lists and checklists?
3) How do you feel about grocery shopping?
4) Do you use a grocery list when you go shopping?
5) Do you make shopping lists at home or when you’re out and about?
6) Do you use your phone to make shopping lists or do you prefer paper?
7) Where do you get most of your recipes?
8) How often do you find that you don’t have an ingredient that you need for a recipe?
9) Do you feel that you have a good grasp of what’s currently in your pantry/fridge/spice rack?
10) Would creating an inventory of your kitchen be appealing to you? Why or why not?
11) If you live with roommates or family/S.O.’s how do you organize/delegate shopping lists?
12) What’s your least favorite thing about going grocery shopping?
13) Is there anything you can think of that would make your grocery shopping experience more enjoyable/easy?
After my first interview, I decided to change a few things. I removed question 12, because a) it had a negative connotation and b) it made question 13 (which I preferred) redundant. I also edited question 8 to include the possibility of buying duplicate items and over stocking.
Insights
Users are organized, but sometimes forgetful
Users enjoy grocery shopping because “food = fun”
Users like to plan in advance
If things don’t go to plan, users feel comfortable improvising
Users don’t have a good grasp of what is currently in their kitchen
User Quotes
“My roommate is ridiculously organized. Checklists are basically like Candy Crush for her.”
“I use recipes a lot so those tend to dictate my grocery lists.”
“We buy duplicates a lot. It’s so bad. Especially with produce, because some is bound to go bad and then we feel wasteful.”
“If I forget my list, it’s not the end of the world, but I do end up forgetting things or buying food I don’t need.”
Assessment
After conducting user interviews, I felt that my initial assumptions and problem statements were validated. Users responded positively to the notion of organized checklists and knowing what’s in their kitchen. Common pain points seemed to be centered around forgetting items when at the store or getting too much and not using it all. I decided to focus my problem statement on a more specific user — The Organizer.
Revised Problem Statement
How can we provide organized people with a more-efficient, less-wasteful way to grocery shop that ensures they have the items needed for their household and their meals?
Sketches
- Opening screen for “Got It”
- “Shopping List” feature- See what you need to get at the store!
- “Inventory”- Select a category and manage the contents of your kitchen.
- “Recipe” feature
- Press to “Search” the app for items in a quick and efficient manner
- Manage “Account” information
- “Return to Last Page” Button
- “Return to Home Page” Button
- Shopping List Screen- After clicking “Got It” (checkout), checked items will be added to the user’s inventory.
Usability Tests and Resulting Iterations
After creating the prototype, I began usability testing. The goal of the test was for the app to be intuitive in a way that, when faced with a scenario and task, users would be able to complete the task easily and without guidance. I tested 4 users using the following guide:
OPENING
Do you use any list-making apps, currently?
Do you write grocery shopping lists? If so, how do you go about doing this?
How often would you say you do this?
What platform do you use?
FIRST IMPRESSIONS
What are you seeing?
Is there anything that you notice, or that stands out to you?
SCENARIO/TASKS
SCENARIO #1
You’ve recently downloaded the app and now you want to take some time to start creating your kitchen inventory. Can you start creating the inventory for your spices?
TASK #1
Open the app and add items to your inventory. Let’s start by adding items to your spice inventory. Have the app guide you through the process. When you’re done, return to the home screen.SCENARIO #2
You’re super hungry, but you’re also in your favorite pair of PJs and leaving to go to the store does NOT sound appealing.
TASK #2
Use the app to find a recipe that only uses items you have in your kitchen.SCENARIO #3
You have 2 other roommates and the 3 of you have created a group on the app. You’re coming home from work and are going to stop by the store, but you can’t remember what you agreed to buy for the apartment.
TASK #3
Can you find your account information and then check your joint shopping list?FINAL THOUGHTS
Did you find this app useful?
How did this compare to your usual method of making shopping lists?
Is there anything you’d expect to be able to do that you couldn’t do?
During the first usability test, the user had difficulty completing the task of adding items to an inventory. I realized that a flow path that made perfect sense to me was not clear to the user! Instead of fixing the layout of the prototype, I observed the path the user was trying to create and then reiterated to match this path on Marvel. When I tested this on the other users, they followed the same path, only this time it worked! The other users were able to complete all 3 tasks.
There is a feature on the app that presents users with 3 ways to add items to the inventory. Users can 1) Use their camera to scan the barcode of an item to be automatically added to the inventory (not an interactive option for test users), 2) A guided list where users can press “yes/no” buttons based on if they have an item, 3) A manual entry options where users can type in the spice they’re adding. When I tested users from different platforms, iOS users typically preferred the manual entry over the buttons because the buttons were “time-consuming” and involved lots of screens. However, Android users preferred the guided option over typing because they claimed an Android keyboard can be difficult and annoying to use.
I was also very surprised at the positive response I received for a feature that was added on a whim! It was a “recipe generator” feature that, if selected, would find a recipe you could cook using only ingredients that you currently have in your kitchen. You wouldn’t have to put on pants and go to the store!
Prototype
“It’s like a pantry in your pants.”
— User During Testing
Reflection
Given that this was my first project within UX, it was extremely informative and quite the ride. I felt comfortable conducting user interviews and testing, but want to develop my synthesis and affinity mapping skills more. I believe that I produced a product that focused on meeting user’s needs by utilizing their feedback and suggestions. During usability testing, I would sometimes be surprised by their interpretations of my design. It’s interesting to see how something that seems obvious to you is completely lost on another person. It’s a good reminder to step away from the process sometimes and get fresh eyes and opinions on the product.
If I could do something differently, I would maybe take my app through a few different reiterations. My initial templates didn’t change very much after I began usability testing, and I believe that there is always something that can be changed and improved upon. This is something that I may grow from once we begin doing multiple rounds of testing, so I can really take those breaks between tests to revamp my designs. That being said, I really enjoyed creating the prototype. Figuring out the flow of the app was like working on a multi-dimensional puzzle. Good times!
