This class will introduce the idea of a scientific approach to product development. We’ll focus on how to make sure we build products customers love, starting with how to frame hypotheses and perform user research.
of the questions they had. Go ﬁgure it out for yourself, they would say. “I got really into the scientiﬁc method of developing a hypothesis and testing it and getting a result and going back to do it again.” http://www.forbes.com/sites/bruceupbin/2012/06/18/wait-did-this-15-year-old-from-maryland-just-change-cancer-treatment/
need with the time, skills and technology we have) 1. value risk (whether customers will buy it or users will choose to use it) 2. usability risk (whether users can ﬁgure out how to use it) 4. business viability risk (whether this solution also works for the various aspects of our business) measuring risk https://svpg.com/four-big-risks/
product that enables a full turn of the Build-Measure-Learn loop with a minimum amount of eﬀort and the least amount of development time.” — Eric Ries “An MVP should never be an actual product (where product is deﬁned as something that your developers can release with conﬁdence, that your customers can run their business on, and that you can sell and support). The MVP should be a prototype, not a product.” — Marty Cagan
and knowledge about users explicit • Give the team a common language to talk meaningfully about users • Building empathy towards users in a way that data can’t accomplish • Sketch out a person, their needs, and behavior • Look into the mind of the targeted persona & think about the sensory experiences of the character when interacting with your company and product • Work together in your teams and consider: Who are your users and why are they using the system? What behaviors, assumptions, and expectations color their view of the system? FURTHER READING http://www.innovationgames.com/empathy-map/ | Adlin, T., & Pruitt, J. (2010). The Essential Persona Lifecycle | http://www.cooper.com/journal/2014/05/persona-empathy-mapping