lean ux

43
LEAN UX Ryan Winzenburg 1 Tuesday, April 9, 13

Upload: ryan-winzenburg

Post on 27-Jan-2015

1.054 views

Category:

Business


2 download

DESCRIPTION

Presentation of Jeff Gothelf's book "Lean UX" to internal Global UX and Strategic Insights Group

TRANSCRIPT

Page 1: Lean UX

LEAN UXRyan Winzenburg

1Tuesday, April 9, 13

Page 2: Lean UX

LEAN UX

Vision

Design

MVPs

Research

2Tuesday, April 9, 13

Page 3: Lean UX

VISION

• Assumptions

• Hypothesis

•Outcomes

• Features

3Tuesday, April 9, 13

Page 4: Lean UX

PREPARATION

•Divergent Process

• Research

• Analytics

• Usability Report

• Past Success/Failures

• Stakeholder Input

• Competitive Analysis

4Tuesday, April 9, 13

Page 5: Lean UX

5Tuesday, April 9, 13

Page 6: Lean UX

6Tuesday, April 9, 13

Page 7: Lean UX

7Tuesday, April 9, 13

Page 8: Lean UX

BUSINESS ASSUMPTIONS

• I believe my customers have a need to _______ .• These needs can be solved with _______ .• My initial customers are (or will be) _______ .• The #1 value a customer wants to get out of my service is

_______ .

• The customer can also get these additional benefits _______ .

• I will acquire the majority of my customers through _______ .

• I will make money by _______ .

• My primary competition in the market will be _______ .

• We will beat them due to _______ .

• My biggest product risk is _______ .

• We will solve this through _______ .

• What other assumptions do we have that, if proven false, will cause our business/project to fail? _______ .

8Tuesday, April 9, 13

Page 9: Lean UX

9Tuesday, April 9, 13

Page 10: Lean UX

10Tuesday, April 9, 13

Page 11: Lean UX

11Tuesday, April 9, 13

Page 12: Lean UX

USER ASSUMPTIONS

• Who is the user?

• Where does our product fit in his work or life?

• What problems does our product solve?

• When and how is our product used?

• What features are important?

• How should our product look and behave?

12Tuesday, April 9, 13

Page 13: Lean UX

13Tuesday, April 9, 13

Page 14: Lean UX

14Tuesday, April 9, 13

Page 15: Lean UX

OUTCOMES

• Statement

• We believe that [doing this/building this feature/creating this experience]

• for [these people/personas]

• will achieve [this outcome].

• We will know this is true when we see [this market feedback, quantitative measure, or qualitative insight].

15Tuesday, April 9, 13

Page 16: Lean UX

[OUR SERVICE/PRODUCT] WAS DESIGNED TO ACHIEVE [THESE GOALS].

WE HAVE OBSERVED THAT THE PRODUCT/SERVICE ISN’T MEETING [THESE GOALS], WHICH IS CAUSING [THIS ADVERSE EFFECT] TO OUR BUSINESS.

HOW MIGHT WE IMPROVE [SERVICE/PRODUCT] SO THAT OUR CUSTOMERS ARE MORE SUCCESSFUL BASED ON [THESE MEASURABLE CRITERIA]?

16Tuesday, April 9, 13

Page 17: Lean UX

FEATURES

• Tactics

• Features

• Products

• Service

17Tuesday, April 9, 13

Page 18: Lean UX

18Tuesday, April 9, 13

Page 19: Lean UX

FEATURE STORY

• Statement

• We will [ create this feature ]

• for [ this persona ]

• In order to achieve [this outcome ]

19Tuesday, April 9, 13

Page 20: Lean UX

COLLABORATIVE DESIGN

•Design Studios

• Style Guides

20Tuesday, April 9, 13

Page 21: Lean UX

DESIGN STUDIO

• Agenda• Problem Definition & Constraints

[15-45 mins]

• Individual Idea Generation (Divergent)[10 mins]

• Presentation and Critique [3 min/each]

• Iterate and Refine [5 - 10 min]

• Team Idea Generation (converge)

• [10 mins]

21Tuesday, April 9, 13

Page 22: Lean UX

STYLE GUIDE

• Pattern Library• Typographic

• Interactive

• Visual

•Maintenance

22Tuesday, April 9, 13

Page 23: Lean UX

23Tuesday, April 9, 13

Page 24: Lean UX

24Tuesday, April 9, 13

Page 25: Lean UX

MVP

• Focus

• Tools

• Prototypes

•Non-Prototype MVPs

25Tuesday, April 9, 13

Page 26: Lean UX

MVP FOCUS

• Increase Learning• Prioritize Ruthlessly• Stay Agile• Measure Behavior• Use a clear call to action

•Delivering Value• Be Functional• Integrate with existing analytics• Be consistent with rest of products

26Tuesday, April 9, 13

Page 27: Lean UX

TOOLS

• Sketching

• Prototyping

• Copy Writing

• Visual Design

27Tuesday, April 9, 13

Page 28: Lean UX

28Tuesday, April 9, 13

Page 29: Lean UX

29Tuesday, April 9, 13

Page 30: Lean UX

30Tuesday, April 9, 13

Page 31: Lean UX

31Tuesday, April 9, 13

Page 32: Lean UX

32Tuesday, April 9, 13

Page 33: Lean UX

PROTOTYPING

• What am I trying to learn?

• What are the main signals I need from the market to validate my hypothesis

• Are there other signals I can test for that will serve as indicators for my main signal

• What’s the fastest way for me to find this information?

33Tuesday, April 9, 13

Page 34: Lean UX

NON-PROTOTYPE MVP

• Email

• Google Ad Words

• Landing Pages

• Button to Nowhere

• Concierge Services

34Tuesday, April 9, 13

Page 35: Lean UX

FEEDBACK & RESEARCH

• Collaborative Research

• Continuous Research

• Artifacts/Results

•Methods

35Tuesday, April 9, 13

Page 36: Lean UX

COLLABORATIVE RESEARCH

• Researcher as Coach

• Review Interview Guide

•Who to speak to

• Interview

36Tuesday, April 9, 13

Page 37: Lean UX

INTERVIEW

•Questions

• Conversations

•Demonstrations

• Follow Up Questions

• Referrals

37Tuesday, April 9, 13

Page 38: Lean UX

CONTINUOUS RESEARCH

•M: Recruit and Plan

• T: Refine MVP

•W: Refine, Script, Finalize Recruiting

• Th: Test/Review

• F: Plan Next Steps

38Tuesday, April 9, 13

Page 39: Lean UX

ARTIFACTS/RESULTS

• Sketches

•Wireframes

•Mock-Ups

• Prototypes

• Coded Prototypes

39Tuesday, April 9, 13

Page 40: Lean UX

METHODS

•Diary Studies

• Card Sorting

• Unmoderated Testing

• Usability Tests

• Contextual Inquiry

• Customer Support

• Analytics

• User Forums

• Social Media

• Surveys

• Search Logs

• A/B Tests

40Tuesday, April 9, 13

Page 41: Lean UX

41Tuesday, April 9, 13

Page 42: Lean UX

42Tuesday, April 9, 13

Page 43: Lean UX

43Tuesday, April 9, 13