eecs 441 - mealjet mvp 1 - user testing

9
MVP 1 User Feedback Jashanjit Kaur, Kruthi Sabnis Krishna, Rahul Raina, Austin Feight, David Quesada

Upload: jashanjit-kaur

Post on 29-Jul-2015

97 views

Category:

Design


2 download

TRANSCRIPT

Page 1: EECS 441 - MealJet MVP 1 - User Testing

MVP 1 User Feedback !

!

Jashanjit Kaur, Kruthi Sabnis Krishna, Rahul Raina, Austin Feight, David Quesada

Page 2: EECS 441 - MealJet MVP 1 - User Testing

Problem

Target User: Driver who is delivering the food

Customer orders food

(Veg/Meat options)

Driver picks up meals Driver delivers

food using the app

Page 3: EECS 441 - MealJet MVP 1 - User Testing

Problem Current Process:

• Driver gets these orders as emails

• He switches between multiple applications such as his email client, calling application and Google Maps

• Driver has to figure out most efficient sequence of delivering orders by himself

• System fails when there are multiple drivers

Aim: Deliver orders efficiently and safely

Page 4: EECS 441 - MealJet MVP 1 - User Testing

Our Approach Task Scenarios (for Usability Issues)

• Discover problems faced by users

• Understand causes of the problems

Feature Testing (for User’s Attitudes)

• Importance Rating

• Satisfaction Rating

Page 5: EECS 441 - MealJet MVP 1 - User Testing

SummaryOverall Satisfaction: 3.4

Importance Satisfaction

Browsing orders 4.2 4.0 Navigating to the destination 4.4 3.2 Marking an order as complete 4.4 3.4 Canceling an order 4.1 3.4 Calling the customer 4.6 4.0 Update Inventory 3.6 3.4

FeaturesRatings (1-5)

Page 6: EECS 441 - MealJet MVP 1 - User Testing

What we confirmed

!

• Participants liked the concept

• Information provided for each order was sufficient

• Font size, iconography, color scheme was easy to locate in a moving vehicle

John Smith

Meat (2)

10 E William St

8 orders in queue

42%EECS441 3:00 PM

Page 7: EECS 441 - MealJet MVP 1 - User Testing

Surprises !

• Unclear UX

• Switching between maps and app wasn’t as easy as we thought

• “Go Online” flow was annoying

• Reluctant to update inventory

Page 8: EECS 441 - MealJet MVP 1 - User Testing

Next Steps !

• Refine the current interaction flow

• Introduce demo and prompts

• Provide embedded maps

• Inventory management without going offline

• Automating inventory updates

• Send texts along with calls

Page 9: EECS 441 - MealJet MVP 1 - User Testing

Thank You!Questions? Feedback?