How to Prototype

How to Prototype

1. Uncertainties

   • How will it work?
   • What will it look like?
   • Will it address the problem?
   • Prototypes help make decisions
     • Iterative from feedback
     • Converge design that addresses the problem
     • Acquire Knowledge
       • Other details left out
       • Prototype answers one question at a time
         • Accidentally order pizza?
         • How to know their pizza is on the way?
         • Safe ordering pizza from their watch?
       • Hypothesis
     • If cost is low, just make the actual product

2. Forms of prototypes

   • Sketch
     • See
     • Communicate
     • Evaluate
     • Fast
     • Beginning
     • Low fidelity
   • Bodystorming
     • Human body simulates behavior and interaction
   • Paper
     • Something you can test
     • Wireframe for every screen
     • Tapping on paper
     • Use our glass or gesture to indicate busy
   • Wizard of Oz
     • Human mind replicates complex functions
     • Hard to act like a computer
     • Static
     • AI based Systems
     • Steal-the-mouse
       • Same room as the user
       • User looks away from the screen during busy
   • Web and Mobile
     • Lots of time
     • High Fidelity

3. Fidelity

   • High
     • Realistic/Faster system response
     • Users remember what they did
     • Test workflow, UI components, graphical elements
       • Image Quality
       • Affordance
       • Engagement
     • Participants behave realistically
     • Allows designer to observe the test
     • Less human error
   • Low
     • More time to work on design
     • Make design changes easier
     • Less pressure on users to recognize hard work
     • Less attached to design
     • Stakeholders recognize work isn't finished

4. Interaction with User

   • Correct mistakes as fast as possible
   • Explain the prototype
     • Purpose
     • State
   • Get user state of mind