Se ha denunciado esta presentación.
Se está descargando tu SlideShare. ×

(Agile 2011) Lean UX: Getting Out of the Deliverables Business

Más Contenido Relacionado

Audiolibros relacionados

Gratis con una prueba de 30 días de Scribd

Ver todo

(Agile 2011) Lean UX: Getting Out of the Deliverables Business

  1. 1. Lean UX<br />Getting out of the deliverables business<br />Agile 2011<br />Salt Lake City, UT<br /><br />
  2. 2. Why am I up here?<br />Designer. Team Leader. Lover of conference schwag. <br />Jeff Gothelf<br />currently: <br />Director of UX at<br />previously: <br />Publicis Modem, Webtrends, AOL, Fidelity and an assortment of startups<br />blog: <br /><br />twitter: <br />@jboogie<br />email: <br /><br />#LeanUX<br />
  3. 3. In the beginning…<br />UX began with Information Architecture which no one had ever heard of<br />#LeanUX | @jboogie<br /><br />
  4. 4. Deliverables helped define Information Architecture<br />And this was good<br />#LeanUX | @jboogie<br />
  5. 5. IA evolved and expanded into Interaction Design<br />Darwinism at work<br />#LeanUX | @jboogie<br />
  6. 6. Deliverables helped define these emerging practices<br />And this was good<br />#LeanUX | @jboogie<br />
  7. 7. Value has ultimately been placed on the deliverable<br />Not on the experience being created<br />#LeanUX | @jboogie<br />
  8. 8. Deliverables eat babies!<br />I kid. Only a little.<br />#LeanUX | @jboogie<br />
  9. 9. With interactive experiences evolving rapidly<br />The deliverable is just not enough<br />#LeanUX | @jboogie<br />
  10. 10. Lean UX<br />Inspired by Lean Startup and Agile development theories, it’s the practice of bringing the true nature of design work to light faster, with less emphasis on deliverables and greater focus on the actual experience being designed.<br />#LeanUX | @jboogie<br />
  11. 11. It goes a little something like this…<br />Look familiar?<br />Just the UX process<br />Prototype<br />Concept<br />Validate Internally<br />Test Externally<br />Learn from user behavior<br />Iterate<br />#LeanUX | @jboogie<br />
  12. 12. Designers can’t hide behind their monitor any more!<br />Hope you like hanging out with designers.<br />#LeanUX | @jboogie<br /><br />
  13. 13. Get design work out there. Fast.<br />In public. (Yes, where everyone can see it.)<br />#LeanUX | @jboogie<br />
  14. 14. What Lean UX is NOT<br />#LeanUX | @jboogie<br />
  15. 15. Lazy.<br />Sorry. Designers still have to work hard.<br />“…the best part … is that the team is doing a F@&K-TON of UX. They document a ton of stuff explicitly on the walls and implicitly in shared understanding among team members.”<br /><ul><li>Austin Govella</li></ul>commenting on Whitney Hess’s “Why I Detest the Term Lean UX”<br /><br />#LeanUX | @jboogie<br /><br />
  16. 16. The only thing being removed is waste.<br />You leave that stuff laying around and it starts to stink!<br />#LeanUX | @jboogie<br /><br />
  17. 17. This is NOT design-by-committee!<br />That never leads to anything pretty.<br />#LeanUX | @jboogie<br /><br />
  18. 18. What Lean UX is…<br />#LeanUX | @jboogie<br />
  19. 19. Control<br />Designers still drive the design<br />#LeanUX | @jboogie<br />
  20. 20. “But I’m giving up control of my work!”<br />Not really. It just feels that way at first.<br />#LeanUX | @jboogie<br /><br />
  21. 21. It’s not “The Spec” that gives control<br />That’s the last mile of the value design brings to the team<br />#LeanUX | @jboogie<br /><br />
  22. 22. If a designer spends 3 months perfecting a design only to find out it fails to meet customer and/or business needs, they’ve just wasted 3 months of their life, not to mention the team’s.<br />#LeanUX | @jboogie<br />
  23. 23. Designers shouldn’t be expected to get it right the first time<br />Nobody else has to<br />From Design Criticism and the Creative Process by Cassie McDaniel on A List Apart, 11 Jan, 2011.<br /><br />#LeanUX | @jboogie<br />
  24. 24. Designers are the “Keepers of the Vision”<br />The experience is design’s responsibility<br />#LeanUX | @jboogie<br /><br />
  25. 25. Momentum<br />Everyone’s engaged. Everyone’s motivated.<br />#LeanUX | @jboogie<br />
  26. 26. Keep everybody moving forward<br />Clients, stakeholders, design and team.<br />#LeanUX | @jboogie<br /><br />
  27. 27. Quality<br />No compromises<br />#LeanUX | @jboogie<br />
  28. 28. “Speed first. Aesthetics second.” <br />– Jason Fried,<br />#LeanUX | @jboogie<br />
  29. 29. “Going for the bronze.” <br />– A Creative Director I used to work with<br />#LeanUX | @jboogie<br />
  30. 30. What about the quality of the design?<br />Iterations mean quality continually improves.<br />#LeanUX | @jboogie<br /><br />
  31. 31. Feasibility<br />Make sure it can be built (and built well)<br />#LeanUX | @jboogie<br />
  32. 32. Prototype it!<br />But not all of it.<br />#LeanUX | @jboogie<br />ht<br />
  33. 33. Once validated, demo to the team.<br />Presto! Instant documentation.<br />No additional deliverables are needed!<br />#LeanUX | @jboogie<br /><br />
  34. 34. Then show it to your customers.<br />Keep it light and cheap.<br />#LeanUX | @jboogie<br /><br />
  35. 35. Fill in the gaps<br />What did you not think about?<br />#LeanUX | @jboogie<br />
  36. 36. The more you talk about it<br />The more you realize what’s missing<br />#LeanUX | @jboogie<br /><br />
  37. 37. Can I make this happen in my organization?<br />Short answer: Yes. Long answer: Yessssssssss!<br />#LeanUX | @jboogie<br />
  38. 38. The internal software/web design shop.<br />Well within your grasp.<br />#LeanUX | @jboogie<br /><br />
  39. 39. You are in the problem-solving business and you don’t solve problems with design documentation. You solve them with elegant, efficient and sophisticated software. <br />#LeanUX | @jboogie<br />
  40. 40. The interactive agency and services world.<br />Tougher sell. Worth it in the end.<br />#LeanUX | @jboogie<br />
  41. 41. Agencies are in the deliverables business.<br />#LeanUX | @jboogie<br />
  42. 42. Recapping the “internal” Lean UX process….<br />Remember?<br />Just the UX process<br />Concept<br />Validate Internally<br />Test Externally<br />Learn from user behavior<br />Iterate<br />Prototype<br />#LeanUX | @jboogie<br />
  43. 43. For services agencies it looks slightly different<br />Give your clients the power. They like that.<br />Validate w/client<br />Validate w/client<br />Concept<br />Prototype<br />Iterate<br />Learn from user behavior<br />#LeanUX | @jboogie<br />
  44. 44. Consultants are specialized mini-agencies<br />Success with Lean UX will be determined by attention level<br />#LeanUX | @jboogie<br />
  45. 45. Reducing deliverables efforts reduces revenue<br />In theory…<br />Fewer deliverables<br />Fewer billable hours<br />$$$$<br />Project delivered faster<br />Happier, more empowered client<br />Repeat customer<br />#LeanUX | @jboogie<br />
  46. 46. Invest in your client’s success<br />It shows the confidence you have in your work<br />#LeanUX | @jboogie<br /><br />
  47. 47. Distributed teams do it remotely!<br />If they’re a part of you, it’s on! If not, it ain’t bloody likely.<br />#LeanUX | @jboogie<br /><br />
  48. 48. Is this good for every project?<br />Use it where it makes sense.<br />#LeanUX | @jboogie<br /><br />
  49. 49. Functional, task-flow projects work well.<br />There’s a clear end goal.<br />#LeanUX | @jboogie<br />
  50. 50. Highly experiential marketing projects will struggle.<br />Time to ideate and create options is essential.<br />#LeanUX | @jboogie<br />
  51. 51. What about content heavy experiences?<br />Some up front planning is necessary.<br />#LeanUX | @jboogie<br />
  52. 52. Case Study<br />100 Days of Collaboration<br />#LeanUX | @jboogie<br />
  53. 53. Problem Statement:<br />“You’re like Monster, but I have to pay for it.”<br />#LeanUX | @jboogie<br />
  54. 54. 3 days, 3 themes:<br />Acquisition and conversion<br />Resume services<br />A human in every interaction<br />#LeanUX | @jboogie<br />
  55. 55. #LeanUX | @jboogie<br />
  56. 56. #LeanUX | @jboogie<br />
  57. 57. #LeanUX | @jboogie<br />
  58. 58. #LeanUX | @jboogie<br />
  59. 59. #LeanUX | @jboogie<br />
  60. 60. How do I get started?<br />Here are 5 quick wins you can implement today<br />#LeanUX | @jboogie<br />
  61. 61. 1<br />Solve the problem together<br />As opposed to implementing someone else’s solution<br />#LeanUX | @jboogie<br /><br />
  62. 62. 2<br />Sketching<br />It’s all the rage!<br />#LeanUX | @jboogie<br />
  63. 63. 2<br />Example of sketching at work<br />V1 of the UI<br />#LeanUX | @jboogie<br />
  64. 64. 2<br />Sketching brings experiences to life faster<br />Launched UI<br />#LeanUX | @jboogie<br /><br />
  65. 65. 3<br />Get the experience out there, not the document<br />Act it out if you have to<br />#LeanUX | @jboogie<br /><br />
  66. 66. 4<br />Pair up!<br />But do it, cross-functionally<br />#LeanUX | @jboogie<br /><br />
  67. 67. 4<br />Pairing saves time<br />It also levels the playing field<br />#LeanUX | @jboogie<br /><br />
  68. 68. 4<br />Pairing sets designers free, man<br />…and empowers developers!<br />#LeanUX | @jboogie<br /><br />
  69. 69. 5<br />Style guides!<br />The cause of, and solution, all your UX problems<br />#LeanUX | @jboogie<br />
  70. 70. 5<br />They’re good for developers too!<br />Creates a reusable asset library and point from which to start<br />#LeanUX | @jboogie<br />
  71. 71. Designers are used to being heroes. <br />Lean UX is distinctly, anti-hero.<br />#LeanUX | @jboogie<br /><br />
  72. 72. This is an evolution. Not a revolution.<br />Designers must evolve to stay relevant.<br />#LeanUX | @jboogie<br /><br />
  73. 73. Once you go lean…<br />Apparently it’s good and you can’t go back to…err…fat…or something<br />#LeanUX | @jboogie<br />
  74. 74. Let’s get back to the experience design business.<br />It’s where it’s at (as the kids say)<br />#LeanUX | @jboogie<br /><br />
  75. 75. Thanks!<br />Call me. Let’s chat.<br />Jeff Gothelf<br />@jboogie<br /><br /><br /><br /><br />#LeanUX | @jboogie<br />

Notas del editor

  • #LeanUX hash tag
  • Traditional design yielded these thick deliverable specs…..that eat babies, right?Well, whether they do or they don’t, they do get in the way of getting a team focusing on the experience. Instead the team focuses on the document itself and getting approval for it instead of validation for the product being designed.