Lean UX for Agile Teams

2,345 views
2,192 views

Published on

My slides from my talk at Agile Austin, March 2013. The talk covered key concepts from the book "Lean UX", written by Jeff Gothelf and me, and available here: www.leanuxbook.com

Published in: Design

Lean UX for Agile Teams

  1. 1. March 11, 2013Lean UX forAgile Teams Jeff Gothelf Josh Seiden www.neo.com
  2. 2. Me and my #hashtagsJosh Seidenwww.neo.com@jseiden@neo_innovation#leanUX#leanStartup
  3. 3. Internet Mouse
  4. 4. The Lean UX CycleState  your  desired  outcomes IdeasDeclare  your  assump2onsHypothesize:  write  the  test  first Learn BuildDesign  an  Experiment  Make  an  MVPGet  out  of  the  buildingTeam  synthesis Data ProductRepeat Measure
  5. 5. AGENDA1. MANAGE OUTCOMES2. FREEDOM TO EXPERIMENT3. CONTINUOUS LEARNING 5
  6. 6. 1MANAGE OUTCOMES 6
  7. 7. Output
  8. 8. Outcome
  9. 9. Impact
  10. 10. Many companies manage to output.Instead, focus on outcomes.Don’t make teams responsible for impact.
  11. 11. Case Study: TheLadders 14%
  12. 12. Case Study: TheLadders 63%
  13. 13. 2FREEDOM TO EXPERIMENT 15
  14. 14. Kill
  15. 15. Pivot
  16. 16. Double-down
  17. 17. 2. Freedom to experiment….and fail1. Run small, low-risk experiments2. Refine your hypotheses3. Reward learning (aka failure)4. Make decisions based on objective observations
  18. 18. Case Study: Social Media BenchmarkingObserved: Small business owners want to use social mediafor marketing but don’t know how.Hypothesis: They would pay for a service that providesbenchmarking data from their peers. 20
  19. 19. What’s the smallest thing we can build? 21
  20. 20. Don’t design a product,design an experiment. 22
  21. 21. 23
  22. 22. 24
  23. 23. 25
  24. 24. 26
  25. 25. 3CONTINUOUS LEARNING 27
  26. 26. Reduce Inventory, Risk and Waste This is No one going to clicked. be BIG!Make adesign MONTHS Get feedback from marketdecision HOURS Concept credit: @clevergirl
  27. 27. A system built on continuous learning Risk Learning!Diagram concept: @clevergirl 29
  28. 28. 3. Continuous learning1. Instrument your software to measure usage2. Build a process that includes the customer (regularly)3. Combine the what (quantitative) with the why (qualitative) for a holistic view of your product
  29. 29. AGENDA1. MANAGE OUTCOMES2. FREEDOM TO EXPERIMENT3. CONTINUOUS LEARNING 31
  30. 30. THANK YOU!@jboogie | @jseidenwww.leanuxbook.comwww.neo.com 32

×