The Lean Startup approach is becoming increasingly popular among companies of all sizes and organizations of all kinds. There is a lot of buzz words thrown around and the meaning gets muddled, but at it’s core, the Lean Startup approach is a way to apply the scientific method across business and product development.
It also turns out that the Lean Startup framework calls for very budget friendly UX-friendly processes, such as Build Measure Learn cycles, in which you collect small amounts of iterative feedback and focusing on building a Minimal Viable Product (MVP) required for doing so. While Lean Startup isn’t specifically for UXers, it’s a great framework to incorporate UX research early and often across the whole team, regardless of whether you’re in a true startup, a massive organization, a nonprofit, or anywhere in between.
Join this session to get:
An overview of the Lean Startup approach
Description of the Build Measure Learn framework
Discussion of different types of MVPs
Steps for successful implementation of lean expreiments, including:
Start with an observed problem
Write an effective hypothesis
Craft your experiment
Collaboratively generate MVP
Analyze data and incorporate
2. Using Lean Startup Principles
Outside of a Startup
@MandaLaceyS | #UXNZ 2017
@MandaLaceyS | #UXNZ2017
3. What is The Lean Startup,
again?
@MandaLaceyS | #UXNZ2017
4. Lean Startup
A method to develop new businesses
and products that addresses
uncertainty and risk
through cycles of rapid
experimentation.
@MandaLaceyS | #UXNZ2017
31. answer
Actionable MetricsVanity Metrics*
Anything that looks good
but doesn’t help you
make a decision
Examples:
• Facebook likes
• Pageviews
• Event attendees
Metrics that help you
decide whether you’re
succeeding or not
Examples:
• Revenue per customer
• Retention rate
• Customer source
@MandaLaceyS | #UXNZ2017
52. answer
Actionable MetricsVanity Metrics*
Anything that looks good
but doesn’t help you
make a decision
Examples:
• Facebook likes
• Pageviews
• Event attendees
Tied to specific,
repeatable tasks and
help you decide whether
you’re succeeding or not
Examples:
• Revenue per customer
• Retention rate
• Customer source
@MandaLaceyS | #UXNZ2017
56. @MandaLaceyS | #UXNZ2017
1. Add frosting
2. Change to vanilla frosting
3. Add sprinkles
4. Change to vanilla cake
5. Improve the recipe.
These are all pivots:
70. Context of use
Patterns of interaction
Interruptions
Workarounds
Moments of frustration and delight
Transitions
@MandaLaceyS | #UXNZ2017
Pay attention to:
75. @MandaLaceyS | #UXNZ2017
@MandaLaceyS | #UXNZ2017
Insights from 1 round of research do not a
sustainable business build.
Now you have a list of much better
informed assumptions.
Keep in mind.
76. 2. List and prioritize assumptions
@MandaLaceyS | #UXNZ2017
77. @MandaLaceyS | #UXNZ2017
Assumptions come in three flavors
is this thing viable?
is this thing feasible?
is this thing desirable?
@MandaLaceyS | #UXNZ2017
78. Desirability
assumption
prompts (Design)
Who is your target audience?
_________________________
_________________________
What problem are they trying to
solve? ____________________
__________________________
How do they solve that now?
_________________________
_________________________
What are the obstacles to solving
that problem with current solution?
___________________________
___________________________
What outcome are they looking
for? ______________________
__________________________
What will make users switch from
their current solution?
__________________________
__________________________
Viability
assumption
prompts (Product)
How will you generate revenue?
___________________________
___________________________
Who are your primary
competitors? ________________
___________________________
What advantages would we have
to any competitors?
__________________________
How will you acquire new
customers? ________________
___________________________
How often will they come back?
__________________________
___________________________
Why will users come back?
___________________________
___________________________
Why will users refer us to others?
____________________________
____________________________
How does this solution support
company vision?_____________
____________________________
Feasibility
assumption
prompts
(Engineering)
What are the biggest engineering
or tech challenges?
_____________________________
_ __________________________
What are the legal or regulatory
risks? ______________________
___________________________
What are the internal governance
or policy hurdles?
___________________________
___________________________
Why will leadership teams
support this? ________________
___________________________
Where does your funding come
from? _____________________
___________________________
Adapted from David Bland, Precoil
@MandaLaceyS | #UXNZ2017
81. Scenario
@MandaLaceyS | #UXNZ2017
*You’re trying to create a new application to help
busy parents plan meals and you’ve just interviewed
a dozen parents who were out grocery shopping
with their kids. .
82. Desirability
assumption
prompts (Design)
Who is your target audience?
_________________________
_________________________
What problem are they trying to
solve? ____________________
__________________________
How do they solve that now?
_________________________
_________________________
What are the obstacles to solving
that problem with current solution?
___________________________
___________________________
What outcome are they looking
for? ______________________
__________________________
What will make users switch from
their current solution?
__________________________
__________________________
Viability
assumption
prompts (Product)
How will you generate revenue?
___________________________
___________________________
Who are your primary
competitors? ________________
___________________________
What advantages would we have
to any competitors?
__________________________
How will you acquire new
customers? ________________
___________________________
How often will they come back?
__________________________
___________________________
Why will users come back?
___________________________
___________________________
Why will users refer us to others?
____________________________
____________________________
How does this solution support
company vision?_____________
____________________________
Feasibility
assumption
prompts
(Engineering)
What are the biggest engineering
or tech challenges?
_____________________________
_ __________________________
What are the legal or regulatory
risks? ______________________
___________________________
What are the internal governance
or policy hurdles?
___________________________
___________________________
Why will leadership teams
support this? ________________
___________________________
Where does your funding come
from? _____________________
___________________________
Adapted from David Bland, Precoil
@MandaLaceyS | #UXNZ2017
Be as specific and
precise as possible.
90. 1. Assumptions about users and their problems/
needs are riskier than assumptions about
solutions.
2. It doesn’t really matter where things land. The
general quadrant is good enough.
3. The conversation is the most important piece.
PROTIPS
@MandaLaceyS | #UXNZ2017
92. 3. Make a clear hypothesis
@MandaLaceyS | #UXNZ2017
93. Hypothesis
“ a supposition or proposed
explanation made on the basis of
limited evidence as a starting point for
further investigation.”
-The Interwebs
@MandaLaceyS | #UXNZ2017
94. @MandaLaceyS | #UXNZ2017
If we [do, build, provide x thing],
then [these people]
will [some desirable outcome].
We’ll know when [actionable metrics].
103. So let’s say…
@MandaLaceyS | #UXNZ2017
$5,000 extra per week to
cover $25k in 5 weeks
(which is Extra $5/sale)
Necessary added value
104. @MandaLaceyS | #UXNZ2017
If we [suggest matching accessories in the cart],
then [Fashion-challenged Amandas]
will [purchase more accessories].
We’ll know when [we earn $5,000 over the course
of a week].
105. @MandaLaceyS | #UXNZ2017
If we [suggest matching accessories in the cart],
then [Fashion-challenged Amandas]
will [purchase more accessories].
We’ll know when [average order value goes up
$5].
OR
106. Sometimes it’s
easier to
frame as
failure
condition.
@MandaLaceyS | #UXNZ2017
“If we don’t make
at least x% more
on each order,
we won’t
implement.”
107. Sometimes
you don’t
have existing
numbers, so
you use what
you have.
@MandaLaceyS | #UXNZ2017
“We’ll move
forward with
option a if they
pick it 25% more
often than
anything of the
other options.”
109. Your Turn!
@MandaLaceyS | #UXNZ2017
*You’re trying to create a new application to help
busy parents plan meals and you’ve just interviewed
a dozen parents who were out grocery shopping
with their kids.
110. @MandaLaceyS | #UXNZ2017
If we [do, build, provide x thing],
then [these people]
will [some desirable outcome].
We’ll know when [actionable metrics].
Your Turn
111. If we build an app that automatically generates 5
recipe ideas per week,
Then busy parents,
Will be interested in downloading this application.
We’ll know this is true when we present them
with a variety of food-related apps and they choose the
recipe generation app at least 15 percentage points
more often than any other choice.
@MandaLaceyS | #UXNZ2017
128. Exercise
How would you test the hypothesis you just created?
What might you need to build?
How might you make that even more minimal?
How might you make that even more lovable?
129. If we build an app that automatically generates 5
recipe ideas per week,
Then busy parents,
Will be interested in downloading this application.
We’ll know this is true when we present them
with a variety of food-related apps and they choose the
recipe generation app at least 15 percentage points
more often than any other choice.
@MandaLaceyS | #UXNZ2017
How would you test this hypothesis?
130. Create fundraisers for 3 theoretical apps and
see what gets most funding.
@MandaLaceyS | #UXNZ2017
Maybe…
131. Create a landing page that presents 3
different app options and see which is
clicked most.
@MandaLaceyS | #UXNZ2017
OR
132. Create ads for 3 different app ideas and see
what gets the most click-throughs.
@MandaLaceyS | #UXNZ2017
OR
133. Describe 3 different options and utilize click
testing to see what gets chosen most often.
@MandaLaceyS | #UXNZ2017
Maybe…
134. 5. THEN run your test
@MandaLaceyS | #UXNZ2017
142. Actionable MetricsPivots aren’t
You might need to change:
Feature focus
Overall market
Specific customer segment
Platform
Channel
Technology
Engine of growth
etc.
etc.
etc.
@MandaLaceyS | #UXNZ2017@MandaLaceyS | #UXNZ2017
magic.
153. @MandaLaceyS | #UXNZ2017
Experimentation supports vision.
Adapted from Mark Shahid | @plastic_fuzz
Generative longitudinal research
Short periods of investigation