Slides from my talk at UX Strat, 2013. (www.uxstrat.com)
How to use Lean UX methods to execute on business, product, and design strategy.
I presented a slightly altered version a few days later at Fluxible 2013. (http://www.fluxible.ca)
15. 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
16. 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
31. 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.
32. 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].
33. Hypothesis statement: feature
We believe that
creating Internet Mouse
for people who own “Convergence” TVs
will need a way to control the computer
from their couches
We’ll know this is true when we see
people buying Convergence TVs.
34. Hypothesis statement: business
We believe that
creating Internet Mouse
for people who own “Convergence” TVs
will get us in the internet business.
We’ll know this is true when we see
pre-orders from our retail channel
partners.
51. Output, Outcome, Impact
§ Output: the software we build. The materials we produce.
Easy to trace. Example: A new log-in page.
52. 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.
53. 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.
66. Business model validation
Product validation
Small team
Culture / Infrastructure to support continuous learning
Stakeholders
Small-chunk, outcome-based, predictable funding
$$$