Unit 3 - An Experimental Approach to Product Development
This class will present hypothesis-driven development, the modern paradigm for evolving validated products. We’ll dive into how to frame hypotheses, design experiments, and use A/B testing to gather data to prove or disprove our ideas.
identify experiments to test hypotheses understand how to do outcome-based planning describe hypothesis-driven development understand why small batches are important define A/B testing and the culture it enables learning outcomes
@jezhumble Jeff Gothelf “Better product definition with Lean UX and Design” http://bit.ly/TylT6A hypothesis-driven delivery We believe that [building this feature] [for these people] will achieve [this outcome]. We will know we are successful when we see [this signal from the market].
exercise • choose a hypothesis from week 2’s class • design an experiment to test your hypothesis • what do you expect the results to be? • what result will confirm your hypothesis? • what result will disprove your hypothesis? • how soon can we get the result?
do less “Evaluating well-designed and executed experiments that were designed to improve a key metric, only about 1/3 were successful at improving the key metric!” “Online Experimentation at Microsoft” | Kohavi et al | http://stanford.io/130uW6X
“I think building this culture is the key to innovation. Creativity must flow from everywhere. Whether you are a summer intern or the CTO, any good idea must be able to seek an objective test, preferably a test that exposes the idea to real customers. Everyone must be able to experiment, learn, and iterate.” http://glinden.blogspot.com/2006/04/early-amazon-shopping-cart.html
less rework, higher quality you can stop at any time with a working system faster feedback (assuming people pay attention) higher motivation quickly release high priority features / bugfixes working in small batches Don Reinertsen, Principles of Product Development Flow, ch5.
lead time “How long would it take your organization to deploy a change that involved just one single line of code? Do you do this on a repeatable, reliable basis?” Mary and Tom Poppendieck, Implementing Lean Software Development, p59.
small batches • Reduce cycle time, variability in flow, risk, overhead • Accelerates feedback • Increase efficiency, motivation and urgency Don Reinertsen, Principles of Product Development Flow, ch5.
INVEST • Independent: can be worked on in any order • Negotiable: a conversation not a contract • Valuable: delivers benefit to a stakeholder • Estimable: to a good degree of precision • Small: less than a week to build • Testable: clearly defined acceptance criteria http://bit.ly/small-batches-invest
experiment design • Identify risky assumption about your product. • For example: “in order to make our business model work, 5% of people who sign up for my service that meet my criteria must pay $100 for the service.” • Write down hypothesis. • Design an experiment to test this with small sample size and acceptable level of precision, including testable success criteria. • Gather data. Analyze. State results. • State if hypothesis was validated or not. • What did you learn? What changes will you make?
further reading https://www.infoq.com/presentations/controlled-experiments https://svpg.com/assets/Files/goodprd.pdf Tom DeMarco & Tim Lister, Waltzing with Bears Humble et al, Lean Enterprise ch 9 Gojko Adzic, Impact Mapping
jezhumbleucb
hide2kano
alex2022
tarugoconf
kinunori
junyaokabe
gmoriki
asial_corp
olanetsoft
codeforeveryone
fullfull
motherhoodinadhd
sakunao
holman
morganepeng
mza
chriscoyier
philhawksworth
quramy
erikaheidi
geeforr
hannesfritz
thoeni
destraynor