The Lean UX Cycle
Ideas
Build
Product
Measure
Data
Learn
The Lean UX Cycle
State your desired outcomes
Ideas
Build
Product
Measure
Data
Learn
The Lean UX Cycle
State your desired outcomes
Declare your assumptions
Ideas
Build
Product
Measure
Data
Learn
The Lean UX Cycle
State your desired outcomes
Declare your assumptions
Hypothesize: write the test first
Ideas
Build
Product
Measure
Data
Learn
The Lean UX Cycle
State your desired outcomes
Declare your assumptions
Hypothesize: write the test first
Design an Experiment
Ideas
Build
Product
Measure
Data
Learn
The Lean UX Cycle
State your desired outcomes
Declare your assumptions
Hypothesize: write the test first
Design an Experiment
Make an MVP
Ideas
Build
Product
Measure
Data
Learn
The Lean UX Cycle
State your desired outcomes
Declare your assumptions
Hypothesize: write the test first
Design an Experiment
Make an MVP
Get out of the building
Ideas
Build
Product
Measure
Data
Learn
The Lean UX Cycle
State your desired outcomes
Declare your assumptions
Hypothesize: write the test first
Design an Experiment
Make an MVP
Get out of the building
Team synthesis
Ideas
Build
Product
Measure
Data
Learn
The Lean UX Cycle
State your desired outcomes
Declare your assumptions
Hypothesize: write the test first
Design an Experiment
Make an MVP
Get out of the building
Team synthesis
Repeat
Ideas
Build
Product
Measure
Data
Learn
Lean UX Characteristics
Small, x-functional teams
Small-batch flow
A bias towards making
Ideas
Build
Product
Measure
Data
Learn
Lean UX Characteristics
Small, x-functional teams
Small-batch flow
A bias towards making
Continuous Learning
Ideas
Build
Product
Measure
Data
Learn
Lean UX Characteristics
Small, x-functional teams
Small-batch flow
A bias towards making
Continuous Learning
A focus on outcomes
Ideas
Build
Product
Measure
Data
Learn
Reduce Inventory, Risk and Waste
Make a
design
decision
Get feedback
from market
Concept credit: @clevergirl
Reduce Inventory, Risk and Waste
This is
going to
be BIG!
Make a
design
decision
Get feedback
from market
Concept credit: @clevergirl
Reduce Inventory, Risk and Waste
Nope.
This is
going to
be BIG!
Make a
design
decision
Get feedback
from market
Concept credit: @clevergirl
Reduce Inventory, Risk and Waste
Nope.
This is
going to
be BIG!
Make a
design
decision
MONTHS Get feedback
from market
Concept credit: @clevergirl
Reduce Inventory, Risk and Waste
Nope.
This is
going to
be BIG!
Make a
design
decision
MONTHS
HOURS
Get feedback
from market
Concept credit: @clevergirl
A system built on continuous learning
18
Risk
Diagram concept: @clevergirl
Learning!
360° ASSUMPTIONS
Tech-enthusiast
consumers
Need to control web
browser from couch
Internet mouse!
Traditional retail
channel sales
Logitech,
Microsoft
More buttons than
anyone else!
Able to surf the
internet from the
couch
Computer stores,
magazine
advertising
Purchasers of
Gateway
Convergence TV
Technique: Write the test first
We believe ______.
We’ll know this is true when we see
§ qualitative outcome and/or
§ quantitative outcome
§ That improves this KPI.
Hypothesis statement
We believe that
[doing this]
for [these people]
will achieve [this outcome].
We’ll know this is true when we see
[this market feedback].
Hypothesis statement
We believe that
creating Internet Mouse
for people who own “Convergence” TVs
will get us into the internet business.
We’ll know this is true when we see
pre-order commitments from big-box
retailers.
Case Study: Social Media Benchmarking
Observed: Small business owners want to use
social media for marketing but don’t know how.
Hypothesis: They would pay for a service that
provides benchmarking data from their peers.
33
Hypothesis statement
We believe that creating
a social-media benchmarking platform
for small business owners
will encourage small business owners to
participate in our programs.
We’ll know this is true when we see
a willingness to pay for the service.
Output, Outcome, Impact
§ Output: the software we build. The materials we produce.
Easy to trace. Example: A new log-in page.
Output, Outcome, Impact
§ Output: the software we build. The materials we produce.
Easy to trace. Example: A new log-in page.
§ Outcome: the change in the world after we deliver output.
Harder to trace. Example: increase user log-in rate.
Output, Outcome, Impact
§ Output: the software we build. The materials we produce.
Easy to trace. Example: A new log-in page.
§ Outcome: the change in the world after we deliver output.
Harder to trace. Example: increase user log-in rate.
§ Impact: the change we see over time.
Very hard to trace. Example: Our service is profitable.
56
Business model validation
Product validation
Small team
Culture / Infrastructure to support continuous learning
Stakeholders
Small-chunk, outcome-based, predictable funding
$$$
AGENDA
1. CONTINUOUS LEARNING
2. ASSUMPTIONS AND HYPOTHESES
3. TEST HYPOTHESES BY MAKING
4. MANAGE OUTCOMES
5. A NEW ORGANIZATION
57