Lean UX for Agile Teams
17 likes2,874 views
The document discusses Lean UX principles for Agile teams, emphasizing the importance of managing outcomes over outputs and allowing teams the freedom to experiment. It presents case studies to illustrate methods for refining hypotheses and making decisions based on objective observations. Additionally, it advocates for continuous learning through customer feedback and data measurement.
Lean UX for Agile Teams
- 1. March 11, 2013 Lean UX for Agile Teams Jeff Gothelf Josh Seiden www.neo.com
- 2. Me and my #hashtags Josh Seiden www.neo.com @jseiden @neo_innovation #leanUX #leanStartup
- 4. The Lean UX Cycle State your desired outcomes Ideas Declare your assump2ons Hypothesize: write the test first Learn Build Design an Experiment Make an MVP Get out of the building Team synthesis Data Product Repeat Measure
- 5. AGENDA 1. MANAGE OUTCOMES 2. FREEDOM TO EXPERIMENT 3. CONTINUOUS LEARNING 5
- 6. 1 MANAGE OUTCOMES 6
- 7. Output
- 8. Outcome
- 9. Impact
- 10. Many companies manage to output. Instead, focus on outcomes. Don’t make teams responsible for impact.
- 11. Case Study: TheLadders 14%
- 14. Case Study: TheLadders 63%
- 15. 2 FREEDOM TO EXPERIMENT 15
- 16. Kill
- 17. Pivot
- 18. Double-down
- 19. 2. Freedom to experiment….and fail 1. Run small, low-risk experiments 2. Refine your hypotheses 3. Reward learning (aka failure) 4. Make decisions based on objective observations
- 20. Case Study: Social Media Benchmarking Observed: Small business owners want to use social media for marketing but don’t know how. Hypothesis: They would pay for a service that provides benchmarking data from their peers. 20
- 21. What’s the smallest thing we can build? 21
- 22. Don’t design a product, design an experiment. 22
- 23. 23
- 24. 24
- 25. 25
- 26. 26
- 27. 3 CONTINUOUS LEARNING 27
- 28. Reduce Inventory, Risk and Waste This is No one going to clicked. be BIG! Make a design MONTHS Get feedback from market decision HOURS Concept credit: @clevergirl
- 29. A system built on continuous learning Risk Learning! Diagram concept: @clevergirl 29
- 30. 3. Continuous learning 1. Instrument your software to measure usage 2. Build a process that includes the customer (regularly) 3. Combine the what (quantitative) with the why (qualitative) for a holistic view of your product
- 31. AGENDA 1. MANAGE OUTCOMES 2. FREEDOM TO EXPERIMENT 3. CONTINUOUS LEARNING 31
- 32. THANK YOU! @jboogie | @jseiden www.leanuxbook.com www.neo.com 32