LEAN UXFOUNDATIONSJanice FraserLean User Experience IntensiveNovember 2010janice@LUXr.co
2010 Survey of Early-Stage Companies 93% say UX is a strategic differentiator 80% spend < $25k on design before launch It’s too important to outsource. Designers are here then gone. By the time I get the work, we don’t want that thing any longer. I don’t know where to ﬁnd the right person. It’s too expensive.LEAN UX INTENSIVE, NOV 2010 JANICE@LUXR.CO
“Anyone who makes decisions about how the product should be is a designer*. “Designer is a role, not a person. Almost every developer on a team makes some decisions about how the product will be, just through the act of creating the product. “These decisions are design decisions, and when you make them, you are a designer. “For this reason, no matter what your role on a development team, an understanding of the principles of design will make you better at what you do.LEAN UX INTENSIVE, NOV 2010 Jesse Schell, The Art of Game Design, 2010 JANICE@LUXR.CO
CUSTOMER DEVELOPMENT IN ONE PAGELEAN UX INTENSIVE, NOV 2010 JANICE@LUXR.CO
How do you do good user experience work in a lean/ agile environment?LEAN UX INTENSIVE, NOV 2010 JANICE@LUXR.CO
What slows teams • Making decisions • Being in the weeds • Not making decisions • Forest/trees • Disagreements • Analysis paralysis • Negotiation • Forgetting to move on • Talking • Not seeing that you already agree • Not Listening • Not noticing that you need to • Meetings make a decision(!)LEAN UX INTENSIVE, NOV 2010 JANICE@LUXR.CO
Lean User Experience is a cross- functional, principle-driven process characterized by rituals that predispose teams to predictable, high-quality, high- velocity user experience outcomes.LEAN UX INTENSIVE, NOV 2010 JANICE@LUXR.CO
Launch ﬁxes next Make the lightest thing that’s checkable inform your thinking by talking to people start by understanding the needs of one person What are the principles? cross-functional or die check what you make as you go. ux, business, and tech. learn quickly usability testing and a/b what you think is less important than testing are the liver and what users do spleen, not the brain or the heart. test what’s testable Humans can’t predictably be right the ﬁrst time. focus on solving the right problem not build this product.LEAN UX INTENSIVE, NOV 2010 JANICE@LUXR.CO
Lean UX process Users 1. BLAH why Needs 2. BLAH 3. BLAH ple what peo how uct pro d (INSERT BUSINESS THINKING HERE) Bob can... Uses Features (CREATE SKETCHES, WIREFRAMES & PIXELS) This Week User Stories Themed Releases
Lean UX methods are Lightweight Low-Fi Lo-Tech External Face to Face Collaborative Generative and Decisive Fast Repeatable Routinized Goal Driven Outcome FocusedLEAN UX INTENSIVE, NOV 2010 JANICE@LUXR.CO
The UX ﬁeld has ABSTRACT CONCEPTSloads of methods that Pyramid Sticky Strategy strategywill work lean. Ecosystem Map(plus a few new ones that I puttogether based on lean principles.) Personas (scenarios) Design Target user 6-Up Sketching Activity Map Story Boards uses Sticky Triage Story Mapping feature planning Iteration Planning 2 or 3-Up Sketching Test Creation Wireframes Card Sorting IA, IxD, UI Black Hat Session Sketch Boards Prototyping (many kinds) Greyboxing detail design Pair Production/Design Design Bible Pattern Libraries velocity & Housecleaning cohesiveness WORKING SOFTWARELEAN UX INTENSIVE, NOV 2010 JANICE@LUXR.CO
They also havemethods for “gettingout of the building.” CUSTOMER DEVELOPMENT Listen (talk*) to people** Surveys generative Watch people use competitors Customer acceptance testing with paper prototypes Card sorting evolutionary Usability testing Usertesting.com Behavioral metrics A/B testing quantitative Heat mapping OPTIMIZATION ** WHO? People who match your design target * ABOUT WHAT? What they do, what their life is like, what they use, what their problems are, how they meet their needs now?LEAN UX INTENSIVE, NOV 2010 JANICE@LUXR.CO
Possible rituals for lean product teams Rituals should predispose respect and collaboration across disciplines, reduce defensiveness and debate, and ensure successive improvements to the product. ABSTRACT CONCEPTS First frame the question (deﬁne the problem) User need/quote as sprint name Write tests ﬁrst ideate Standup Wireframe check Pairing communicate Acceptance discipline Retrospective respect User talks and tests Redo improve Housecleaning Most important thing for the problem owner is to deﬁne WORKING SOFTWARE and own the problem.LEAN UX INTENSIVE, NOV 2010 JANICE@LUXR.CO
A particular slide catching your eye?
Clipping is a handy way to collect important slides you want to go back to later.