Lean UX Workshop I.ILean UX Workshop I.ILean UXAssumption HypothesesWorkshopChris BarklemLean UX Labs & Just UXWhat is a HypothesesLet us look at Feynman on Scientific Method on how science comes up with a new law.What is a HypothesesFirst we guess, then we compute the consequences and then compare the outcome to see if it fits our guess.We declare our assumptionsWe run experimentsIf our results disagree with our ideas of the outcome, we are wrong.Declare our assumptionsWhat 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 BusinessEvery 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 WasteMONTHSReduce Inventory, Risk and WasteHOURSLess risk, more oftenNail it, then scale it. Key ideasPrioritize learning over growthPrioritize making over analysisFrame your business as a set of hypothesesReality testingAllows teams to move faster..Typical product assumptionsWho 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 assumptionsHow will we acquire customers?How will we make money?Who are our competitors?Whats our differentiator?Whats our biggest risk?How do we expect to solve it?Hypothesis: Write the test firstWe believe .Well know this is true when we seeQualitative outcome and/orQuantitative outcomeThat improves this KPI.Hypothesis StatementWe believe that[doing this]for [these people]will achieve [this outcome].Well know this is true when we see[this market feedback].BeYou: Vision StatementBeYou will and . We will succeed by: PersonasLightweight personasModel of what we know today Low investment, easy to improve Assumption: our usersWhat info do we need?Name and sketchDemographic and psychographic (relevant)NeedsHow we address needsTeam exercise: our customersName and sketchDemographic and psychographic (relevant)NeedsHow we address needs1234Exercise: Who could use our service?Flip size: Brainstorm a list of potential users.Be more specific.Identify groups of like mindedness.Choose the two you want to work on first.Personas are people, drill down from group to individual.Exercise: Who could use our service?Name and SketchDrawAgeShe/HeNeedsHelp with?DemographicsJobEducationTech understandingHow does she use technologySocial mediaWhere is he/shePhysical challengesHow we addrees the needsWhat is progressManufacturing: 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, ImpactOutput: the software we build. The materials we produce. Easy to measureOutcome: the observable change in the world after we deliver output.Hard to measureImpact: the change we see over time.Very hard to attributeOutput, Outcome, ImpactOutput: a new log-in page (feature)Outcome: users of this page log in at a higher success rateImpact: increase in salesWhy 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 outcomesStep 1: individual brainstormWhat 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 MappingTime 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 themesPut 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: FeaturesStep 1: individual brainstormWhat features will serve our users and create our desired outcomes?Write one idea per post-it (use the black markers)Example:10K preporation scheduleLosing 5Kg of weight for a weddingExercise Start6 minutes to create as many features that will serve our users and create our desired outcomes.OrganizeLike before, place the features, explain the features to the group. Then organize into themes.Hypothesis StatementWe believe that[doing this]for [these people]will achieve [this outcome].Well know this is true when we see[this market feedback].Exercise: Create your hypothesesTake all your assumptions to the wall and group into themes with your team.We believeForWill achieveProof/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: continuedOptimize 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 trapThis 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 trapThis 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 firstStop Well doneYou 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 outcomesWe 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.