Advertisement
Prototyping - A Conversation about your Assumptions
Oct. 22, 2014•0 likes•1,463 views
4 likes
Be the first to like this
Show More
views
Total views
0
On Slideshare
0
From embeds
0
Number of embeds
0
Download to read offline
Report
Design
Prototyping is all about facilitating a conversation between you and your user. The goal of this conversation is to test the assumptions you had while building your product. This presentation examines different prototyping scoping, designing and testing methodologies from the perspective of testing assumptions in the product design process.
Growth SparkFollow
Growth SparkAdvertisement
Prototyping - A Conversation about your Assumptions
- prototyping A Conversation About Your Assumptions presented at olin college
- ross beyeler Founder of Growth Spark Babson College Alum BusinessWeek Top 25
- agenda Introduction Scoping Activities Testing for Content Testing for Context Testing for Capabilities Prototype Testing & Feedback Q&A
- Introduction
- introduction We use prototyping to facilitate a conversation between us and our users.
- introduction These conversations focus on testing a set of assumptions as we continue to define the product.
- introduction We use the quickest, and most effective methods of prototyping to start these conversations.
- introduction Determining what method to use depends on the type of assumptions you are testing.
- introduction There are three types of assumptions you should be testing while prototyping. Content. Context Capabilities 1 2 3
- Scoping Activities
- scoping activities Before we can begin prototyping, we need to define a baseline driven by assumptions. The following activities inform our assumptions.
- audience personas Who is using your product? photo via mailchimp.com
- problem definition What problem are you trying to solve? chalkboard
- how will you help How will your product solve their problem? photo via caryarts.net
- define success What does success look like for your users?
- Testing for Content
- testing for content Testing for content is about defining what elements need to be included in your product.
- testing for content We need to visually communicate the elements of our product that meet our user’s goals.
- low-fi wireframes Whiteboard Sketches
- mid-fi wireframes Balsamiq
- hi-fi wireframes UX Pin
- Testing for Context
- paper prototypes photo via medialab.hva.nl
- pdf prototypes Invision App photo via wireframes.linowski.ca
- html prototypes Bootstrap photo via getboostrap.com
- mobile prototypes Flinto photo via flinto.com
- cms-based prototypes Wordpress photo via wordpress.org
- Testing for Capabilities
- scripts Codepen photo via codepen.com
- scaffolding Ruby Tutorial photo via railstutorial.org
- data-scraping Kimono App photo via kimono.com
- mock-data Mocky.io photo via mocky.io
- crud data Firebase photo via firebase.com
- api integrations Zapier photo via zapier.com
- rapid infrastructure Heroku photo via heroku.com
- Prototype Testing & Feedback
- prototype testing & feedback If we built our prototype to test our assumptions, then we must test our prototype.
- prototype testing & feedback Getting your prototype in the hands of your users is key to collecting feedback that will improve your product.
- in-person demos photo via tishadiplomaproject.blogspot.com
- qualitative surveys Qualaroo photo via heroku.com
- usability testing UserTesting photo via usertesting.com
- visual tracking Mouseflow photo via mouseflow.com
- the end! Thank you! ross@growthspark.com / @growthspark any questions?
Advertisement