Designing an MVP that works for users (2 and 1/2 hours) @Lean UX NYC 2013

6,948 views

Published on

2 and 1/2 hour workshop that covers contextual inquiry, empathy map, user experience map, MVP, elevator pitch, flow diagrams, stories, paper prototype and guerrilla usability testing.

Published in: Technology, Education

Designing an MVP that works for users (2 and 1/2 hours) @Lean UX NYC 2013

  1. 1. Designing an MVP that works foryour usersAriadna Font LlitjósUX Lead & Development ManagerIBM, Big Data@quicola #LeanUXNYC #LeanUX ariadna.font.cat
  2. 2. Write your expectations for this session on a stickyAriadna Font Llitjós @quicola
  3. 3. The Plan 20 min Theory Brief Description of UX techniques User Research, Scoping, Prototyping and Testing Practice 2 hours Focus on delivering an MVP fast with user-driven design Collaborative design session - Build a Mobile App! Ariadna Font Llitjós @quicola
  4. 4. Where are you? Product dev No product dev UX No UXAriadna Font Llitjós @quicola
  5. 5. Contextual inquiry Collaborative design Inception deck Sketches Paper prototype (CI) sessions Usability Testing (most of this MVP Flow diagram Personas workshop) Qualitative Elevator pitch Wireframes Usability Testing Empathy map Brainstorming 3 Must have goals Paper prototype Quantitative Stakeholder map Storyboard Usability Testing Flow diagram Mockups User Experience Sketchboard Pair testing map Stories Functional prototype Controlled Journey map Story map experiments (A/B Testing)Heuristic evaluation “Agile schedule” Heuristic Cognitive BDD evaluation walkthrough Cognitive Benchmarking walkthrough
  6. 6. Ariadna Font Llitjós @quicola
  7. 7. Contextual Inquiry (User Research)First hand observation of how people perform and structure theirwork (or any other relevant tasks)Who does it? UX person or other team member. A pair ofobservers is idealKey benefits:•  Best way to understand your users•  Only way to know what the real work flow/process is (vs the official one)•  Opportunity to discuss with users what they are doing and why Ariadna Font Llitjós @quicola
  8. 8. (Lean) Personas Characterization of a type of user that we want to target with ourproduct/applicationWho does it? Ideally, UX or somebody who has done some userresearch.Key Benefits:•  Document user research •  Remind team of users needs and motivations (different from managers and buyers) •  Allow team to ground communication throughout development Ariadna Font Llitjós @quicola
  9. 9. Empathy MapExplore a target user (persona) from different perspectives: Who am I? Behavior, See –Motivations, Do – Features, Say, Feel Who does it? The TeamKey Benefits: •  Very quick way to have a holistic view of your target user•  Forces you to think about more than their role•  Allow team to ground communication throughout developmentAriadna Font Llitjós @quicola
  10. 10. User experience mapVisual representation of the user workflow for accomplishing agoal. Key elements include: •  Questions to signal areas where more information/understanding is needed •  Comments with known information that clarifies / lends meaning •  Ideas to illustrate an interesting concept that could enhance a stepWho does it? The teamKey Benefits:•  Make team’s (lack of) knowledge explicit •  Good to figure out areas that need (further) user research Ariadna Font Llitjós @quicola
  11. 11. Ariadna Font Llitjós @quicola
  12. 12. Rules for brainstormingDefer judgment. Encourage wild ideas. Build on the ideas of others. Stay focused on the topic. Be visual. One conversation at a time. Go for quantity.Ariadna Font Llitjós @quicola
  13. 13. Storyboard Use of story telling to quickly visualize/share a solution to specificproblem making use of personas and their behaviors, stories andany known constraints.Who does it? The TeamKey Benefits:•  Help us think about the problem in a creative way•  Facilitates focused communication •  Affordable and easy to do Ariadna Font Llitjós @quicola
  14. 14. SketchboardIt’s like story boarding but with sketches, almost like a biomap ofthe system you are building or about to build.Who does it? Team with UX/designer’s helpKey Benefits:•  Provides Big Picture using initial design ideas•  Very iterative and highly collaboratively•  Very focused requirement discussions Ariadna Font Llitjós @quicola
  15. 15. Ariadna Font Llitjós @quicola
  16. 16. Minimal Viable Product - MVP•  (First) product version to test our ideas as quickly and cheaply as possible.•  An MVP has just those features that allow the product to be deployed and validated, and no more.•  "The minimum viable product is that version of a new product (or feature) which allows a team to collect the maximum amount of validated learning about customers with the least effort.”•  Is not a minimal product, it’s a strategy and process directed towards making and selling a product to customers.•  The MVP works together with a build-measure-learn cycle: developing software, gathering customer feedback, and learning from it.Ariadna Font Llitjós @quicola
  17. 17. Elevator Pitch For [target user] !who [statement of need or opportunity] !the [product/app name] is a [product category] !that [key benefit, compelling reason to buy/use]. !Unlike [primary competitive alternative] !our product/app [statement of primary differentiation]!Who does it? The Team Key Benefits:•  Allows team to focus on differentiator feature(s) and direct their energy to features with the highest business value•  Quick and inexpensiveAriadna Font Llitjós @quicola
  18. 18. 3 Must have goals1.  …2.  …3.  …Anything else goes in the Nice-to-have category.Good to have a “Will not do/have” category as well.Ariadna Font Llitjós @quicola
  19. 19. User stories Software system requirement formulated in one or two sentencesin everyday or business language that makes explicit the user’sneed. Example: As a [type of user] ! I want to [perform some task] ! so that I can [reach some goal]! Who does this? The team (dev, tester, doc or UX)Key Benefits: •  Provides a thinking template; token for a conversation •  Description of why the product needs to do what it doesAriadna Font Llitjós @quicola
  20. 20. User stories Software system requirement formulated in one or two sentencesin everyday or business language that makes explicit the user’sneed. Example: As a [type of user] ! I want to [perform some task] ! so that I can [reach some goal]! Who does this? The team (dev, tester, doc or UX)Key Benefits: •  Provides a thinking template; token for a conversation •  Description of why the product needs to do what it doesAriadna Font Llitjós @quicola
  21. 21. Ariadna Font Llitjós @quicola
  22. 22. Ariadna Font Llitjós @quicola
  23. 23. Flow diagram Visualize the workflow the user has to follow through theapplication to complete a task or achieve a goal. Can I use it? Who does it? The Team Key Benefits:•  Quick way to run through the system from a user perspective •  Allows you to identify gaps in your current flow•  Affordable and easy to do Ariadna Font Llitjós @quicola
  24. 24. Wireframes Grayscale mockups showing layout and position of page elements(can range from low-fidelity to exact grid-based resolution)Who does this? Typically UX, designer, but anyone can do it!Key Benefits:•  Easiest/cheapest way to realize and test ideas•  Great to get early feedback•  Can be done at any stage of developmentAriadna Font Llitjós @quicola
  25. 25. Paper PrototypeAriadna Font Llitjós @quicola
  26. 26. Ariadna Font Llitjós @quicola
  27. 27. Paper prototype usability testingUsability testing on paper versions of wireframes or sketches thatusers can simulate slicks and talk through their thoughts anddecisionsWho does it? Anyone can do this (be an observer) Key Benefits:•  Fastest and cheapest way to validate ideas/assumptions•  Results can be fed back into the design process immediately •  You can do this at any time you are not sure what is the best UI for a specific problemAriadna Font Llitjós @quicola
  28. 28. Usability Testing Facilitation 101•  Give user a specific task. Example: from the homepage, navigate to the Inspiration Zone and see if there is anything there that you’d like to buy; pretend there is, buy it.•  Use the think-out-loud protocol•  Stay neutral, non-judgmental. The user is never wrong. We re testing the product, not you •  Just observe, after stating the task, don’t tell them what to do or how to do it.•  Create questions that don t bias the responses you hope to get. •  Biased Q: Was it easy for you to sign up for the product •  Unbiased Q: Overall please rate how difficult or easy it was to sign up for this product 1 is difficult, 7 is easy.Ariadna Font Llitjós @quicola
  29. 29. To learn more about how to run your own UT… Read this book Ariadna Font Llitjós @quicola
  30. 30. Let s Practice!Collaborative Design SessionAriadna Font Llitjós @quicola
  31. 31. 5 minForm teams of 4-6 peopleIntroduce yourself (role, something unusual)You will collaboratively work on: 1.  User Research and Analysis 2.  Scoping 3.  Prototyping 4.  Usability Testing Ariadna Font Llitjós @quicola
  32. 32. Challenge Develop a Mobile App that helps promote networking and interaction between all conference attendeesAriadna Font Llitjós @quicola
  33. 33. Ariadna Font Llitjós @quicola
  34. 34. 15 minContextual Inquiry • Find a user and try to understand what they would want to do with this app (examples: check schedule, see how is in what session, chat with a speaker, rendezvous with random conference attendee, etc.) • Have they used such an app before? What did they like/hate about it? Try to get them to show it to you. • Observe and take notesAriadna Font Llitjós @quicola
  35. 35. 15 minEmpathy MapExplore multiple dimensions of your target users. Do as a brainstorming exercise. ThinksOne idea per sticky. Hears SeesQuestions: Feels Says Who are your users? Does What do they need/want? Pains GainsAriadna Font Llitjós @quicola
  36. 36. Empathy Map ExamplesAriadna Font Llitjós @quicola
  37. 37. 30 minUser experience mapVisual representation of the user workflow for a taskUsing a user experience map, document: 1.  The steps your user persona follows, 2.  What you know? (comments) •  Time and frequency of use. •  Location and physical context. •  Interactions with people or systems. •  Terminology and standards. •  Technical capabilities and limitations. 3.  What don’t know about them (questions) Ariadna Font Llitjós @quicola
  38. 38. User Experience Map ExamplesAriadna Font Llitjós @quicola
  39. 39. UX Map - Covering up the Questions• Talk to domain experts• Interview more users• Watch users in their environment• …Ariadna Font Llitjós @quicola
  40. 40. Ariadna Font Llitjós @quicola
  41. 41. 10 minElevator PitchCreate an elevator pitch to define what should beyour MVP functionality.Question: What do users want to do with the app? What’s our business proposition and the value added? (MUST haves vs NICE to haves) Ariadna Font Llitjós @quicola
  42. 42. Elevator Pitch For [target user] who [statement of need or opportunity] the [product/app name] is a [product category] that [key benefit, compelling reason to buy/use]. Unlike [primary competitive alternative] our product/app [statement of primary differentiation] ! Ariadna Font Llitjós @quicola
  43. 43. Ariadna Font Llitjós @quicola
  44. 44. 20 minPaper prototypingNow, pick a technique and apply it to design yourkiller feature (differentiator).You can use a flow diagram or other paper artifactthat you can use to do UT with. Question: Can I use it?Ariadna Font Llitjós @quicola
  45. 45. Ariadna Font Llitjós @quicola
  46. 46. 10 minGuerrilla Usability TestingNow let s test your paper prototype!Question: Can somebody outside your team use it? •  Do they know what they can do? and how to do it? •  Are there any big usability issues that would prevent your MVP from being broadly adopted?Ariadna Font Llitjós @quicola
  47. 47. Usability Testing Facilitation 101•  Give user a specific task. Example: from the homepage, navigate to the Inspiration Zone and see if there is anything there that you’d like to buy; pretend there is, buy it.•  Use the think-out-loud protocol•  Stay neutral, non-judgmental. The user is never wrong. We re testing the product, not you •  Just observe, after stating the task, don’t tell them what to do or how to do it.•  Create questions that don t bias the responses you hope to get. •  Biased Q: Was it easy for you to sign up for the product •  Unbiased Q: Overall please rate how difficult or easy it was to sign up for this product 1 is difficult, 7 is easy.Ariadna Font Llitjós @quicola
  48. 48. How did that go?What happened?Teams Could your user finish the task you had designed?Users Could you use the prototype? Would you buy it? Did the team do a good job at facilitating?Ariadna Font Llitjós @quicola
  49. 49. Ariadna Font Llitjós @quicola
  50. 50. Did we achieve the session’s goals?Ariadna Font Llitjós @quicola
  51. 51. Did we achieve the session’s goals?Did it meet your expectations?Ariadna Font Llitjós @quicola
  52. 52. + & −+ What was your favorite part of the session? Did you have any a-ha moments? Will you be able to take something you learned in this session back to your work/life? (if so, what?) − What was your least favorite part? What could be improved? Would make it for a better learning experience for you? Ariadna Font Llitjós @quicola
  53. 53. QUESTIONS?Ariadna Font Llitjós @quicola
  54. 54. THANKS!Ariadna Font Llitjós @quicola #LeanUXNYC ariadna.font.cat

×