Marty cagan built to learn - ux


Published on

IxDA Hamburg event - Marty Cagan on "How to Create Products Customers Love"
May 2011

Published in: Design

Marty cagan built to learn - ux

  1. 1. 5/31/11   Built To Learn The Case For UX Marty Cagan, PartnerAbout Me The Silicon Valley Product Group was created to share senior level experience and best practices with technology companies | 2 1  
  2. 2. 5/31/11  My Clients | 3Topics•  What I Tell The CEO: The Case For UX•  What I Tell Product Managers: Why You Need UX•  What I Tell UX Teams: Creating Great Products | 4 2  
  3. 3. 5/31/11  The Case For UX“Our Job is to Invent on Behalf of the User” Jeff Bezos | 5Product DiscoveryThe job of product discovery is to discover the minimumviable product that solves the customer’s problem | 6 3  
  4. 4. 5/31/11  Product Discovery TeamProduct discovery is a collaboration: – Product Owner – User Experience Design – Development | 7The Case For UX“Design is not just what it looks like and feels like; Design is how it works.” Steve Jobs | 8 4  
  5. 5. 5/31/11  The Case For UXEngineering is important anddifficult, but user experience design is even moreimportant, and usually more difficult | 9The Case For UX “Think in Leaps; Iterate in Steps” Chris Wetherell | 10 5  
  6. 6. 5/31/11  The Case For UX “The Company Cares About What the Leaders Care About” Bill Campbell | 11User Experience Design•  Interaction Designers: –  Interaction Models: Information Architecture, Tasks, Wireframes•  Visual Designers: –  Emotional Response: Look & Feel, Comps•  Content: –  Emotional Response: Voice, Copy•  User Researchers: –  Qualitative: User Prototypes, User Testing –  Quantitative: Live-Data Prototypes, A/B Testing, Web Analytics | 12 6  
  7. 7. 5/31/11  The Power of Interaction DesignThe Mental Model-  Products that “just work”-  Products where the value is clear and accessible-  No training or online-help required | 13The Power of Visual DesignThe Emotional Response•  Assuage fear•  Build trust•  Convince people to provide personal information they otherwise would not•  Motivate users to reach out to their friends•  Persuade users to buy merchandise they wouldn’t otherwise•  Make them actually enjoy their time on your site•  Love a product they would otherwise just like | 14 7  
  8. 8. 5/31/11  The Case For UX Fail Fast Make product discovery the core competency of the product organization | 15Product Discovery Overview –  Identify product discovery team (PM, UX, ENG) –  Utilize ideation techniques as needed (vision, product principles, personas, customer discovery) –  Quickly prototype ideas (user or live-data prototype) –  Validate prototype with customers (less than 2 weeks!) –  Review feasibility (and ideas) with engineering –  Demo and discuss prototype with stakeholders –  Iterate or pivot –  Continue until minimal viable product discovered, or you decide it’s best to give up | 16 8  
  9. 9. 5/31/11   High-Fidelity Prototypes Product Discovery | 17The Case For UX “Don’t Fall In Love” “Mockups Lie” | 18 9  
  10. 10. 5/31/11  High-Fidelity PrototypesTwo Forms:1.  User Prototypes (Simulation)2.  Live-Data Prototypes (Real Code) | 19User PrototypesBenefits:•  Quick to create and easy to modify•  Doesn’t require development resourcesLimitations:•  Qualitative testing only•  If tests successful, must still be built | 20 10  
  11. 11. 5/31/11  Live-Data PrototypesBenefits:•  Statistically significant results•  Quick to deploy if performs well in A/B test•  Can also test via user testingLimitations:•  Requires development resources•  Time to build may be significant | 21User Prototypes vs. Live Data Prototypes•  With User Testing we learn why things don’t work and what we can do to fix them•  With Live Data Testing we can prove that something actually works | 22 11  
  12. 12. 5/31/11  High-Fidelity Prototypes1.  Enables you to quickly test ideas on target users2.  Forces you to think through product at a much deeper level3.  Provides the mechanism for collaboration between product owner, design and engineering4.  Allows a more accurate cost estimate5.  Provides engineering and QA with a richer product definition to work from6.  Enables the rest of the organization to understand the product in time to actually prepare7.  Forces you to consider form and function together8.  Allows you to “fail fast”9.  Significantly reduces churn10.  Keeps the team focused on the user experience | 23 User Testing Product Discovery | 24 12  
  13. 13. 5/31/11  User TestingThe Two Key Questions:1.  Could they use it?2.  Would they use it? If not, what would it take to get them to use it? | 25Pivots•  Change target customer•  Change problem to be solved•  Change solution approach•  Change business model | 26 13  
  14. 14. 5/31/11  Product Manager Required•  Always ensure Product Manager is present•  Product Manager observes during usability test but drives during value test | 27 Key Points For UX User Experience Design | 28 14  
  15. 15. 5/31/11   Key Points For UX •  Know Your Audience •  Be Sensitive To Change •  It’s About Customer Learning •  Time To Step Up •  Role Confusion •  Titles | 29Top 10 Product Innovation Issues 1.  Weak Product Management Function 2.  Weak User Experience Function 3.  Little Direct Customer Interaction 4.  No Product Discovery Process 5.  Stakeholder Driven Roadmap 6.  Not Utilizing Engineering Early Enough 7.  Lack of Holistic View / Whole Product Focus 8.  Focus on Dates & Features not Business Results 9.  Missing Rapid Test and Learn Product Culture 10.  Missing Product Discovery Team Collaboration | 30 15  
  16. 16. 5/31/11  Learning More | 31 16