10/15/12&

www.ProtoShare.com& 1&

Lean&UX&

Andrew&Mo:az&

CTO&ProtoShare&

Lean&Manufacturing&C>&Lean&Startup&C>&Lean&UX&

"Lean,"&is&a&producIon&pracIce&that&considers&the&expenditure&of&resources&for&any&goal&other&than&the&creaIon&of&value&for&the&end&customer&to&be&wasteful,&and&thus&a&target&for&eliminaIon.&

& C&Wikipedia&

10/15/12&

www.ProtoShare.com& 2&

UX&is&important,&but&Agile&gives&it&less&emphasis.&

Lean&UX&makes&UX&the&heart&of&the&development&process&

UX&is&the&glue.&&Takes&BA/Business&requirements,&user&input,&developer&concerns,&makes&them&concrete,&&creates&the&shared&understanding&between&all&stakeholders.&

Lean&UX&in&a&Nutshell&

•  Every&design&is&a&hypothesis&and&must&be&tested.&&

•  The&focus&on&a&giant&spec&doc&is&replaced&by&a&focus&on&a&shared&understanding.&

10/15/12&

www.ProtoShare.com& 3&

How&we&do&it.&

•  Prototype&the&Backlog&•  Backlog&consists&of&defects&and&User&Stories&•  Sketch,&Prototype,&Review&and&Iterate&as&you&decompose&the&

story&into&doable&chunks.&

•  Get&as&much&of&the&team&reviewing&prototypes&as&you&can.&&Create&the&shared&understanding.&

•  Document&what&you&need&to&to&get&your&point&across.&

•  Get&end&users&involved&to&validate&your&hypotheses.&•  Prototypes&are&an&important&part&(&but&not&the&only&part&)&of&

the&documentaIon&

An&Example:&&

Our&ideas&are&usually&first&expressed&as&User&Stories&

10/15/12&

www.ProtoShare.com& 4&

User&Story:&US820&

User&Stories&

•  Verbal,&userCcentered,&abstract.&(What&and&why)&&

•  Audience:&&People&who&have&inImate&knowledge&of&product.&&

•  Drawbacks:&&Different&people&can&have&radically&different&understanding.&&

•  User&stories&are&explored,&supplemented,&decomposed&and&validated&using&visual&prototypes&of&varying&levels&of&fidelity&

10/15/12&

www.ProtoShare.com& 5&

Prototypes&

Start&ValidaIng&Early&with&Prototypes&

Internal(Valida,on(•  Do&this&all&the&Ime&

•  Train&yourself&to&share&early&•  Regular&Reviews&•  Part&of&cadence&

External(Valida,on(•  FormaIve&User&TesIng&

–  Small&number&(&2&to&3&)&–  Informal&–  FaceCtoCface&or&monitored&

•  ValidaIve&User&TesIng&–  Larger&number&–  AnalyIcs&–  More&formal&–  Watching&a&small&subset&of&

users&sIll&useful&–  ImpracIcal&to&watch&all&users.&

10/15/12&

www.ProtoShare.com& 6&

Prototypes&

•  Iterate,&Iterate,&Iterate&&

•  Visual,&experienIal,&concrete&(&What&and&how&)&&

•  User&TesIng:&Do&this&regularly,&don’t&wait&unIl&you’re&ready.&&

•  Prototypes&start&low&fidelity,&and&evolve&to&as&high&fidelity&as&we&need&them&to&be.&&

•  Regular&review&of&prototypes&by&team&members&creates&a&shared&understanding&&

•  When&are&you&done&prototyping?&&When&developers&have&a&reasonable&amount&of&certainty&that&they&can&build&what’s&being&proposed.&

Working&Code&

10/15/12&

www.ProtoShare.com& 7&

IteraIng&in&code&

•  Just&because&you’ve&started&engineering,&doesn’t&mean&you’re&done&validaIng.&

•  ConInue&Internal&and&External&ValidaIon&•  ValidaIve&User&TesIng&&