Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

What's for Lunch! presentation

13 views

Published on

Presentation of the UX Design process and development of the What's for Lunch! app

Published in: Design
  • Be the first to comment

  • Be the first to like this

What's for Lunch! presentation

  1. 1. WHAT’S FOR LUNCH! UX JOURNEY TEAM Nanosoft MEMBERS Randy Medders Pamela Funk Mirza Zaman
  2. 2. Houston… We have a problem! • Our work-lives have been spent in offices • Work schedules are too demanding • Back-to-back meetings most days • Lunch is our only break • Better make it count!
  3. 3. Can we fix it? Yes… we… can! A BETTER LUNCH EXPERIENCE • QUICK way to choose a place to eat… Let the app do it… randomly! • Share that place with my friends & vote… In real time • Communicate with my friends while voting • Need extras like ratings, reviews, maps & coupons to help us decide
  4. 4. We will breakdown these phases in the following sections. OUR UX PROCESS RESEARCH DESIGN TESTING PHASE 1 PHASE 2 PHASE 3 GATHER FACTS & OPINIONS SKETCH, IDEATE & PROTOTYPE USER TESTING & ANALYSIS
  5. 5. RESEARCH GATHER FACTS & OPINIONS
  6. 6. 1. COMPETITOR ANALYSIS identify gaps in competitor functionality 2. USER INTERVIEWS do potential users like your proposal 3. PERSONAS target the typical user GATHER FACTS & OPINIONS USER RESEARCH: Process RESEARCH
  7. 7. USER RESEARCH: Competitor Analysis OpenTable 1. Find eatery & book res. 2. Pics, menus, reviews 3. Reward program 4. No Random Selection 5. No Viral Component Yelp 1. Find eatery & much more 2. Pics, menus, reviews 3. No Random Selection 4. No Viral Component SpotLuck 1. Find eatery randomly 2. Pics, menus, reviews 3. No Viral Component
  8. 8. USER RESEARCH: User Interviews 1. Secured a test group of people that work in an office: 6 in total 2. We offered them an incentive to be interviewed. a drink after work 3. Each interview was conducted one at a time... and in private 4. Age range & diversity: 25-49, 3 men & 3 women, multiple cultures represented
  9. 9. USER RESEARCH: User Interviews & Results 1. Do you like to go to lunch with your friends at work? Mostly “Yes” 2. Do you have trouble deciding where to go to lunch with our group? Mostly “Yes” 3. Do you find that you wind up going to the same places? Just over half “Yes”. Others “Sometimes”. 4. Would you like an app that makes choosing a place for lunch fun and quick? Mostly “Yes” 5. Circle the features you would find useful in this app and add any we are missing. Eatery selection, Voting on a place to eat, Seeing a friend’s vote, Chat/text session during voting, Reviews, Coupons, Maps, Ratings
  10. 10. Personas
  11. 11. The What’s For Lunch? App For the busy person with barely enough time to eat during the day, What’s For Lunch is a restaurant selection app that starts the selection process for you and let’s you share the experience with your friends in real time unlike OpenTable, Yelp, and SpotLuck. Unique Features: • Fun, engaging game to find your eatery • Sharing the experience with your friends • Random selection of a restaurant
  12. 12. DESIGN SKETCH, IDEATE & PROTOTYPE
  13. 13. DESIGN: Process SKETCH, IDEATE & PROTOTYPE WORKFLOWS SKETCHES PROTOTYPEUSER STORIES
  14. 14. DESIGN: Epics and User Stories
  15. 15. DESIGN: Workflows USER TYPES • First Time User • Game Organizer • Game Player (Invitee) PROCESS • On Boarding • Profile Update • Game Play • Reviews • Ratings • Coupons • Search Settings
  16. 16. DESIGN: Workflows Example
  17. 17. DESIGN: Workflows//First Time User
  18. 18. DESIGN: Workflows//Game Organizer
  19. 19. DESIGN: Workflows//Game Player (Invitee)
  20. 20. DESIGN: Screen Design
  21. 21. DESIGN: Screen Design
  22. 22. DESIGN: Prototype
  23. 23. TESTING USER TESTING & ANALYSIS
  24. 24. TESTING PROTOTYPE Initial Impressions Affordances & Expectations Task Scenarios SUS Test System Usability Scale
  25. 25. TESTING PROTOTYPE Initial Impressions Affordances & Expectations Task Scenarios SUS Test System Usability Scale INITIAL IMPRESSIONS
  26. 26. TESTING PROTOTYPE Initial Impressions Affordances & Expectations Task Scenarios SUS Test System Usability Scale
  27. 27. TESTING PROTOTYPE Initial Impressions Affordances & Expectations Task Scenarios SUS Test System Usability Scale
  28. 28. Struggling with Buttons FINDINGS: Game Screen 1. Buttons and CTA on screen look out of order. I’m confused on what to do first. 2. CTA is hard to read and not scannable. It is two different commands but hard to tell at a glance. RECOMMENDATIONS 1. Move buttons under CTA. 2. Split up CTA better to make it more scannable.
  29. 29. Struggling with Content Hierarchy FINDINGS: Vote Screen 1. Users didn’t understand what the Lunch Group section was and what info it communicated. 2. Coupon and Menu buttons are important but we have to scroll too far to get to them. RECOMMENDATIONS 1. Make the items in the Lunch Group section larger. 2. Move the Coupon and Menu buttons above content of lesser importance.
  30. 30. TESTING PROTOTYPE Initial Impressions Affordances & Expectations Task Scenarios SUS Test System Usability Scale
  31. 31. TESTING PROTOTYPE Initial Impressions Affordances & Expectations Task Scenarios SUS Test System Usability Scale = WFL App What’s For Lunch! scored an average of 87 (86.8) based on results from our six usability test participants
  32. 32. DESIGN UPDATED PROTOTYPE
  33. 33. Before & After CHANGES TO PROTOTYPE 1. Move buttons under CTA and closer to the user’s thumbs when holding phone with one hand. 2. Split up CTA better by using rule lines and using different sizes of text the build hierarchy.
  34. 34. Before & After CHANGES TO PROTOTYPE 1. Make the items in the Lunch Group section larger. Make section scroll horizontally as not to push other content further down the page. 2. Move the Coupon and Menu buttons above content of lesser importance showing in the first screen view.
  35. 35. NEXT STEPS
  36. 36. Next Steps 1. Need to perform additional usability testing to ensure the proposed changes will work. 2. Expand our user stories with the Development team and Product Manager. 3. Schedule a workshop with the Product Manager for additional features, such as a Reward Program. 4. Develop a richer set of personas to take advantage of additional opportunities.
  37. 37. QUESTIONS? AND THAT’S…

×