Fail Fast, Learn Fast, Move Fast: My UX journey to move faster
•
83 likes•52,086 views
We've all heard about the Lean Startup, and now Lean UX. This is a intro into how I've been using these methods to speed up the UX process, and work better within product teams.
Fail Fast, Learn Fast, Move Fast: My UX journey to move faster
- 1. Fail FAst Learn Fast Move Fast My UX journey to move faster @jeremyjohnson
- 3. @jeremyjohnson #leanux #DDSum12
- 7. un peu UX 101
- 8. UX 101 we make things for http://500px.com/jeremyjohnson/sets/london_2012
- 9. UX 101 we make things for http://500px.com/jeremyjohnson/sets/buenos_aires_2012
- 10. UX 101 We work in ecosystems http://500px.com/jeremyjohnson/sets/london_2012
- 11. UX 101 we think visually http://500px.com/jeremyjohnson/sets/buenos_aires_2012
- 12. UX 101 We learn through observation http://500px.com/jeremyjohnson/sets/london_2012
- 13. UX 101 we’re curious http://500px.com/jeremyjohnson/sets/london_2012
- 14. UX 101
- 15. agency/consultant UX startup large org
- 16. startup Where the core component...
- 17. ...of Lean Startup methodology is the build-measure-learn feedback loop.
- 18. experiment via mvp iterative prototyping (keep it simple) UX value customer shipping / launching feedback often
- 19. Agency making deliverables is your job
- 21. consultant UX http://www.flickr.com/photos/jeroenbennink/2355768494/sizes/l/in/photostream/
- 23. large org http://www.flickr.com/photos/23671396@N06/4445276713/
- 25. large org
- 26. how i learned to stop worrying about being in a large organization, and just move faster.
- 27. Hard.
- 28. Jim, Social Media “Expert” http://www.webwanderers.org/05_industry/mining/
- 29. I got 99 problems
- 30. Let’s fix it.
- 31. development UX Product development business
- 32. development UX Product development business
- 33. I’ve heard Team is too small, must be shared Team doesn't work directly with development Team doesn’t work directly with product/business
- 34. Big hairy problem #1
- 35. Selling UX
- 36. How many people have true UX buy in at the c-level?
- 38. ABEX (always be evangelizing ux)
- 39. Big hairy problem #2
- 40. embracing and Agile
- 41. “Rather than focus on artifacts, we focus on prototypes and validating those prototypes in Discovery, with the added benefit that the prototype serves as the spec for Delivery.” http://www.svproduct.com/dual-track-scrum/
- 42. Documentation = bad rough, quick, iterative, prototype = good
- 43. Getting closer, quicker to the actual experience
- 44. http://uxdesign.smashingmagazine.com/2011/03/07/lean-ux-getting-out-of-the-deliverables-business/
- 45. http://uxdesign.smashingmagazine.com/2011/03/07/lean-ux-getting-out-of-the-deliverables-business/
- 46. development UX Product development business
- 47. UX development Product development business
- 48. One new interesting challenge
- 49. mobile UX Designer me seo/sem UX Designer homepage UX Designer shopping checkout UX Designer UX Designer
- 50. New ways of working for designers will, at first, be uncomfortable. For many design managers, assigning their staff to particular teams brings a new challenge. No longer does the design manager dole out specific work to each person on the team. Instead, the designer’s daily agenda is driven by the prioritized backlog of the scrum team. http://uxdesign.smashingmagazine.com/2011/10/18/how-to-build-an-agile-ux-team-culture/
- 51. MBWA
- 53. MBWA Management By Walking Around http://en.wikipedia.org/wiki/Management_by_wandering_around http://www.flickr.com/photos/zubeirtai/7747819548/
- 54. (not new) 1. Drive: UX practitioners are part of the customer or product owner team 2. Research, model, and design up front - but only just enough 3. Chunk your design work 4. Use parallel track development to work ahead, and follow behind 5. Buy design time with complex engineering stories 6.Cultivate a user validation group for use for continuous user validation 7. Schedule continuous user research in a separate track from development 8. Leverage user time for multiple activities 9.Use RITE to iterate UI before development 10.Prototype in low fidelity 11.Treat prototype as specification 12.Become a design facilitator - 2008 http://agileproductdesign.com/blog/emerging_best_agile_ux_practice.html
- 55. walls = slow http://www.flickr.com/photos/yewenyi/360374054/sizes/o/in/photostream/
- 56. agile
- 58. agile / lean UX everyone is involved!
- 60. agile, better than waterfall
- 61. agile, shows value faster
- 62. agile, can work well with UX
- 63. agile, makes better software
- 65. ****
- 67. business valuable Usable UX Enjoyable Wonder twins
- 68. + UX Business
- 69. determine value, create experience, repeat
- 70. how
- 71. “We gathered our designers, our product folks and our engineers and took over a few conference rooms and began to operate like a startup. Design was done on whiteboards and coded in real time. Usability tests were weekly so the pace was fast and furious. But we were able to try dozens of experiences across desktop, tablet and mobile in the time that would have taken years at PayPal before. Build/Test/Learn became our mantra.” - http://looksgoodworkswell.blogspot.com/2012/09/why-you-should-work-with-me-at-paypal.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+LooksGoodWorksWell+%28Looks+Good+Works+Well%29
- 72. Build/Test/Learn
- 75. - problem - Can’t get started?
- 76. “You – everyone in fact – have all it takes to be a brilliant designer, creator, or author. All that’s holding you back is the lizard. It’s that little voice in the back of your head, the “but” or the “what if” that speaks up at the crucial moment and defeats the joy and insight you brought to the project in the first place. It’s the lizard that ruins your career, stunts your projects, and hinders your organization.” – Seth Godin (in The Truth About Shipping) http://gloriamarie.com/stay-focused-and-keep-shipping
- 77. Ship often. Ship lousy stuff, but ship. Ship constantly. http://99u.com/tips/6249/Seth-Godin-The-Truth-About-Shipping
- 78. - problem - Find it hard to strip out what’s not valuable? Spend too much time planning? DOn’t talk with your customers?
- 80. “The timing of long- range plans is screwed up too. You have the most information when you’re doing something, not before you’ve done it. Yet when do you write a plan? Usually it’s before you’ve even begun. That’s the worst time to make a big decision.” http://37signals.com/rework
- 81. - problem - Large team
- 82. Keep your team small. Smaller than that. No team at all if you can help it. http://99u.com/tips/6249/Seth-Godin-The-Truth-About-Shipping
- 83. A throwback to their days with Jeff Bezos at Amazon, projects are assigned to "two pizza teams," groups of engineers small enough for them to be fed on two large pies. "We want the team to be flat and allow everyone to communicate with each other," Rajaraman says. http://www.fastcompany.com/1811934/walmartlabs-brings-two-pizza-team-startup-culture-walmart-empire
- 85. - problem - Try to jam too much into a product? Only launch x times a year? Looking for perfection?
- 86. “Great companies focus on their users and ship great products.” http://www.aaronklein.com/2012/02/why-facebook-is-worth-100-billion/
- 89. “real artist ship” - steve jobs http://gloriamarie.com/stay-focused-and-keep-shipping
- 90. - problem - It’s going to cost too much to try that out. How do we know our customers will want this?
- 91. The Wizard Of Oz Techniques For Social Prototyping – You don’t need to build everything at first. You can be the man behind the curtain. Krieger says him and Systrom tested an early version of a feature which would notify you when friends joined the service. Instead of building it out, they manually sent people notifications “like a human bot” saying ‘your friend has joined.’ It turned - Mike Krieger, Instagram’s founder out not to be useful. “We wrote zero lines of Python, so we had zero lines to throw away.” http://techcrunch.com/2012/11/30/instagram-co-founder-mike-kriegers-8-principles-for-building-products-people-want/
- 93. 404 testing W FEAT URE X NE
- 94. Just some of the issues around software development
- 97. #LeanStartup
- 99. UX is a integral part of product development
- 100. UX is a integral part of product development http://www.flickr.com/photos/51838075@N04/6061253450/
- 101. Here’s where I saw speed.
- 102. product team 101 the core team product owner UX Dev
- 103. no, really 1x full time
- 104. core team 1x product owner 1x UX 1x Dev
- 105. mobile core team 5x UX seo/sem core team homepage core team shopping checkout core team core team
- 106. product owner This guy is the boss
- 107. product owner ux designer
- 108. Why? He/she gets fired. He/she need to meet numbers.
- 109. product owner UX core team Dev ideas
- 110. ideas ideas ideas ideas id ideas ideas ideas ideas id ideas ideas ideas ideas id Idea or discovery backlog ideas ideas ideas ideas id ideas ideas ideas ideas id ideas ideas ideas ideas id
- 111. The Discovery track is all about quickly generating validated product backlog items, and the Delivery track is all about generating releasable software. - marty cagan http://www.svproduct.com/dual-track-scrum/
- 112. ideas ideas ideas ideas id ideas ideas ideas ideas id ideas ideas ideas ideas id ideas ideas ideas ideas id ideas ideas ideas ideas id ideas ideas ideas ideas id
- 114. prototype
- 115. fast rough keep moving
- 116. test rough prototypes (usually built within a week or less)
- 117. (literally 100s) http://looksgoodworkswell.blogspot.com/2012/11/list-of-mockupprototyping-tools.html http://www.adaptivepath.com/ideas/rapid-prototyping-tools#thelist
- 118. 9:30am 10:30am 11:30am lab setting - 6 participants 1:30pm 2:30pm 3:30pm
- 120. ideas ideas ideas ideas id ideas ideas ideas ideas id ideas ideas ideas ideas id ideas ideas ideas ideas id ideas ideas ideas ideas id ideas ideas ideas ideas id
- 121. the core team Core team makes decisions Done!
- 122. ...it is collaborative – the product manager, designer and lead engineer are working together, side- by-side, to create and validate backlog items. - marty cagan http://www.svproduct.com/dual-track-scrum/
- 123. failed usability failed to understand failed to find value ideas ideas id
- 124. refine retest ideas
- 125. ideas ideas Ready for development
- 126. s ea ideas id What’s your kill rate? Ship that bad boy!
- 127. Did I mention this happens within a week? (or less)
- 128. Get moving!
- 129. discovery backlog Iteration Iteration Iteration Iteration design discovery discovery discovery discovery build Implement Implement Implement Implement http://www.sebastiangreger.net/writings/concept-design-in-agile-environment/
- 133. #2 one ux designer per team
- 134. #3 rough, fast, iterative prototyping
- 135. #4 Getting in front of customers weekly
- 136. #5 build/test/learn
- 137. in no time at all, you too can be a... lean, agile, prototyping, shipping, ux design master.
- 139. sh ere thanks! lide S @jeremyjohnson www.jeremyjohnsononline.com