SlideShare a Scribd company logo
Lean UX Workshop I.I
Lean UX
Assumption Hypotheses
Workshop
Chris Barklem
Lean UX Labs & Just UX
What is a Hypotheses
Let us look at Feynman on Scientific Method on how science comes up
with a new law.
What is a Hypotheses
First we guess, then we compute the consequences and then compare
the outcome to see if it fits our guess.
• We declare our assumptions
• We run experiments
• If our results disagree with our ideas of the outcome, we are wrong.
Declare our assumptions
What assumptions do you have?
• About your customers?
• That if proven false, will cause you to fail?
In other words: what do you need to know in order to move forward
successfully?
Lean and the Design of Business
• Every decision you make about your offering is a design decision.
• Every design decision is a hypothesis.
• Declare your assumptions and test them.
• Evaluate your results ruthlessly, and be prepared to change course.
Reduce Inventory, Risk and Waste
MONTHS
Reduce Inventory, Risk and Waste
HOURS
Less risk, more often
Nail it, then scale it. Key ideas…
• Prioritize learning over growth
• Prioritize making over analysis
• Frame your business as a set of hypotheses
• Reality testing
Allows teams to move faster..
Typical product assumptions…
• Who is the user? Who is the customer?
• Where does our product fit in their work or life?
• What problems does our product solve?
• When and how is our product used?
• What features are important?
• How should our product look and behave?
Typical business assumptions…
• How will we acquire customers?
• How will we make money?
• Who are our competitors?
• What’s our differentiator?
• What’s our biggest risk?
• How do we expect to solve it?
Hypothesis: 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].
BeYou: Vision Statement
BeYou will and .
We will succeed by:
•
•
•
Personas
Lightweight personas
• Model of what we know today
• Low investment, easy to improve
Assumption: our users
What info do we need?
1. Name and sketch
2. Demographic and psychographic (relevant)
3. Needs
4. How we address needs
Team exercise: our customers
1. Name and sketch
2. Demographic and
psychographic (relevant)
3. Needs
4. How we address needs
1 2
3 4
Exercise: Who could use our service?
1. Flip size: Brainstorm a list of potential users.
2. Be more specific.
3. Identify groups of like mindedness.
4. Choose the two you want to work on first.
5. Personas are people, drill down from group to individual.
Exercise: Who could use our service?
1. Name and Sketch
• Draw
• Age
• She/He
2. Needs
• Help with?
3. Demographics
• Job
• Education
• Tech understanding
• How does she use technology
• Social media
• Where is he/she
• Physical challenges
4. How we addrees the needs
What is progress
Manufacturing: production of high-quality goods.
Agile: working software is the primary measure of progress.
Lean Startup: the measure of progress is a validated learning.
Lean UX: Outcomes and impact.
Output, Outcome, Impact
• Output: the software we build. The materials we produce.
• Easy to measure
• Outcome: the observable change in the world after we deliver
output.
• Hard to measure
• Impact: the change we see over time.
• Very hard to attribute
Output, Outcome, Impact
• Output: a new log-in page (feature)
• Outcome: users of this page log in at a higher success rate
• Impact: increase in sales
Why manage with outcomes?
From “Principles behind the Agile Manifesto.”
• Build projects around motivated individuals. Give them the
environment and support they need, and trust them to get the job
done.
• The best architectures, requirements, and designs emerge from self-
organizing teams.
Exercise: Detailed outcomes
Step 1: individual brainstorm
What KPIs and metrics determine the success of our product/project?
Write one idea per post-it(use the black markers)
Example:
• Increase in workouts, completed.
• Decrease in the number of questions about making workouts directed
at the fitness coach.
Affinity Mapping
• Time boxed, 6 minutes.
• What KPIs and metrics determine the success of our
product/project?
• One per post-it note.
• Changes in behaviour that indicate our product is hitting the mark.
Organize into themes
• Put all the post-it notes up onto the space.
• Explain each post-it to the group.
• Then as a team, come up with groups, themes of how you would
measure success.
Exercise: Features
Step 1: individual brainstorm
What features will serve our users and create our desired outcomes?
Write one idea per post-it (use the black markers)
Example:
• 10K preporation schedule
• Losing 5Kg of weight for a wedding
Exercise Start
6 minutes to create as many features that will serve our users and
create our desired outcomes.
Organize
Like before, place the features, explain the features to the group. Then
organize into themes.
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].
Exercise: Create your hypotheses
Take all your assumptions to the wall and group into themes with your
team.
We believe For Will achieve Proof/Evidence
[Doing this] [These people] [these outcomes] [measured this way]
So as a team what do you believe first? You can grab post-its or rewrite the
row in pen. Feature can address multiple personas, multiple outcomes and
have multiple measures. Make some stripes.
Exercise: continued
Optimize these statements to form
hypotheses for the project.
You should have a set of statements
that read:
“We believe that doing this for these
people will achieve this outcome.”
Its easy to fall into the feature trap
• This exercise details how and why you chose features and for what
outcomes.
• As a team you want to look at which assumptions are the most
riskiest to confirm. Which have the greatest impact on success.
• Test the risk first. Remove it first.
Its easy to fall into the feature trap
• This exercise details how and why you chose features and for what
outcomes.
• As a team you want to look at which assumptions are the most
riskiest to confirm. Which have the greatest impact on success.
• Test the risk first. Remove it first.
Test your riskiest assumptions first
Stop – Well done
• You have:
• Declared a series of assumptions around who we believe we are building a
product for.
• What outcomes we would like to achieve.
• What features we believe will drive those outcomes
• We have written hypotheses from those.
• The last assumption we need to define is how the product needs to look to
deliver these features. Which is what we will look at in a design studio
environment.

More Related Content

PPTX
Putting personas to work - University of Edinburgh Website Programme
PDF
Lean UX Workshop
PDF
Lean UX Recipe Cards (set 01)
PDF
Introduction to Lean Startup & Lean User Experience Design
PDF
Getting into UX: How to take your first steps to a career in user experience
PDF
Writing kick-ass hypotheses: Lean UX Meetup, Las Vegas : July
PDF
Introduction to Kanban for Creative Agencies
PPTX
Requirements are hypotheses: My experiences with Lean UX
Putting personas to work - University of Edinburgh Website Programme
Lean UX Workshop
Lean UX Recipe Cards (set 01)
Introduction to Lean Startup & Lean User Experience Design
Getting into UX: How to take your first steps to a career in user experience
Writing kick-ass hypotheses: Lean UX Meetup, Las Vegas : July
Introduction to Kanban for Creative Agencies
Requirements are hypotheses: My experiences with Lean UX

What's hot (20)

PDF
Collaborative Brainstorming for Better UX Workshop
PDF
What your customers REALLY think: Incorporating usability testing into agile
PDF
Testing Your MVP
PDF
Building Buy-In: 
Internally Positioning UX 
for Executive Impact. BigDesign...
PDF
[DevDay2019] Things i wish I knew when I was a 23-year-old Developer - By Chr...
PDF
Product Strategy for UXers
PDF
MEMSI June: Primary Market Research Skills Clinic
PDF
What does the Business need from DevOps?
PDF
Best Practice For UX Deliverables - Eventhandler, London, 05 March 2014
PDF
Introduction to Lean UX
PPTX
Why UX #FAILS (with notes)
PDF
UX Recipe Cards
PDF
Lean UX Workshop
PPTX
Why your product team should use User Story Mapping to link user research to ...
PDF
Lean startup workshop: practical ways to turn your idea into a successful pro...
PDF
Product Design using Lean UX
PPTX
Grassroots Design Thinking - AIGA SC
PPTX
Prototyping Ideas
PPTX
Building a Minimum Viable Product
PDF
Be A Great Product Leader (Dropbox / AirBnB 2013)
Collaborative Brainstorming for Better UX Workshop
What your customers REALLY think: Incorporating usability testing into agile
Testing Your MVP
Building Buy-In: 
Internally Positioning UX 
for Executive Impact. BigDesign...
[DevDay2019] Things i wish I knew when I was a 23-year-old Developer - By Chr...
Product Strategy for UXers
MEMSI June: Primary Market Research Skills Clinic
What does the Business need from DevOps?
Best Practice For UX Deliverables - Eventhandler, London, 05 March 2014
Introduction to Lean UX
Why UX #FAILS (with notes)
UX Recipe Cards
Lean UX Workshop
Why your product team should use User Story Mapping to link user research to ...
Lean startup workshop: practical ways to turn your idea into a successful pro...
Product Design using Lean UX
Grassroots Design Thinking - AIGA SC
Prototyping Ideas
Building a Minimum Viable Product
Be A Great Product Leader (Dropbox / AirBnB 2013)
Ad

Viewers also liked (20)

PDF
User Experience & Lean Startup
PPTX
Lean UX workshop - Part One
PPT
Prototyping - the what, why and how at the University of Edinburgh
PPTX
Collaborative sketching - research through design
PDF
Innovation through Design Thinking
PDF
Lean UX
PDF
Linking UX Ideas for an Aha Moment from Non-Empathizers
PDF
Agile Prototyping Best Practices
PDF
Implementing Lean UX: The Practical Guide to Lean User Experience
PDF
Tutorial Lean UX Workshop - MexIHC 2016
PDF
Lean UX, Somewhere Over the Waterfall
KEY
Lean User Experience in a Lean Startup
PDF
Lean UX + UX Strat, from UX Strat conference, September 2013
PDF
Team Personas for Enterprise UX
PDF
Lean UX in the Enterprise: A Government Case Study
PDF
Understanding the Power of Lean UX
PDF
Storytelling: Selling a brilliant idea like a rock star
PDF
UX Strategy Blueprint for Agile Teams
PDF
Designing with Lean UX : Rapid Product Design (Handouts only) [UX Lisbon 2014]
PDF
User Experience: A Lean UX Process
User Experience & Lean Startup
Lean UX workshop - Part One
Prototyping - the what, why and how at the University of Edinburgh
Collaborative sketching - research through design
Innovation through Design Thinking
Lean UX
Linking UX Ideas for an Aha Moment from Non-Empathizers
Agile Prototyping Best Practices
Implementing Lean UX: The Practical Guide to Lean User Experience
Tutorial Lean UX Workshop - MexIHC 2016
Lean UX, Somewhere Over the Waterfall
Lean User Experience in a Lean Startup
Lean UX + UX Strat, from UX Strat conference, September 2013
Team Personas for Enterprise UX
Lean UX in the Enterprise: A Government Case Study
Understanding the Power of Lean UX
Storytelling: Selling a brilliant idea like a rock star
UX Strategy Blueprint for Agile Teams
Designing with Lean UX : Rapid Product Design (Handouts only) [UX Lisbon 2014]
User Experience: A Lean UX Process
Ad

Similar to Lean UX workshop - Part Two (20)

PDF
Product Management Guide - A Work In Progress
PDF
Lean UX principles
PDF
Lean Startup 301
PDF
Lean Startup 101
PDF
What Mushrooms and Fish Poop Taught Us About Launching a New Line of Breakfas...
PPT
Agreeing on business value
PPTX
Purpose then priorities
KEY
Mentor your ass off
PPTX
0 to 10 Million Leads : Lessons learned from the lead gen trenches
PPTX
Boston UXPA 2016 | What’s Worse: A Root Canal or Selecting Health Insurance
PPTX
Business Growth Engineering
PDF
[Lean starter kit] workbook ver2.7 - entrepreneurial culture center
PDF
EIA2019HK - Problem-Solution Fit - Mike Kyriacou
PPTX
Presented at Ford's 2017 Global IT Learning Summit (GLITS)
PDF
Experiment to build the right thing
PPT
Problem Solving Skills
PDF
Building Blocks of a strong Experimentation Program (1).pdf
 
PPTX
ASU Startup School Session 1
PDF
Continuous discovery - Caitlin Blackwell
PPTX
Business Validation presentation ppt.pptx
Product Management Guide - A Work In Progress
Lean UX principles
Lean Startup 301
Lean Startup 101
What Mushrooms and Fish Poop Taught Us About Launching a New Line of Breakfas...
Agreeing on business value
Purpose then priorities
Mentor your ass off
0 to 10 Million Leads : Lessons learned from the lead gen trenches
Boston UXPA 2016 | What’s Worse: A Root Canal or Selecting Health Insurance
Business Growth Engineering
[Lean starter kit] workbook ver2.7 - entrepreneurial culture center
EIA2019HK - Problem-Solution Fit - Mike Kyriacou
Presented at Ford's 2017 Global IT Learning Summit (GLITS)
Experiment to build the right thing
Problem Solving Skills
Building Blocks of a strong Experimentation Program (1).pdf
 
ASU Startup School Session 1
Continuous discovery - Caitlin Blackwell
Business Validation presentation ppt.pptx

Recently uploaded (20)

PPTX
12. Community Pharmacy and How to organize it
PPTX
HPE Aruba-master-icon-library_052722.pptx
PPTX
DOC-20250430-WA0014._20250714_235747_0000.pptx
PDF
Trusted Executive Protection Services in Ontario — Discreet & Professional.pdf
DOCX
actividad 20% informatica microsoft project
PPTX
YV PROFILE PROJECTS PROFILE PRES. DESIGN
PPT
unit 1 ppt.ppthhhhhhhhhhhhhhhhhhhhhhhhhh
PDF
SEVA- Fashion designing-Presentation.pdf
PPTX
mahatma gandhi bus terminal in india Case Study.pptx
PDF
GREEN BUILDING MATERIALS FOR SUISTAINABLE ARCHITECTURE AND BUILDING STUDY
PPTX
Special finishes, classification and types, explanation
PPTX
Complete Guide to Microsoft PowerPoint 2019 – Features, Tools, and Tips"
PPTX
artificialintelligencedata driven analytics23.pptx
PDF
BRANDBOOK-Presidential Award Scheme-Kenya-2023
PDF
Benefits_of_Cast_Aluminium_Doors_Presentation.pdf
PDF
Integrated-2D-and-3D-Animation-Bridging-Dimensions-for-Impactful-Storytelling...
PDF
YOW2022-BNE-MinimalViableArchitecture.pdf
PPTX
AD Bungalow Case studies Sem 2.pptxvwewev
PDF
UNIT 1 Introduction fnfbbfhfhfbdhdbdto Java.pptx.pdf
PDF
The Advantages of Working With a Design-Build Studio
12. Community Pharmacy and How to organize it
HPE Aruba-master-icon-library_052722.pptx
DOC-20250430-WA0014._20250714_235747_0000.pptx
Trusted Executive Protection Services in Ontario — Discreet & Professional.pdf
actividad 20% informatica microsoft project
YV PROFILE PROJECTS PROFILE PRES. DESIGN
unit 1 ppt.ppthhhhhhhhhhhhhhhhhhhhhhhhhh
SEVA- Fashion designing-Presentation.pdf
mahatma gandhi bus terminal in india Case Study.pptx
GREEN BUILDING MATERIALS FOR SUISTAINABLE ARCHITECTURE AND BUILDING STUDY
Special finishes, classification and types, explanation
Complete Guide to Microsoft PowerPoint 2019 – Features, Tools, and Tips"
artificialintelligencedata driven analytics23.pptx
BRANDBOOK-Presidential Award Scheme-Kenya-2023
Benefits_of_Cast_Aluminium_Doors_Presentation.pdf
Integrated-2D-and-3D-Animation-Bridging-Dimensions-for-Impactful-Storytelling...
YOW2022-BNE-MinimalViableArchitecture.pdf
AD Bungalow Case studies Sem 2.pptxvwewev
UNIT 1 Introduction fnfbbfhfhfbdhdbdto Java.pptx.pdf
The Advantages of Working With a Design-Build Studio

Lean UX workshop - Part Two

  • 2. Lean UX Assumption Hypotheses Workshop Chris Barklem Lean UX Labs & Just UX
  • 3. What is a Hypotheses Let us look at Feynman on Scientific Method on how science comes up with a new law.
  • 4. What is a Hypotheses First we guess, then we compute the consequences and then compare the outcome to see if it fits our guess. • We declare our assumptions • We run experiments • If our results disagree with our ideas of the outcome, we are wrong.
  • 5. Declare our assumptions What assumptions do you have? • About your customers? • That if proven false, will cause you to fail? In other words: what do you need to know in order to move forward successfully?
  • 6. Lean and the Design of Business • Every decision you make about your offering is a design decision. • Every design decision is a hypothesis. • Declare your assumptions and test them. • Evaluate your results ruthlessly, and be prepared to change course.
  • 7. Reduce Inventory, Risk and Waste MONTHS
  • 8. Reduce Inventory, Risk and Waste HOURS
  • 10. Nail it, then scale it. Key ideas… • Prioritize learning over growth • Prioritize making over analysis • Frame your business as a set of hypotheses • Reality testing Allows teams to move faster..
  • 11. Typical product assumptions… • Who is the user? Who is the customer? • Where does our product fit in their work or life? • What problems does our product solve? • When and how is our product used? • What features are important? • How should our product look and behave?
  • 12. Typical business assumptions… • How will we acquire customers? • How will we make money? • Who are our competitors? • What’s our differentiator? • What’s our biggest risk? • How do we expect to solve it?
  • 13. Hypothesis: 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.
  • 14. 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].
  • 15. BeYou: Vision Statement BeYou will and . We will succeed by: • • •
  • 16. Personas Lightweight personas • Model of what we know today • Low investment, easy to improve
  • 17. Assumption: our users What info do we need? 1. Name and sketch 2. Demographic and psychographic (relevant) 3. Needs 4. How we address needs
  • 18. Team exercise: our customers 1. Name and sketch 2. Demographic and psychographic (relevant) 3. Needs 4. How we address needs 1 2 3 4
  • 19. Exercise: Who could use our service? 1. Flip size: Brainstorm a list of potential users. 2. Be more specific. 3. Identify groups of like mindedness. 4. Choose the two you want to work on first. 5. Personas are people, drill down from group to individual.
  • 20. Exercise: Who could use our service? 1. Name and Sketch • Draw • Age • She/He 2. Needs • Help with? 3. Demographics • Job • Education • Tech understanding • How does she use technology • Social media • Where is he/she • Physical challenges 4. How we addrees the needs
  • 21. What is progress Manufacturing: production of high-quality goods. Agile: working software is the primary measure of progress. Lean Startup: the measure of progress is a validated learning. Lean UX: Outcomes and impact.
  • 22. Output, Outcome, Impact • Output: the software we build. The materials we produce. • Easy to measure • Outcome: the observable change in the world after we deliver output. • Hard to measure • Impact: the change we see over time. • Very hard to attribute
  • 23. Output, Outcome, Impact • Output: a new log-in page (feature) • Outcome: users of this page log in at a higher success rate • Impact: increase in sales
  • 24. Why manage with outcomes? From “Principles behind the Agile Manifesto.” • Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. • The best architectures, requirements, and designs emerge from self- organizing teams.
  • 25. Exercise: Detailed outcomes Step 1: individual brainstorm What KPIs and metrics determine the success of our product/project? Write one idea per post-it(use the black markers) Example: • Increase in workouts, completed. • Decrease in the number of questions about making workouts directed at the fitness coach.
  • 26. Affinity Mapping • Time boxed, 6 minutes. • What KPIs and metrics determine the success of our product/project? • One per post-it note. • Changes in behaviour that indicate our product is hitting the mark.
  • 27. Organize into themes • Put all the post-it notes up onto the space. • Explain each post-it to the group. • Then as a team, come up with groups, themes of how you would measure success.
  • 28. Exercise: Features Step 1: individual brainstorm What features will serve our users and create our desired outcomes? Write one idea per post-it (use the black markers) Example: • 10K preporation schedule • Losing 5Kg of weight for a wedding
  • 29. Exercise Start 6 minutes to create as many features that will serve our users and create our desired outcomes.
  • 30. Organize Like before, place the features, explain the features to the group. Then organize into themes.
  • 31. 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].
  • 32. Exercise: Create your hypotheses Take all your assumptions to the wall and group into themes with your team. We believe For Will achieve Proof/Evidence [Doing this] [These people] [these outcomes] [measured this way] So as a team what do you believe first? You can grab post-its or rewrite the row in pen. Feature can address multiple personas, multiple outcomes and have multiple measures. Make some stripes.
  • 33. Exercise: continued Optimize these statements to form hypotheses for the project. You should have a set of statements that read: “We believe that doing this for these people will achieve this outcome.”
  • 34. Its easy to fall into the feature trap • This exercise details how and why you chose features and for what outcomes. • As a team you want to look at which assumptions are the most riskiest to confirm. Which have the greatest impact on success. • Test the risk first. Remove it first.
  • 35. Its easy to fall into the feature trap • This exercise details how and why you chose features and for what outcomes. • As a team you want to look at which assumptions are the most riskiest to confirm. Which have the greatest impact on success. • Test the risk first. Remove it first.
  • 36. Test your riskiest assumptions first
  • 37. Stop – Well done • You have: • Declared a series of assumptions around who we believe we are building a product for. • What outcomes we would like to achieve. • What features we believe will drive those outcomes • We have written hypotheses from those. • The last assumption we need to define is how the product needs to look to deliver these features. Which is what we will look at in a design studio environment.