Successfully reported this slideshow.

Lean UX: Building a shared understanding to get out of the deliverables business

109

Share

Loading in …3
×
1 of 67
1 of 67

More Related Content

Related Books

Free with a 14 day trial from Scribd

See all

Related Audiobooks

Free with a 14 day trial from Scribd

See all

Lean UX: Building a shared understanding to get out of the deliverables business

  1. Lean UX: Building a shared understanding …and getting out of the deliverables business UX LX Lisbon, Portugal May 18th, 2012
  2. A tale of two cities… …it was (definitely not) the best of times #LeanUX | @jboogie
  3. Building (digital) bridges …turned out to be fairly effective #LeanUX | @jboogie
  4. Aligning corporate strategy with a UX focus …many (expensive) ways to bring awareness #LeanUX | @jboogie
  5. Or the team can spend some time visualizing …to, at least, start from the same point #LeanUX | @jboogie
  6. And we made it easy… …to keep the conversation going #LeanUX | @jboogie
  7. And we made it easy… …to keep the conversation going #LeanUX | @jboogie
  8. #LeanUX | @jboogie http://www.agileproductdesign.com (Jeff Patton)
  9. Visualizing our ideas reveals inconsistencies …between designers, developers, product owners and customers #LeanUX | @jboogie http://www.agileproductdesign.com (Jeff Patton)
  10. Regular discussion leads to iteration …with each iteration leading to broader buy-in #LeanUX | @jboogie http://www.agileproductdesign.com (Jeff Patton)
  11. Ultimately leading to shared understanding …and team alignment #LeanUX | @jboogie http://www.agileproductdesign.com (Jeff Patton)
  12. Shared understanding is the currency of Lean UX …it’s worth its weight in paper, time & productivity #LeanUX | @jboogie http://images.wikia.com/currencies/images/6/65/Euro_coins_and_banknotes.jpg
  13. Lean UX Inspired by Lean Startup and Agile development theories, it’s the practice of bringing the true nature of design work to light faster, in a collaborative, cross-functional way with less emphasis on deliverables and greater focus on the actual experience being designed. #LeanUX | @jboogie
  14. Agile values: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan #LeanUX | @jboogie
  15. #LeanUX | @jboogie
  16. Lean Startup The Lean Startup has as a premise that every startup is a grand experiment that attempts to answer a question. The question is not "Can this product be built?" Instead, the questions are "Should this product be built?" and "Can we build a sustainable business around this set of products and services?" This experiment is more than just theoretical inquiry; it is a first product. #LeanUX | @jboogie
  17. These are philosophies, not methodologies. #LeanUX | @jboogie
  18. It goes a little something like this… Do this. Quickly. Many times. Just the UX process Concept Validate Prototype Test Learn Iterate Internally Externally from user behavior #LeanUX | @jboogie
  19. “Go that way. Really fast. If something gets in your way, turn.” -Charles DeMar (Curtis Armstrong) to Lane Myer (John Cusack) in “Better Off Dead” #LeanUX | @jboogie
  20. In fast-paced environments, traditional UX is a bottleneck We’re getting in our own way #LeanUX | @jboogie http://www.freakingnews.com/Bottle-Neck-Pics-36343.asp
  21. With interactive experiences evolving rapidly The traditional design deliverable is an inefficient obstacle #LeanUX | @jboogie
  22. We have to change perspective on how to “do” UX Today’s markets require a new way of looking at our processes #LeanUX | @jboogie http://offroadinghome.blogspot.com/2011/04/geo-tography-forced-perspective.html
  23. Designers can’t hide behind their monitor any more! This is a designer-led initiative #LeanUX | @jboogie http://www.flickr.com/photos/yamagatacamille/4799648425/sizes/l/
  24. Get design work out there. Fast. In public. Yep, where others can see it. #LeanUX | @jboogie
  25. OK. I’m intrigued. But how does it really work? First 5 things you need to do… #LeanUX | @jboogie
  26. Solve the problem together As opposed to implementing someone else’s solution 1 #LeanUX | @jboogie
  27. Sketching It’s all the rage! 2 It’s Bieber! #LeanUX | @jboogie
  28. Example of sketching at work V1 of the UI 2 #LeanUX | @jboogie
  29. Sketching brings experiences to life faster Launched UI 2 #LeanUX | @jboogie http://www.flickr.com/photos/mims/326748812/sizes/l/
  30. Prototype it! Build an experience, not a document. 3 #LeanUX | @jboogie http://justaddwater.dk/
  31. Once validated, demo to the team. …and get everybody started. 3 No additional deliverables are needed! #LeanUX | @jboogie http://www.flickr.com/photos/koolwaaij/152426460/sizes/o/
  32. Pair up! But do it, cross-functionally 4 #LeanUX | @jboogie http://photofind.com/featured-photo/20-uncomfortable-moments-in-sports
  33. Pairing saves time Builds a common language 4 #LeanUX | @jboogie http://hoveringartdirectors.tumblr.com/page/2
  34. Pairing sets designers free, man …and empowers developers! 4 #LeanUX | @jboogie http://www.clydekellerphotos.com/images/AP_Kesey_HippiesDancing_GALLERY_CGW.jpg
  35. Style guides! The cause of, and solution to, all your UX problems 5 #LeanUX | @jboogie
  36. They’re good for developers too! Creates a reusable asset library and point from which to start 5 #LeanUX | @jboogie
  37. “Speed first. Aesthetics second.” – Jason Fried, 37Signals.com #LeanUX | @jboogie
  38. “Going for the bronze.” – A Creative Director I used to work with #LeanUX | @jboogie
  39. “It’s not iterative if you only do it once.” – Stu Eccles, Technical Director, Made By Many #LeanUX | @jboogie
  40. Every design is a hypothesis Don’t design things people don’t want #LeanUX | @jboogie http://deggan.blogspot.com/2011/01/three-giant-paper-airplanes-and.html
  41. Validate your hypothesis with customers Keep it light and cheap. #LeanUX | @jboogie http://www.flickr.com/photos/forakerdesign/3657336793/sizes/l/
  42. Use data to settle subjective issues A/B testing can settle these “Pepsi challenges” #LeanUX | @jboogie http://2.bp.blogspot.com/__3p5_gzemps/TLpuaIolhlI/AAAAAAAAA-o/smDfmM8xqQM/s1600/Coke-vs-Pepsi.jpg
  43. Form factor is ultimately irrelevant There are many ways to validate hypotheses
  44. Informal and quick is better than…. Delayed feedback loops
  45. It’s not “The Spec” that gives control Lead with conversation, trail with documentation #LeanUX | @jboogie http://talkingtraffic.org/wp-content/images/stack_documents.jpg
  46. This is the goal… Moving towards parallel path development and design. http://www.greatoutdoors.com/files/imagecache/display/files/images/articles/Wong%20leading%20a%20Powder%208%20win%20%20photo%20-
  47. What Lean UX is NOT #LeanUX | @jboogie
  48. Lazy. Sorry. This is not a shortcut. “…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.” -Austin Govella commenting on Whitney Hess’s “Why I Detest the Term Lean UX” http://whitneyhess.com/blog/2011/02/27/why-i-detest-the-term-lean-ux/ #LeanUX | @jboogie http://www.causticsodapodcast.com/wp-content/uploads/2010/11/lazy.jpg
  49. The only thing being removed is waste. Leave the toolbox intact. Use the tools as necessary. #LeanUX | @jboogie http://www.flickr.com/photos/mims/326748812/sizes/l/
  50. This is NOT design-by-committee! That never leads to anything pretty. #LeanUX | @jboogie http://www.flickr.com/photos/mims/326748812/sizes/l/
  51. Can I make this happen in my organization? Short answer: Yes. Long answer: Yessssssssss! #LeanUX | @jboogie
  52. You’re an in-house designer… Start small and internal. Ask for forgiveness. #LeanUX | @jboogie http://sarah.theworkexperiment.com/wp-content/uploads/2011/07/think-big-start-small1.jpg
  53. 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. #LeanUX | @jboogie
  54. Startups This is the only way to work… #LeanUX | @jboogie http://militarytobusiness.blogspot.com/2010/12/start-ups-at-hbs.html
  55. The interactive agency and services world. Tougher sell. Worth it in the end. #LeanUX | @jboogie
  56. Agencies are in the deliverables business. (Focus is on output rather than outcome) #LeanUX | @jboogie
  57. Recapping the “in-house” Lean UX process…. Remember? Just the UX process Concept Validate Prototype Test Learn Iterate Internally Externally from user behavior #LeanUX | @jboogie
  58. For services agencies it looks slightly different Give your clients the power. They like that. Validate Validate Concept w/client Iterate w/client Prototype Learn from user behavior #LeanUX | @jboogie
  59. Distributed teams do it remotely! If they’re a part of you, it’s on! If not, it ain’t bloody likely. #LeanUX | @jboogie http://farm3.static.flickr.com/2361/2076450897_be1b8ace7c.jpg
  60. Is this good for every project? Use it where it makes sense. #LeanUX | @jboogie http://manayunkdrinkspecials.com/wp-content/uploads/2009/11/45559121.jpg
  61. Functional, task-flow projects work well. There’s a clear end goal. #LeanUX | @jboogie
  62. Highly experiential marketing projects will struggle. Time to ideate and create options is essential. #LeanUX | @jboogie
  63. What about content heavy experiences? Some up front planning is necessary. #LeanUX | @jboogie
  64. Designers are used to being heroes. Lean UX is distinctly, anti-hero. #LeanUX | @jboogie http://www.abegoodman.com/Images/greatest-american-hero.jpg
  65. Lean UX brings Design Thinking to a broader audience. Which creates empathy for: - The customer - The problem space - The design discipline #LeanUX | @jboogie
  66. This is an evolution. Not a revolution. Designers must evolve to stay relevant. #LeanUX | @jboogie http://www.flickr.com/photos/freejay3/2387714157/sizes/l/
  67. @jboogie jeff@proof-nyc.com Thank you www.leanuxbook.com www.jeffgothelf.com slideshare.net/jgothelf I’m writing a book! Pre-order here

Editor's Notes

  • Gust case study – distributed teams w/devs in Vancouver, PM/UX in NYC and no collaboration going on. Just docs/emails exchanged between teams. No coding till sign off and then more negotiation.Bad communication, no shared goals, no shared language, non shared understanding…
  • Gust case study – distributed teams w/devs in Vancouver, PM/UX in NYC and no collaboration going on. Just docs/emails exchanged between teams. No coding till sign off and then more negotiation.Bad communication, no shared goals, non shared understanding…
  • When I was at my last employer, we were concerned that the company was making strategic decisions without fully considering the needs of the user. Since most of us rarely sat at that table we wanted to bring the user to the team. Initial proposals centered around persona research and creation – an activity which can cost tens of thousands of dollars and take several months.What were some other ways we could do this?The ad-hoc persona proved to be a terrific way to get the conversation started at the exec level.
  • After the exercise, which took 8 hours over two days, the team walked away with a similar POV of who they were serving with current and new services.
  • Knowing we wouldn’t be at every subsequent conversation, we wanted our work to go with the team…
  • Knowing we wouldn’t be at every subsequent conversation, we wanted our work to go with the team…
  • This is where every team starts at the beginning of every product design project.The goal is shared understanding.
  • The goal is shared understanding.
  • The goal is shared understanding.
  • The goal is shared understanding.
  • The goal is shared understanding.
  • Takes too long to get to an ideaTakes too long to get the idea validatedHow do you know it’s the right designCan’t wait to launch productEtc…
  • ×