32
LEAN UX the state of affairs Taco Ekkel / VP Product Design at ProQuest / @tacoe / #TWAB2012 (Notes here) Show of hands: who here uses Lean UX methodologies in their daily practice?

Lean UX - State of Affairs

Embed Size (px)

DESCRIPTION

Going on the question, "If Lean UX is so fabulous why do so few people say they use it?", this presentation shares insights from interviews with a number of agile/lean UX practices to find successful lean UX patterns, and shows how these patterns can help you get started.

Citation preview

Page 1: Lean UX - State of Affairs

LEAN UXthe state of affairs

Taco Ekkel / VP Product Design at ProQuest / @tacoe / #TWAB2012

(Notes here) Show of hands: who here uses Lean UX methodologies in their daily practice?

Page 2: Lean UX - State of Affairs

http://www.wisegeek.com/what-is-lean-manufacturing.htmLean: Ford — Toyota — Toyotism — waste reduction Image http://www.wisegeek.com/what-is-lean-manufacturing.htm

Page 3: Lean UX - State of Affairs

90% OF NEW PRODUCTS

In Software, different origin: products failed a lot. Not because the thing was built wrong, but because the wrong thing was built.

Page 4: Lean UX - State of Affairs

CUSTOMER DEVELOPMENT

Steve Blank came along and fixed that by switching product development to customer development. Validated learning.

Page 5: Lean UX - State of Affairs

+ =Agile DevLean UX

FOSS

Note that the left part (the book that introduces customer development) is the important part. This middle bit is only tools.

Page 6: Lean UX - State of Affairs

Agile UX

Ability to respond quickly

Collaborate

Build requirements quickly

Central concept: lean ux builds on agile ux (i.e., not an either/or). The confusion between the two stems from the fact that both focus on reduction of deliverables.

Page 7: Lean UX - State of Affairs

Lean UX

Know what to respond to

Learn

Test hypotheses quickly

Agile UX

Ability to respond quickly

Collaborate

Build requirements quickly

Central concept: lean ux builds on agile ux (i.e., not an either/or). The confusion between the two stems from the fact that both focus on reduction of deliverables.

Page 8: Lean UX - State of Affairs

Lean UX

Know what to respond to

Learn

Test hypotheses quickly

Agile UX

Ability to respond quickly

Collaborate

Build requirements quickly

Waste reduction by minimizing deliverables

Communication over documentation

Central concept: lean ux builds on agile ux (i.e., not an either/or). The confusion between the two stems from the fact that both focus on reduction of deliverables.

Page 9: Lean UX - State of Affairs

Agile UX + Lean UX

Traditional UX

Page 10: Lean UX - State of Affairs

1. Lean UX 2. ????3. Profit!!

Page 11: Lean UX - State of Affairs

(wake-up call)

If it were so easy or fantastic, everyone here would’ve raised their hand at the beginningImage http://www.forkparty.com/11785/you-requested-a-wake-up-call-video

Page 12: Lean UX - State of Affairs

1. Lean UX 2. ????3. Profit!!

Page 13: Lean UX - State of Affairs

Questions

• If Lean UX is so fabulous why doesn’t everyone use it?• What are practical things you can do to get started with it?

Page 14: Lean UX - State of Affairs

Approach

• Qualitative exploratory research • interviews with teams of designers/developers/product people• startups, agencies, product teams in larger companies

• Find recurring lean patterns in daily practices• Learning over building• Waste reduction• Speed increase

maker teams: where design/development/product people bump into eachother

Page 15: Lean UX - State of Affairs
Page 16: Lean UX - State of Affairs

PATTERNS

Page 17: Lean UX - State of Affairs

PATTERN Agile: Been There, Done That

• Lean-using teams had fully mastered agile• Manifesto flavor, not “agifall” flavor

• Signs of having agile mastered• Little formality, lots of personal understanding of the problem space• Emergent planning and detailing of requirements/hypotheses• A feeling that fixed sprint rhythm constrains speed and flexibility• Experimentation with lighter-weight forms (like applying Kanban)

Manifesto flavor: people & communication focused. ‘Agifall’ is when everyone does the motions of scrum (standup, etc) but we still require waterfall-like deliverables and steps

Page 18: Lean UX - State of Affairs

RUP50,000,000 rules

Agile (Scrum)10 rules

Kanban3 rules

NOTE The less rules, the more awesome your team needs to be. I.e., you don’t start on the right sideImage http://jkneilson.wordpress.com

Page 19: Lean UX - State of Affairs

PATTERN Minimum Viable Anything

• Not just Minimum Viable Product, but also• Minimum Viable Personality• Minimum Viable Documentation• Minimum Viable API

• Really useful as ‘understanding device’ for stakeholders

Makes it easier to prevent stakeholders to throw in too many requirements

Page 20: Lean UX - State of Affairs

PATTERN Learning-focused Measuring

• Measure things that’ll help you learn• Not useful: vanity metrics, visitor count, arrival rate• Useful: next/previous action flows, funnels

• Not a replacement for getting out of the building

Page 21: Lean UX - State of Affairs

PATTERN Lean Experiments

problem,opportunity

brainstorm select

ideaidea idea

idea

idea

ideaidea

idea idea

functionalities A, B, C

design / builddeploy

measuretest

Keep A, CLose B

idea

start

donehypotheses A, B, C

Timeline is short: One sprint. No A/B needed for many of these!

Page 22: Lean UX - State of Affairs

PATTERN The Design Guardian

I’LL SAVE THIS PRODUCT FROM BECOMING AN INCOHERENT MESS

• With “constant change”, coherence needs work• Can be anyone — IxD, VD, PO, etc

• But someone has to be this• Usually, designer works a sprint ahead for this

• “design lead sprint” not necessarily a bad thing

Page 23: Lean UX - State of Affairs

PATTERN Physical Proximity

• Developer & UI Designer: Closer = Better• Different physical location, email: bad• Different locations/rooms, Skype: okay• Sitting next to eachother looking at same screen: fantastic• One and the same person: nirvana

Page 24: Lean UX - State of Affairs

PATTERN Front-End Designer

• Prototype interaction in browser• not often reused in production code

• Labels still in flux• Interaction Engineer, UI Engineer, Front-End Designer, Design Technologist

• Often takes the role of design guardian• Not necessarily formally trained either way

DesignersCoders

who know CodeDesign

If you’re considering a career switch... consider this

Page 25: Lean UX - State of Affairs

PATTERN Formal Wireframing On The Way Out

AxureOmnigraffle

Visio

ideation, layout, interaction

specification

ideation, layout

layout, interaction

browser-based prototypes in actual code

lower-fi collaborative sketching

• Good riddance. Wireframes did a bunch of things poorly• Since only the IxD can wireframe, slow ideation process• Since wireframes suck at interactivity, bad way to specify interaction

• Design in browser — actually code. Usually not used in prod code. Most people just start with jquery or something

Page 26: Lean UX - State of Affairs

The Hammer-Nail Issue

“With browser-based design, everything becomes boxes”

Photoshop

“Everything looks like Bootstrap”

Browser prototyping

“Pretty but dead pictures”

Page 27: Lean UX - State of Affairs

PATTERN Product Owner In The Trenches

• “If the PO isn’t passionate about the user experience, forget about it”• Signs of a PO in the trenches

• PO does a lot of sketching • Nitpicky about UI details• Leaning on a design guardian (or being it)• Getting pulled in for UI related discussions whenever possible

Page 28: Lean UX - State of Affairs

PATTERN Terminology Confusion

• Some teams using Lean UX patterns don’t self-identify as such• Lean, Agile etc often confused

• No one gives a damn what it’s called, as long as it works

Not giving a damn what it’s called is a good thing!

Page 29: Lean UX - State of Affairs

ANSWERS

Page 30: Lean UX - State of Affairs

Using patterns to get started with Lean UX

• Q: What practical starting points do these patterns provide?

• Get agile UX working first!• Have a design guardian who ensures consistency over time• Design-ahead is not a horrible thing (within limits)• Get designers and developers really close to eachother• If your PO is not passionately in the trenches, buy a new one • Start replacing “requirements” stories with “hypothesis” stories• Run lean experiments

Page 31: Lean UX - State of Affairs

The starting question

• Q: “If Lean UX is so fabulous why doesn’t everyone use it?”

• Still struggling getting Agile UX to work • Lack of awareness, terminology confusion

Learn quicklyBuild quickly

Agile UX Lean UX

Page 32: Lean UX - State of Affairs

THANKSquestions?

Taco Ekkel / VP Product Design at ProQuest / @tacoe / #TWAB2012