Lean UX - State of Affairs

2,593 views
2,472 views

Published on

Going on the question, "If Lean UX is so fabulous why do so few people say they use it?", this presentation shares insights from interviews with a number of agile/lean UX practices to find successful lean UX patterns, and shows how these patterns can help you get started.

Published in: Design, Technology, Business
1 Comment
11 Likes
Statistics
Notes
No Downloads
Views
Total views
2,593
On SlideShare
0
From Embeds
0
Number of Embeds
201
Actions
Shares
0
Downloads
51
Comments
1
Likes
11
Embeds 0
No embeds

No notes for slide

Lean UX - State of Affairs

  1. 1. LEAN UX the state of affairs Taco Ekkel / VP Product Design at ProQuest / @tacoe / #TWAB2012(Notes here) Show of hands: who here uses Lean UX methodologies in their daily practice?
  2. 2. http://www.wisegeek.com/what-is-lean-manufacturing.htmLean: Ford — Toyota — Toyotism — waste reductionImage http://www.wisegeek.com/what-is-lean-manufacturing.htm
  3. 3. 90% OF NEW PRODUCTSIn Software, different origin: products failed a lot. Not because the thing was built wrong, but because the wrong thing was built.
  4. 4. CUSTOMER DEVELOPMENTSteve Blank came along and fixed that by switching product development to customer development. Validated learning.
  5. 5. Agile Dev + Lean UX = FOSSNote that the left part (the book that introduces customer development) is the important part. This middle bit is only tools.
  6. 6. Agile UX Collaborate Ability to respond quickly Build requirements quicklyCentral concept: lean ux builds on agile ux (i.e., not an either/or). The confusion between the two stems from the fact that both focus on reduction of deliverables.
  7. 7. Agile UX Lean UX Collaborate Learn Ability to respond quickly Know what to respond to Build requirements quickly Test hypotheses quicklyCentral concept: lean ux builds on agile ux (i.e., not an either/or). The confusion between the two stems from the fact that both focus on reduction of deliverables.
  8. 8. Agile UX Lean UX Collaborate Learn Ability to respond quickly Know what to respond to Build requirements quickly Test hypotheses quickly Communication over Waste reduction by documentation minimizing deliverablesCentral concept: lean ux builds on agile ux (i.e., not an either/or). The confusion between the two stems from the fact that both focus on reduction of deliverables.
  9. 9. Traditional UXAgile UX + Lean UX
  10. 10. 1. Lean UX2. ????3. Profit!!
  11. 11. (wake-up call)If it were so easy or fantastic, everyone here would’ve raised their hand at the beginningImage http://www.forkparty.com/11785/you-requested-a-wake-up-call-video
  12. 12. 1. Lean UX2. ????3. Profit!!
  13. 13. Questions• If Lean UX is so fabulous why doesn’t everyone use it?• What are practical things you can do to get started with it?
  14. 14. Approach • Qualitative exploratory research • interviews with teams of designers/developers/product people • startups, agencies, product teams in larger companies • Find recurring lean patterns in daily practices • Learning over building • Waste reduction • Speed increasemaker teams: where design/development/product people bump into eachother
  15. 15. PATTERNS
  16. 16. PATTERN Agile: Been There, Done That • Lean-using teams had fully mastered agile • Manifesto flavor, not “agifall” flavor • Signs of having agile mastered • Little formality, lots of personal understanding of the problem space • Emergent planning and detailing of requirements/hypotheses • A feeling that fixed sprint rhythm constrains speed and flexibility • Experimentation with lighter-weight forms (like applying Kanban)Manifesto flavor: people & communication focused. ‘Agifall’ is when everyone does the motions of scrum (standup, etc) but we still require waterfall-like deliverables and steps
  17. 17. RUP 50,000,000 rules Agile (Scrum) 10 rules Kanban 3 rulesNOTE The less rules, the more awesome your team needs to be. I.e., you don’t start on the right sideImage http://jkneilson.wordpress.com
  18. 18. PATTERN Minimum Viable Anything • Not just Minimum Viable Product, but also • Minimum Viable Personality • Minimum Viable Documentation • Minimum Viable API • Really useful as ‘understanding device’ for stakeholdersMakes it easier to prevent stakeholders to throw in too many requirements
  19. 19. PATTERN Learning-focused Measuring• Measure things that’ll help you learn • Not useful: vanity metrics, visitor count, arrival rate • Useful: next/previous action flows, funnels• Not a replacement for getting out of the building
  20. 20. PATTERN Lean Experiments idea id ide a ea problem, idea idea start opportunity idea brainstorm idea idea select ea idea id hypotheses functionalities Keep A, C done A, B, C A, B, C Lose B design / build measure deploy testTimeline is short: One sprint. No A/B needed for many of these!
  21. 21. PATTERN The Design Guardian I’LL SAVE THIS PRODUCT FROM BECOMING AN INCOHERENT MESS • With “constant change”, coherence needs work • Can be anyone — IxD, VD, PO, etc • But someone has to be this • Usually, designer works a sprint ahead for this • “design lead sprint” not necessarily a bad thing
  22. 22. PATTERN Physical Proximity• Developer & UI Designer: Closer = Better • Different physical location, email: bad • Different locations/rooms, Skype: okay • Sitting next to eachother looking at same screen: fantastic • One and the same person: nirvana
  23. 23. PATTERN Front-End Designer Designers Code who know Coders Design • Prototype interaction in browser • not often reused in production code • Labels still in flux • Interaction Engineer, UI Engineer, Front-End Designer, Design Technologist • Often takes the role of design guardian • Not necessarily formally trained either wayIf you’re considering a career switch... consider this
  24. 24. PATTERN Formal Wireframing On The Way Out lower-fi collaborative sketching t you o n, la id eati browser-based prototypes in actual code Axure layo Omnigraffle ut, i nte Visio ract i on ideation, layout, interaction specification• Good riddance. Wireframes did a bunch of things poorly • Since only the IxD can wireframe, slow ideation process • Since wireframes suck at interactivity, bad way to specify interaction• Design in browser — actually code. Usually not used in prod code. Most people just start with jquery or something
  25. 25. The Hammer-Nail Issue“With browser-based design, everything becomes boxes” Photoshop “Pretty but dead pictures” Browser prototyping “Everything looks like Bootstrap”
  26. 26. PATTERN Product Owner In The Trenches• “If the PO isn’t passionate about the user experience, forget about it”• Signs of a PO in the trenches • PO does a lot of sketching • Nitpicky about UI details • Leaning on a design guardian (or being it) • Getting pulled in for UI related discussions whenever possible
  27. 27. PATTERN Terminology Confusion • Some teams using Lean UX patterns don’t self-identify as such • Lean, Agile etc often confused • No one gives a damn what it’s called, as long as it worksNot giving a damn what it’s called is a good thing!
  28. 28. ANSWERS
  29. 29. Using patterns to get started with Lean UX• Q: What practical starting points do these patterns provide? • Get agile UX working first! • Have a design guardian who ensures consistency over time • Design-ahead is not a horrible thing (within limits) • Get designers and developers really close to eachother • If your PO is not passionately in the trenches, buy a new one • Start replacing “requirements” stories with “hypothesis” stories • Run lean experiments
  30. 30. The starting question• Q: “If Lean UX is so fabulous why doesn’t everyone use it?” • Still struggling getting Agile UX to work • Lack of awareness, terminology confusion Agile UX Lean UX Build quickly Learn quickly
  31. 31. THANKS questions?Taco Ekkel / VP Product Design at ProQuest / @tacoe / #TWAB2012

×