Lean UX - Integrated Teams

  • 3,018 views
Uploaded on

Lean UX presented by Fabio Armani at the Bettersoftware 2012 Conference in september 2012. …

Lean UX presented by Fabio Armani at the Bettersoftware 2012 Conference in september 2012.

Cosa è Lean UX?
User Centered Design x Lean Startup (Customer Development + approcci Lean & Agile).

Per la prima volta, i metodi User Centered Design hanno il dovuto slancio nel mondo degli affari.
Quando la comunità imprenditoriale comincia a misurare il valore dell'esperienza dell'utente, è il momento in cui essa investe su questo importante aspetto come un driver di valore, piuttosto che come un costo da minimizzare.

Quando la scienza del Lean Startup include lo "user centered design" come uno dei suoi attrattori principali, noi progettisti abbiamo una nuova opportunità di fare grandi cose.

In questo talk vorrei parlare dell'importanza del movimento Lean UX e di come questo possa condurre alla realizzazione di un team integrato che superi il semplice concetto di Product Owner, andando a definire un più vasto concetto di Product Ownership.

Oltre alla trattazione teorica dei concetti fondamentali, verranno forniti esempi tratti dalle mie molteplici esperienze di Coaching e Consulting in diversi contesti con aziende di medie e grandi dimensioni.

More in: Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
3,018
On Slideshare
0
From Embeds
0
Number of Embeds
5

Actions

Shares
Downloads
99
Comments
0
Likes
22

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. openware #LeanUX  |  @fabioarmani  
  • 2. About  me  •  Fabio Armani•  CEO of OpenWare•  Artistic Director of Different Lands•  @fabioarmani•  f.armani@open-ware.org•  armani.fabio@gmail.com
  • 3. Tradi6onal  UX   • User  Interviews   • Context  Inquiry   Lean  UX   Agile  UX   •  Hypothesis   • Direct  interac5ons   •  Experiment,   • Rapid  itera5ons   validated  learning  Anders Ramsay.com
  • 4. Tradi6onal  UX   • Design,  Usability   • What  are  we  making?   Lean  UX   Agile  UX   •  Measuring,   • Collabora6on,   valida6ng  product   Delivery   •  Are  we  making   • How  do  we  make   the  right  thing?   it?  Anders Ramsay.com
  • 5. What is Lean UX?User Centered DesignxLean Startup (Customer Development + Lean & Agile approaches)Anders Ramsay.com
  • 6. Roots Of Lean Startup make products incremental reduce customer wants releases waste #LeanUX  |  @fabioarmani  
  • 7. For the first time, user centred design methods have momentumin the business community
  • 8. When the business community begins to measure the value of user experience, they will invest in it as a driver of value,rather than a cost to be minimized
  • 9. When the science of startups includes user centred design as one of its tent-poles, we havea new opportunity to do great things
  • 10. Lean UX means...•  Tight collaboration of UX, Product Management, Development•  Know your customers (users) and their needs•  Prioritize to reduce wasted effort•  Focus releases on specific user goals•  Externalize your ideas and your process•  Test design hypotheses rapidly and repeatedly•  Observing, learning, and adjusting with rapid cycles of Think-Make-Check
  • 11. Lean UX CyclesGenerative Research Ideation THINK Mental models Behaviour Models Test ResultsCompetitive Analysis MAKE Prototypes Wireframes Value Prop Landing Page Hypotheses Comps Deployed Code A/B Testing Site Analytics Usability Testing CHECK Funnel Sign-ups #LeanUX  |  @fabioarmani  
  • 12. Agile Sprints Velocity Points Iterations Only  part  of   Continuous Deployment the  story!     S1 S2 S3 S4 Lean UX CyclesLean UX Cycles Generative Research Reduce  cycle   Ideation THINK Lean   6me  not   Mental models build  6me     Behavior Models Test Results Competitive Analysis MAKE Prototypes Wireframes Value Prop Landing Page A/B Testing Hypotheses Site Analytics Comps Usability Testing Deployed Code Funnel Sign-ups CHECK #LeanUX  |  @fabioarmani  
  • 13. Lean UX Framework Lean UX Framework Users Users why 1. BLAH why what Needs 2. BLAH 1. BLAH Needs 3. BLAH 2. BLAH ople what how pe 3. BLAH uct ple pro d peo how BUSINESS THINKING uct Bob can... pro d BUSINESS THINKING Uses/Scenarios Bob can... Uses/Scenarios Features (CREATE SKETCHES, Features WIREFRAMES & PIXELS) (CREATE SKETCHES, This Week WIREFRAMES & PIXELS) User Stories This Week Themed Releases User Stories Themed Releases
  • 14. Solving  problem  together  Every  member  of  your  team  is  present  during  brainstorming  for  new  projects   #LeanUX  |  @fabioarmani  
  • 15. Sketch  Help  them  visualize  their  ideas  and  come  to  a  consensus   #LeanUX  |  @fabioarmani  
  • 16. Prototype  Get  to  a  product  experience  as  quickly  as  possible   #LeanUX  |  @fabioarmani  
  • 17. Prototype  Get  to  a  product  experience  as  quickly  as  possible  
  • 18. Pair  your  developers  and  designers  Have  developers  and  designers  pair  up  to  create  the  user  interfaces     #LeanUX  |  @fabioarmani  
  • 19. Create  a  style  guide  Codify  your  design  elements  in  paRern  libraries  and  code  repositories       #LeanUX  |  @fabioarmani  
  • 20. Why? Who? What? How? Create & Delivery Refine & Evolve
  • 21. Gather customer, business, and technical insights that provide insight into customerand business goals and identify opportunitiesfor inspiration, improvement, and innovation.
  • 22. We  place  the  customer  at  the  heart  of  our  design  thinking  to  produce  a  mul6tude  of  ideas  to  create   different  opportuni6es.
  • 23. We  elaborate  on  the  vision  and  plan  what  we’ll  need  to  do  to  get  a  product  into  produc6on  as   quickly  as  possible.
  • 24. We  think  about  the  cri6cal  path  and,  as  in  lean  manufacturing,  produce  our  design  inventory  just   in  6me.
  • 25. You  then  seek  to  con6nuously  improve  your  product  through  a  process  of  test  and  learn.
  • 26. Agile experience design is   Inclusive rather than elitist Emergent with direction rather than up front Integrated and collaborative rather than handed over the fence Considerate of customer, rather than biased toward a singlebusiness and technology needs factor  
  • 27. Agile   Business   AXD   enableTechnology   Customer   Design  
  • 28. Lean UXInspired by Lean Startup and Agile development theories, it’sthe practice of bringing the true nature of our work to lightfaster, with less emphasis on deliverables and greater focus onthe actual experience being designed. Jeff Gothelf #LeanUX  |  @fabioarmani  
  • 29. Agile•  Individuals and interactions over processes and tools•  Working software over comprehensive documentation•  Customer collaboration over contract negotiation•  Responding to change over following a planLeanLean Startup initially advocates the creation of rapid prototypesdesigned to test market assumptions, and uses customerfeedback to evolve them much faster than via more traditionalsoftware engineering practices. #LeanUX  |  @fabioarmani  
  • 30. 12  emerging  best  prac6ces  •  Drive: UX practitioners are part of the customer or product owner team•  Research, model, and design up front - but only just enough•  Chunk your design work•  Use parallel track development to work ahead, and follow behind•  Buy design time with complex engineering stories•  Cultivate a user validation group for use for continuous user validation•  Schedule continuous user research in a separate track from development•  Leverage user time for multiple activities•  Use RITE to iterate UI before development•  Prototype in low fidelity•  Treat prototype as specification•  Become a design facilitator
  • 31. Johnny Rotten
  • 32. Dont know what I want, but I know how to get it
  • 33. Dont know what I want, but I know how to get it Sex Pistol’s Anarchy in the UK
  • 34. We know what we want. Can youestimate how long it will take to build?  
  • 35. We know what we want. Can youestimate how long it will take to build?
  • 36. We need to get these requirements nailed down ….fore we can start development.
  • 37. We need to get these requirements nailed down before we can start development.
  • 38. We use an iterative andincremental agile process
  • 39. Potentially shippable product increment
  • 40. ?  Potentially shippable product increment
  • 41. Iterating and incrementing are separate ideashRp://www.agileproductdesign.com/blog/dont_know_what_i_want.html  
  • 42. Incremen6ng  Iterating and incrementing are separate ideas
  • 43. 1.  Someone  in  the  business  has  an  idea  
  • 44. 1.  Someone  in  the  business  has  an  idea  
  • 45. 2.  The  development  team  decompose  the  idea  into  stories   As a user I want to … so that …
  • 46. 2.  The  development  team  decompose  the  idea  into  stories  
  • 47. 4.  The  team  delivers  in  increments,  tackling  the  technically   hardest  func6onality  first  
  • 48. 5.  They  deliver  high-­‐quality  stories  on  6me  and  on  budget,   adding  func6onality  itera6vely.  
  • 49. 6.  Yet  the  end  result  is  not  quite  what  everyone  expected!  
  • 50. The  process  is  far  from  ideal  
  • 51. Itera6ng  Itera6ng  and  incremen6ng  are   separate  ideas  
  • 52. Let’s  see  if  we  can  fix  it  by  injec6ng  some  user  experience  
  • 53. 1.  Someone  in  the  business  sees  an  opportunity  
  • 54. 1.  Someone  in  the  business  sees  an  opportunity  
  • 55. 2.  A  cross-­‐func6onal  team  comes  together  
  • 56. 3.  Everyone  has  lots  of  different  ideas  
  • 57. 3.  Everyone  has  lots  of  different  ideas  
  • 58. 4.  Everyone  collaborates  to  reach  a  shared  understanding   We  could   use  that   landscape  
  • 59. 5.  They  discover  new  ideas  by  gefng  out  of  the  office  
  • 60. 6.  Rapid  sketching  brings  the  vision  to  life  
  • 61. 7.  With  a  clearer  vision  we  produce,  priori6ze,  and  es6mate  user  stories  and  create  a  development  plan  
  • 62. 8.  Detail  emerges  throughout  the  development  process,  directed  by  the  vision  
  • 63. 8.  Detail  emerges  throughout  the  development  process,  directed  by  the  vision  
  • 64. The  result  is  a  useful,  usable  and   desirable  product    
  • 65. This is not a return to big, up- front design
  • 66. we Iterate for multiple reasons
  • 67. we iterate to find the right solution
  • 68. then given some goodcandidate solution, we might then iterate to improve a candidate solution
  • 69. we Increment for multiple reasons
  • 70. we use incrementing togradually build up functionality
  • 71. we release incrementally so that we actually get that business value were chasing.
  • 72. Itera6ve-­‐incremental   iterativity Spiral model Agile space incrementalness Waterfall Staged deliveryhttp://samipoimala.com/it/2010/04/16/iterations-and-increments-explained/ #LeanUX  |  @fabioarmani  
  • 73. Design-­‐led  par6cipa6on   Design focus Agency Participatory Participation & collaboration approach design Expert led Enterprise approach Research focus #LeanUX  |  @fabioarmani  
  • 74. Designers  and  developers  paring  hRp://www.uxmindset.com  
  • 75. hRp://www.uxmindset.com/2011/11/lean-­‐ux-­‐agile-­‐development-­‐the-­‐next-­‐big-­‐thing-­‐in-­‐sokware-­‐development/  
  • 76. The  life  of  a  story   Week  1   Week  2   Week  3   Week  4  Iteration1 Itera6on  Planning  Mee6ng   Story  Planning  Mee6ng   Showcase   Design  Review  Mee6ng   Retrospec6ve   Analysis & Design Code Test / Deploy Iteration2 Itera6on  Planning  Mee6ng   Story  Planning  Mee6ng   Showcase   Design  Review  Mee6ng   Retrospec6ve   Analysis & Design Code Test / Deploy
  • 77. Adding Design into the Mix
  • 78. Design  works  ahead  of  development  …     Itera*on  0   Itera*on  1   Itera*on  2   Itera*on  3  Developers Set up Code Code Code environments Designers Design for Design for Design for Design for Iteration 3 Iteration 4 Iteration 1 Iteration 2 Test completed Test completed code code Design and test future concepts
  • 79. Working as a team
  • 80. UX  Prod   Dev   QA  
  • 81. a shared goal
  • 82. co-creation
  • 83. one in front: providing design and defining interaction behaviour for the stories
  • 84. one in front: providing design and defining interaction behaviour for the stories
  • 85. clarifying: supporting the developer in the iteration with the design
  • 86. clarifying: supporting the developer in the iteration with the design
  • 87. testing: testing the story with customer
  • 88. testing: testing the story with customer
  • 89. Design spikes and evolving vision: defining and driving the vision to ensure design coherence and creative integrity
  • 90. Design spikes and evolving vision: defining and driving the vision to ensure design coherence and creative integrity
  • 91. What  we  really  need  is  a  shared   accountability  model…    
  • 92. a  team  of  people,  each  of  whom  work   together  as  part  of  the  team…  
  • 93. a  team  of  people,  each  of  whom  work   together  as  part  of  the  team…   #LeanUX  |  @fabioarmani  
  • 94. What Lean UX is… #LeanUX  |  @fabioarmani  
  • 95. Lean UXUser Centered DesignxLean Startup (Customer Development + Lean & Agile approaches)
  • 96. Fabio Armani"CEO OpenWare"f.armani@open-ware.org"@fabioarmani"