This document contains slides from a presentation by Josh Seiden on Lean UX. Some key points from the presentation include: - Lean UX is a principle-driven process for product teams to work under conditions of uncertainty characterized by rituals that produce high-quality outcomes. - Key Lean UX principles include having cross-functional product teams, externalizing work, being goal-driven, and validating hypotheses with user research. - Important Lean UX methods include getting team incentives right by focusing on problems rather than deliverables, identifying assumptions, expressing hypotheses, and conducting experiments through minimum viable products.

1. LeanUX for NYCCHI
NYC-CHI Panel
April 11, 2012
Josh Seiden
@jseiden
Thursday, April 12, 12

2. Me and my hashtags
www.proof-nyc.com
josh@proof-nyc.com
@proof_nyc
#leanUX Josh Seiden
#leanStartup @jseiden
www.proof-nyc.com License: Creative Commons Attribution-
www.slideshare.net/jseiden
2 Share Alike 3.0 United States
Thursday, April 12, 12

3. HOW DID WE GET HERE?
www.proof-nyc.com License: CC BY-NC-SA
www.slideshare.net/jseiden United States
Thursday, April 12, 12

4. Old assumptions, new reality
www.proof-nyc.com License: CC BY-NC-SA
4
www.slideshare.net/jseiden United States
Thursday, April 12, 12

5. Old assumptions, new reality
www.proof-nyc.com License: CC BY-NC-SA
4
www.slideshare.net/jseiden United States
Thursday, April 12, 12

6. Old assumptions, new reality
www.proof-nyc.com License: CC BY-NC-SA
4
www.slideshare.net/jseiden United States
Thursday, April 12, 12

7. Old assumptions, new reality
www.proof-nyc.com License: CC BY-NC-SA
4
www.slideshare.net/jseiden United States
Thursday, April 12, 12

8. Old vs new: handoffs vs. collaboration
www.proof-nyc.com License: CC BY-NC-SA
5
www.slideshare.net/jseiden United States
Thursday, April 12, 12

9. Old vs new: handoffs vs. collaboration
www.proof-nyc.com License: CC BY-NC-SA
5
www.slideshare.net/jseiden United States
Thursday, April 12, 12

10. Responding to change and collaboration
www.proof-nyc.com License: CC BY-NC-SA
6
www.slideshare.net/jseiden United States
Thursday, April 12, 12

11. Responding to change and collaboration
• Agile Software Development
www.proof-nyc.com License: CC BY-NC-SA
6
www.slideshare.net/jseiden United States
Thursday, April 12, 12

12. Responding to change and collaboration
• Agile Software Development
• Design Thinking
www.proof-nyc.com License: CC BY-NC-SA
6
www.slideshare.net/jseiden United States
Thursday, April 12, 12

13. Responding to change and collaboration
• Agile Software Development
• Design Thinking
• Lean Startup and Customer Development
www.proof-nyc.com License: CC BY-NC-SA
6
www.slideshare.net/jseiden United States
Thursday, April 12, 12

14. HOW CAN DESIGNERS RESPOND?
www.proof-nyc.com License: CC BY-NC-SA
www.slideshare.net/jseiden United States
Thursday, April 12, 12

15. Lean UX is a response
“Lean User Experience is principle-driven
process for teams working in situations of
extreme uncertainty. It is characterized by
rituals that predispose predictable, high-quality,
high-velocity user experience outcomes.”
– Janice Fraser, LUXr.co
www.proof-nyc.com License: CC BY-NC-SA
@jseiden
Thursday, April 12, 12

16. LUXr’s Lean UX Principles
Who? 1. Design + biz + development + ... = 1 product team.
2. Externalize!
How do we work 3. Goal-driven and outcome-focused.
together?
4. Repeatable and routinized.
5. Flow: think/make/check.
6. Focus on solving the right problem.
What do we do?
7. Generate many options & decide quickly
what to pursue.
8. Recognize hypotheses & validate them.
How can we be
sure? 9. Research with users is the best source of information.
www.proof-nyc.com
For more, see: http://luxr.co/lean-ux/10-principles-for-lean-ux/ License: CC BY-NC-SA
@jseiden
Thursday, April 12, 12

17. It’s not Lean UX if...
www.proof-nyc.com License: CC BY-NC-SA
10
www.slideshare.net/jseiden United States
Thursday, April 12, 12

18. It’s not Lean UX if...
• UX designers are doing it alone in a room
www.proof-nyc.com License: CC BY-NC-SA
10
www.slideshare.net/jseiden United States
Thursday, April 12, 12

19. It’s not Lean UX if...
• UX designers are doing it alone in a room
• You’re not explicitly declaring your hypotheses
and testing them
www.proof-nyc.com License: CC BY-NC-SA
10
www.slideshare.net/jseiden United States
Thursday, April 12, 12

20. KEY METHODS
www.proof-nyc.com License: CC BY-NC-SA
www.slideshare.net/jseiden United States
Thursday, April 12, 12

21. Key Methods for Lean UX
1. Get the incentive structure right
2. Identifying Assumptions
3. Expressing Hypotheses
4. Experiments / MVPs
www.proof-nyc.com License: CC BY-NC-SA
www.slideshare.net/jseiden United States
Thursday, April 12, 12

22. Method: get the incentives right
www.proof-nyc.com License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
Thursday, April 12, 12

23. Method: get the incentives right
www.proof-nyc.com License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
Thursday, April 12, 12

24. Method: get the incentives right
In-house teams:
 problem-focused, not deliverable-focused.
www.proof-nyc.com License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
Thursday, April 12, 12

25. Method: get the incentives right
In-house teams:
 problem-focused, not deliverable-focused.
 results, not features.
www.proof-nyc.com License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
Thursday, April 12, 12

26. Method: get the incentives right
In-house teams:
 problem-focused, not deliverable-focused.
 results, not features.
www.proof-nyc.com License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
Thursday, April 12, 12

27. Method: get the incentives right
In-house teams:
 problem-focused, not deliverable-focused.
 results, not features.
Agencies:
www.proof-nyc.com License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
Thursday, April 12, 12

28. Method: get the incentives right
In-house teams:
 problem-focused, not deliverable-focused.
 results, not features.
Agencies:
 Charge for hours, charge for results, charge for
continuous work.
www.proof-nyc.com License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
Thursday, April 12, 12

29. Key Methods for Lean UX
1. Get the incentive structure right
2. Identifying Assumptions
3. Expressing Hypotheses
4. Experiments / MVPs
www.proof-nyc.com License: CC BY-NC-SA
www.slideshare.net/jseiden United States
Thursday, April 12, 12

30. Declare your assumptions
www.proof-nyc.com License: CC BY-NC-SA
www.slideshare.net/jseiden United States
Thursday, April 12, 12

31. Declare your assumptions
What assumptions do you have?
www.proof-nyc.com License: CC BY-NC-SA
www.slideshare.net/jseiden United States
Thursday, April 12, 12

32. Declare your assumptions
What assumptions do you have?
…about your customers and business?
www.proof-nyc.com License: CC BY-NC-SA
www.slideshare.net/jseiden United States
Thursday, April 12, 12

33. Declare your assumptions
What assumptions do you have?
…about your customers and business?
…that if proven false, will cause you to fail?
www.proof-nyc.com License: CC BY-NC-SA
www.slideshare.net/jseiden United States
Thursday, April 12, 12

34. Focus on higher risk, higher uncertainty
High Risk
prioritize here
Understood Uncertain
www.proof-nyc.com
www.slideshare.net/jseiden
Low Risk License: CC BY-NC-SA
United States
Thursday, April 12, 12

35. Key Methods for Lean UX
1. Get the incentive structure right
2. Identifying Assumptions
3. Expressing Hypotheses
4. Experiments / MVPs
www.proof-nyc.com License: CC BY-NC-SA
www.slideshare.net/jseiden United States
Thursday, April 12, 12

36. Method: hypotheses
We believe that ______________.
We will know we have succeeded when qualitative and
quantitative outcome. This will improve KPI.
www.proof-nyc.com License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
Thursday, April 12, 12

37. Key Methods for Lean UX
1. Get the incentive structure right
2. Identifying Assumptions
3. Expressing Hypotheses
4. Experiments / MVPs
www.proof-nyc.com License: CC BY-NC-SA
www.slideshare.net/jseiden United States
Thursday, April 12, 12

38. Method: Minimum Viable Product
www.proof-nyc.com License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
Thursday, April 12, 12

39. Method: Minimum Viable Product
www.proof-nyc.com License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
Thursday, April 12, 12

40. Method: Minimum Viable Product
What is the smallest thing we can make to test
our hypothesis?
www.proof-nyc.com License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
Thursday, April 12, 12

41. Method: Minimum Viable Product
What is the smallest thing we can make to test
our hypothesis?
The answer to this question is your MVP.
www.proof-nyc.com License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
Thursday, April 12, 12

42. MVPs are experiments
1. Think about learning, not launching
2. Take an assumption and try to invalidate it in the
market with qualitative and quantitative methods.
www.proof-nyc.com License: CC BY-NC-SA
www.slideshare.net/jseiden United States
Thursday, April 12, 12

43. If you liked this talk, please follow me
THANK YOU!
@jseiden @proof_nyc
josh@proof-nyc.com
www.proof-nyc.com License: CC BY-NC-SA
www.slideshare.net/jseiden United States
Thursday, April 12, 12