Save 37% off PRO during our Black Friday Sale! »

Agile South Coast - WTF is Lean UX?

E1de986e1b1abe566bcaaf897f903a11?s=47 spencer
November 10, 2015

Agile South Coast - WTF is Lean UX?



November 10, 2015


  1. hello
 I’m Spencer @spencerturner

  2. Our History

  3. Show of hands

  4. WTF is Lean UX? (and why should I care?)

  5. Lean UX Principles

  6. Cross Func?onal Teams

  7. Why should you care? • You’ll find more possible solu5ons

    • You’ll have greater buy-in further on • You’ll build trust within the business that their needs are being considered • You’re team will be more resilient
  8. Small, Dedicated, 

  9. Why should you care? • You’re team will be more

    focused • You’ll communicate more easily • You keep ‘documents’ to a minimum
  10. Progress is Outcomes
 not Outputs

  11. Why should you care? • You’ll build things people use

    • You get to help shape the product, not just ‘build the feature’ • Research backed choices mi5gate HIPPOs
  12. Get out of the Deliverables Business

  13. Why should you care? • Permission to stop was5ng your

    5me producing pointless artefacts!
  14. Rapid Prototyping

  15. Why should you care? • You can learn whether what

    you’re building really solves the problem before you’re over invested • You’ll get quicker, cheaper insight • You’ll remove frustra5on at building **** no-one wants or can’t use.
  16. Rapid Prototyping

  17. Problem Focused Teams

  18. Why should you care? • You’ll have happier teams, as

    they feel trusted and empowered • You’ll see more diverse / innova5ve solu5ons, especially when you have cross-func5onal teams.
  19. Removing Waste • Bureaucracy • Unclear or constantly changing requirements

    • Unnecessary code, func/onality or design • Star/ng more than can be completed • Delay in the development process • Slow or ineffec/ve communica/on • Par/ally done work • Defects and quality issues • Task switching
  20. Why should you care? • Waste is demoralising • Happier

    Team • Happier Business
  21. Defer Decisions (a.k.a. Real Op+ons)

  22. Why should you care? We’ll never know less about our

    project than we know now…
  23. Small Batch Size

  24. Why should you care? • Less upfront design • Remove

    pre-test ‘sign-off’ • Promotes use of style guides not PSDs

  26. Why should you care? • Get feedback earlier • Build

    less before you learn. • Get less ‘skewed’ feedback • Build a more focused product • Actually do itera5ve, not incremental!
  27. Get out of the building

  28. Why should you care? • The whole team talking to

    users (or poten5al users) early and oXen keeps everyone honest • Makes your project ‘real’ - I’m building this for all the people we spoke to who wanted ‘xyz’
  29. Customer Conversa:ons OXen called Customer Development Learn how to speak

    to customers in a way that means they don’t lie to you! Buy this book
 If only I was on commission!
  30. An?-paNern: Rockstars, Gurus,
 and Ninjas

  31. Why should you care? • It’ll make your team happier

    to not have to content with RockNinjaGurus • You’ll have be^er knowledge sharing • Learning won’t be s5fled
  32. Shared Understanding Successful
 Product Business Goals Customer

  33. Why should you care? • It’ll make your team happier

    to not have to content with RockNinjaGurus • You’ll have be^er knowledge sharing • Learning won’t be s5fled
  34. Externalise your work

  35. Why should you care? • More Buy-in earlier from the

    business • You’re not another silo! • Free feedback and ideas • Wider interest in what you’re doing (People oXen ask if you can help them try it on their project!)
  36. Making over Analysis

  37. Why should you care? • Evidence based decisions • Quick

    Feedback on real things • Quicker tests of intangible value items (Stakeholder led assump5ons)
  38. Learning over Growth

  39. Why should you care? • Promote learning first, scaling second

    • Build the right thing • Discard the wrong thing before you’re over commi^ed
  40. Permission to Fail

  41. Why should you care? • Safe to fail experiments give

    the business learning value • Promote the idea that failure isn’t absolute, it’s a path to success • Increase experimenta5on culture
  42. A few Personal Opinions

  43. Lean is not a silver-bullet.

  44. Why should you care? • Don’t believe the hype -

    nothing is an absolute fit in every situa5on • Be flexible • Understand the value and context of the (process | tool | test) you’re sugges5ng
  45. Hack the System

  46. Why should you care? • Organisa5ons are very resistant to

    learning as a value • Find opportuni5es to just do it and prove the value.
  47. Be more Banksy.

  48. Why should you care? • You’ll have to take some

    arrows in the back to protect your team and prove value.
  49. Thank You Any Ques5ons? @spencerturner