SlideShare verwendet Cookies, um die Funktionalität und Leistungsfähigkeit der Webseite zu verbessern und Ihnen relevante Werbung bereitzustellen. Wenn Sie diese Webseite weiter besuchen, erklären Sie sich mit der Verwendung von Cookies auf dieser Seite einverstanden. Lesen Sie bitte unsere Nutzervereinbarung und die Datenschutzrichtlinie.
SlideShare verwendet Cookies, um die Funktionalität und Leistungsfähigkeit der Webseite zu verbessern und Ihnen relevante Werbung bereitzustellen. Wenn Sie diese Webseite weiter besuchen, erklären Sie sich mit der Verwendung von Cookies auf dieser Seite einverstanden. Lesen Sie bitte unsere unsere Datenschutzrichtlinie und die Nutzervereinbarung.
Inspired by Lean and Agiledevelopment theories, LeanUX is the practice of bringingthe true nature of our work tolight faster, with lessemphasis on deliverables andgreater focus on the actualexperience being designed.
Design Agile Lean Thinking Development Startuplean UX foundations
An approach for building companies that are creating new product and services in situation of extreme uncertainty. The approach advocates creating of rapid prototypes that test market assumptions and uses customer feedback in an eﬀort to evolve design faster and reduce waste. Eric Rieslean startup
What are we making ?Are we making the right thing ? How do we make it ?why lean UX is different ?
Generative Research Ideation Mental models Think behavior models Test Result Competitive Analysis Prototype Wireframes Value Prop Reduce Landing Page Hypotheses Cycle Time Comps Deployed Code Check Make A/B Testing Site Analytics Usability Testing Funnels Iterative Development Sign-Upslean UX cycle
Identify assumptions you have about your customers and create a clear picture of their needs and goals.Think - envision your customer / users
Prepare for and run customer interviews that will help you validate your customer assumptionsThink - conduct quality interviews
Debrief from customer interviews, sort the insights you’ve gleaned and validate your persona.Think - learn from customer development
Start with Assumptions instead of RequirementsThink - declare assumptions & hypothesis
The current goal of the product / system [Our service/product] was designed to achieve [these goals]. We have The problem the observed that the product/service isn’t meeting [these goals], which is business causing [this adverse effect] to our stakeholders wants business. How might we improve [service/product] so that our customer to addressed are more successful based on [these measurable criteria] ? An explicit request for improvement that doesn’t dictate a speciﬁc solutionThink - problem statement
We believe [this statement is true]. We will know we’re [right/wrong] when we see the following feedback from the market : [Qualitative feedback] and /or [quantitative feedback] and/or [key performance indicator change] More granular description of our assumptions that We believe that [doing this/ building target speciﬁc this feature/creating this areas of our experience]for [these people/ personas] will achieve [this outcome] product for We will know this is true when we see [this market feedback, quantitative experimentation measure or qualitative insight] .Think - hypothesis statement
Get set to deliver on the value proposition for your product by mapping out the features of the MVP. The emphasis is focusing, and ﬁguring out what not to build at this time.Make - identify MVP
“That version of a new product that will allow a team to collect the maximum amount of validated learning about customers with the least eﬀort.” -Eric Ries The goal of an MVP is get to a pivot in as short amount of time as possible.MVP
Just making one big pain point for users go away can be your entire MVP Painkiller manually rename or move ﬁles This can be a great for products or services that you will want users to Fast Money pay for in some way. If you are providing some type of expert advice, MVP could be Email Newsletter. Manually simulate features that eventually will be accomplished by the system Turk It Dating - Matchmaking Sites with complex algorithm This is a great strategy for a product where a core part is some Go Ugly & Early engineering special sauce, or in which a key product risk is technological connect with parts warehouses all over the globe Rather than try to build the actual product, we instead imagine that the Fake it till you make it product already has been built and create the marketing page for selling itMVP design strategies
• Aardvark, a company subsequently acquired by Google, developed a social search engine. The product enables • Skinned Wordpress blog and • Before star=ng signiﬁcant technical users to ask ques=ons, mainly posted daily development, made a 3min video to subjec=ve, that are then distributed to demonstrate how the Dropbox is the social graph for users for answers. • Used FileMaker to create PDF meant to work, targe=ng at early coupons and emailed adopters Build a series of prototypes for ways customers could interact with the • Eﬀec=vely validated the demand • Call to ac=on was to sign up for beta virtual assistant and get their ques=ons for such service without wai=ng list answered, measuring their developing a seamless system engagement • Eﬀec=vely validated its assump=on that customers wanted the product • Once Aardvark (the sixth prototype) that Dropbox was developing was chosen, con=nued reﬁnement with humans replica=ng pieces of the backend as much as possible(Wizard of Oz tes=ng technique.)to avoid premature and unnecessary technical developmentMVP examples
User Acquisition User Engagement User MonetizationMake - deﬁne measurable metrics
Validated Learnings / Meaningful Feedback Lean UX recommend live data prototype but you can choose level of MVP Whiteboard Detail Interactive Live Data prototype based on Sketching Wireframes Prototype Prototypes •Who will be interacting with it Whiteboard •What you hope to learn Keynote Axuare XCode •How much time you have Level of Fidelity to create itMake - prototype / deploy
Launch Live Prototype Run Demo Collaborative Research Continuous ResearchCheck - run experiment
Images Used http://500px.com/photo/7583468 http://ethosworld.com/library/library6.jpg http://i.imgur.com/ysoCR.jpg http://www.coroﬂot.com/helenfurber/Other-Portfolio-work http://lssacademy.com/wp-content/uploads/2007/02/gavel.jpg http://www.ﬂagship-housing.co.uk/mediaFiles/images/ img94joktmu72911.jpg http://www.lowdensitylifestyle.com/media/uploads/2009/09/ sands-of-time1.jpg http://www.flickr.com/photos/villorejo/8274195689/lightbox/ http://www.flickr.com/photos/ 76245693@N04/6969367298/lightbox/ http://joshlinkner.com/images/2012/05/SAN.jpg Blogs Referred http://www.andersramsay.com/2012/04/24/agile-ux-vs-lean-ux/ http://www.custdevframework.com/p/minimum-viable- product.html http://theleanstartup.com/ http://blog.bullethq.com/lean-startup-zappos-how-zappos- validated-their-business-model-with-lean/credits & references http://www.linkedin.com/in/ramakantgAll images used are found on the internet and believed to be in the public domain. In the event that there is still a problem or error with copyrighted material, the break of the copyright isunintentional and non-commercial and the material will be removed upon request.