The document discusses Lean UX, emphasizing a cross-functional and collaborative approach that prioritizes customer needs over deliverables. It suggests a process focused on continuous discovery, outcomes rather than outputs, and encourages teams to engage in conversation rather than design by committee. The document also highlights the importance of minimal artifacts, rapid prototyping, and involving diverse team members while addressing common challenges in implementing Lean UX.

1. Lean UX
Stop with the Deliverables and
Start Making Experiences
Mary Lukanuski UX Day SF
@mlukanuski March 30, 2013

2. Many years ago….
4/2/13
mlukanuski
2

3. 4/2/13
mlukanuski
3

4. 4/2/13
mlukanuski
4

5. 4/2/13
mlukanuski
5

6. 4/2/13
mlukanuski
6

7. 4/2/13
mlukanuski
7

8. 4/2/13
mlukanuski
8

9. Lean UX is:
• Cross Functional
• Collaborative
• Customer Focused
4/2/13
mlukanuski
9

10. Cross Functional:
This skills, not titles
• UX Research
• UX Design
• Developer
• Product Manager
• Project Manager
• QA
• Marketing
•
4/2/13
Customer Support
mlukanuski
10

11. Collaborative
,
4/2/13
mlukanuski
11

12. 4/2/13
mlukanuski
12

13. 4/2/13
mlukanuski
13

14. No design hero
4/2/13
mlukanuski
14

15. Design leads the facilitation
• Not design by committee
• Lead with conversation
4/2/13
mlukanuski
15

16. Customer Focused
4/2/13
mlukanuski
16

17. Customer Focused
We are making product
• For whom?
• Why?
• What’s the customer’s need?
4/2/13
mlukanuski
17

18. Less about artifact – more about the outcome
4/2/13
mlukanuski
18

19. Think
–
Make
–
Check
loop
4/2/13
mlukanuski
19

20. 4/2/13
mlukanuski
20

21. 4/2/13
mlukanuski
21

22. Hypothesis
Feedback/
MVP
Research
Experiment
4/2/13
mlukanuski
22

23. Design
Studio
4/2/13
mlukanuski
23

24. What’s
The
Problem?
Who’s Involved?
What’s Involved?
- Analytics
- Usability
- Past attempts on correcting
- Business stakeholder Analysis
- Competitive Analysis
4/2/13
mlukanuski
24

25. Problem
Statement
Our
Product
was
designed
to
(these
goals).
We
have
observed
that
the
product
isn’t
meeQng
(these
goals),
Which
is
causing
(bad
stuff)
to
our
business.
How
do
we
improve
so
that
our
customers
are
more
successful
based
on
(measurable
goals)
4/2/13
mlukanuski
25

26. Vanity
Metrics
Lean
AnalyBcs,
Alistair
Croll
&
Benjamin
Yoskovitz
4/2/13
mlukanuski
26

27. 4/2/13
mlukanuski
27

28. Hypothesis
Our
Product
was
designed
to
(these
goals).
We
have
observed
that
the
product
isn’t
meeQng
(these
goals),
Which
is
causing
(bad
stuff)
to
our
business.
How
do
we
improve
so
that
our
customers
are
more
successful
based
on
(measurable
goals)
4/2/13
mlukanuski
28

29. 4/2/13
mlukanuski
29

30. 4/2/13
mlukanuski
30

31. SoluBons
Dump & Sort
Affinity Mapping
4/2/13
mlukanuski
31

32. 4/2/13
mlukanuski
32

33. 4/2/13
mlukanuski
33

34. Vanity
Metrics
Lean
AnalyBcs,
Alistair
Croll
&
Benjamin
Yoskovitz
4/2/13
mlukanuski
34

35. 4/2/13
mlukanuski
35

36. Prototyping
Lo – Paper, Basalmiq
Medium – Visio, Excel, Powerpoint, Omnigraffle
Hi – Axure, Fireworks
SuperHi – HTLM/CSS/Javascript
4/2/13
mlukanuski
36

37. PaKern
Libraries
Lo – Visual
Medium – Interaction Design
Hi – Axure, Fireworks
SuperHi – code
4/2/13
mlukanuski
37

38. 4/2/13
mlukanuski
38

39. 4/2/13
mlukanuski
39

40. Get
Out
Of
The
Building
4/2/13
mlukanuski
40

41. 4/2/13
mlukanuski
41

42. Hypothesis
Feedback/
MVP
Research
Experiment
4/2/13
mlukanuski
42

43. Deliverables
• Light
• Communicate results
• Focus on outcome not output
4/2/13
mlukanuski
43

44. Lean
UX
…
Big
Picture
4/2/13
mlukanuski
44

45. Lean
UX
-­‐
OrganizaBon
• Cross functional
• Small: co located – dedicated
• Lead with Conversation
4/2/13
mlukanuski
45

46. Lean
UX
-­‐
Approach
• Collaborative
• Outcomes not outputs
• Problem Focused
• Light: little waste
• Shared Understanding – Externalize Work
• No Design Hero
• Making over Analysis
• Learning Over Growth
• Permission to Fail
• Lead with Conversation
4/2/13
mlukanuski
46

47. Lean
UX
-­‐
Process
• Continuous Discovery
• Get Out of the Building
• Shared Understanding
• Externalize Work
• Lead with Conversation
4/2/13
mlukanuski
47

48. 4/2/13
mlukanuski
48

49. Now
What
• Work with Agile?
• yes
• Materials Needed?
• Post-Its, sharpies, white boards
• See http://luxr.co/ for complete list
• Non co located teams?
• Yes, Skype etc
• Who’s on the team?
• As much cross functional as you can
• Organizational Support?
• Helps, but just do it, don’t announce a big initiative,
“We’re going to do Lean UX!” . Just invite others
into the process
4/2/13
mlukanuski
49

50. Future
of
Designers
• Outcomes not Portfolios
• Leadership
• We don’t own the solution
• UX Debt equal footing as Tech Debt
4/2/13
mlukanuski
50

51. Lean UX has a rough time in:
• Agencies
• 3 party vendors
• Unresponsive distant teams
• Threatened designers
4/2/13
mlukanuski
51

52. Resources
-­‐
Books
The Lean Startup, Eric Ries
Lean UX, Jeff Gothelf with Josh Seiden
Don’t Make Me Think: Steve Krug
The Four Steps to the Epiphany, Steve Gary Blank
Business Model Generation: A Handbook for Visionaries, Game Changers
and Challengers, Alexander Osterwalder
Lean Analytics, Alister Croll & Benjamin Yoskovitz
Design is a Job, Mike Monteiro
Crucial Conversations, http://www.vitalsmarts.com/crucialconversations/
About Face 3: The Essentials of Interaction Design, Robert Reimann
The Art of Game Design, Jesse Schell
Agile Retrospectives: Making Good Teams Great, Esther Derby
Gamestorming: A Playbook for Innovators, Rulebreakers, and
Changemakers, Sunni Brown
Observing the User Experience: A Practioner’s Guide to User Research,
Mike Kuniavsky
4/2/13
mlukanuski
52

53. Resources
-­‐
Sites
http://sf.lean-ux.com/ - Mike Long
http://www.balancedteam.org/ - Balanced Team
http://luxr.co/ - Janice Fraser
http://www.lanehalley.com/ - Lane Halley
http://www.jeffgothelf.com/blog/ - Jeff Gothelf
4/2/13
mlukanuski
53

54. 4/2/13
mlukanuski
54

55. Thank
You
@mlukanuski
mary@lukanuski.com
4/2/13
mlukanuski
55