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

Lean UX hasn't been embraced by large organisations. It's not them - it's us!

E1de986e1b1abe566bcaaf897f903a11?s=47 spencer
June 09, 2016

Lean UX hasn't been embraced by large organisations. It's not them - it's us!

Presented at UXScotland 2016

E1de986e1b1abe566bcaaf897f903a11?s=128

spencer

June 09, 2016
Tweet

Transcript

  1. hello
 I’m Spencer @spencerturner

  2. Lean UX hasn't been embraced by large orgs. it’s not

    them… it’s us!
  3. A short story

  4. None
  5. None
  6. None
  7. None
  8. None
  9. None
  10. None
  11. None
  12. None
  13. None
  14. None
  15. None
  16. We’re ready, we’ve mapped
 our assump5ons, captured our hypothesis, we’ve

    co-designed our MVP.
  17. You are 100% empowered to be
 both Lean and Agile

    (within the constraints of a quarterly profit reporting cycle, and working with IT’s six month lead time, assuming you have budget in place a year in advance.)
  18. (within the constraints of a quarterly profit reporting cycle, and

    working with IT’s six month lead time, assuming you have budget in place a year in advance.)
  19. None
  20. Title Text Banksy (Boston)

  21. Show of hands

  22. Why so hard? Lean UX Principles

  23. Cross Func3onal Teams

  24. Issues Faced • Internal Capability • Up/Cross/Re-skilling • Departmental silos

    • Departmental KPIs • Unclear repor5ng structure Cross Func3onal Teams
  25. Small, Dedicated, 
 Co-located

  26. Issues Faced • Small is hard in large orgs. •

    Dedicated – OOen not… • Co-Located – Some5mes Small, Dedicated, Co-located
  27. Progress is Outcomes
 not Outputs

  28. Issues Faced Only if outcomes are: • Understood • Acceptable

    • (Profitable?) Progress is Outcomes not Outputs
  29. Get out of the Deliverables
 Business

  30. Issues Faced Very hard for business: • to understand! •

    to execute on. Get out of the Deliverables Business
  31. Rapid Prototyping

  32. Issues Faced • Reputa5on worry • Difficulty repor5ng back
 (expecta5on

    of ‘quality’ being valuable) Rapid Prototyping
  33. Problem Focused Teams

  34. Issues Faced • Teams may be problem focused • Organisa5on

    Silos s5ll have conflic5ng ‣ KPIs ‣ desires ‣ requirements Problem Focused Teams
  35. Defer Decisions (a.k.a. Real Op+ons) http://commitment-thebook.com/

  36. Issues Faced Extremely long lead 5mes for: • budget •

    planning Defer Decisions
  37. Small Batch Size

  38. Issues Faced • Everyone wants to see the en5re concept

    • Wants their idea included Small Batch Size
  39. Con3nuous 
 Discovery

  40. Get out of the building

  41. Issues Faced • We did user research 2 years ago.

    • We can’t show users
 (Our product is secret) • Users are too important / busy • I KNOW what the users want, just build what’s in my head. Con3nuous Discovery / GOOB
  42. An3-paFern: Rockstars, Gurus,
 and Ninjas

  43. Issues Faced You oOen can’t pick your team. ‘Resources’ are

    assigned to you and can be changed in and out. An3-paFern: Rockstars, Gurus, and Ninjas
  44. Shared Understanding Successful
 Product Business Goals Customer
 Needs

  45. Externalise your work

  46. Issues Faced How can you share this across a large

    disparate group? • To where? • To whom? • How? Shared Understanding / Externalise your work
  47. Making over Analysis

  48. Issues Faced We like making… You are making the finished

    product now though, right? Making over Analysis
  49. Learning over Growth

  50. Issues Faced We like learning… You are making the finished

    product now though, right? Learning over Growth
  51. Permission to Fail

  52. Issues Faced • Failure sounds bad! • People’s jobs/bonuses rest

    on success! • Org. don’t believe that learning early that something won’t work is valuable Permission to Fail
  53. Lean / Lean UX / Agile are not silver-bullets.

  54. So… How can we fix it?

  55. Educate & Empower

  56. Extend our remit

  57. Visualise (Draw) things! • Maps • Cartoons • Diagrams

  58. Earn Trust

  59. Demonstrate The Value (SHOW DON’T TELL)

  60. Focus on Outcomes (PUSH BACK IF UNDEFINED)

  61. Use Informal Networks

  62. Mi3gate the HiPPOs

  63. De-Risk The Process

  64. Reframe Language .

  65. Ask “Why?” (THEN LISTEN TO THE ANSWER!)

  66. Acknowledge Pressures

  67. Find New Ways (**** the Status Quo)

  68. Hack the System

  69. Thank You Any Ques5ons? @spencerturner