How to Prototype

How to Prototype

1. Don't prototype right away

   • Expensive
   • Takes a long time
   • sunk cost fallacy

2. Why prototype?

   • Resolve uncertanties
   • Iterate on a design
   • Converge on the best design
   • Helps make decisions
   • Acquire knowledge
     • What is made must be close to how it's tested
   • Prototypes not always necessary
     • Cost of implementation > cost of prototype

3. Ways to prototype

   • Sketch
     • Low-fidelity
     • Hand-made
     • Useful early in design process
   • Bodystorming
     • Use hands and bodies
     • Simulate behavior and interactions
     • Fast/Low cost
   • Paper Prototype
     • Informal Drawing
     • Facilitates Communication
     • Testable
     • Precise wireframe to model what the user sees
   • Wizard of Oz
     • Useful when trying to create something
       • Complex
       • Intelligent functionality
       • Doesn't exist yet
       • Time consuming
     • Uses human mind to replicate design
     • Variable Fidelity
       • Difficult for human to act like a computer
   • Figma, InVision, Adobe XD, and Sketch
     • High fidelity
     • Support collaboration
     • Interactive wireframes and workflows
     • Can closely mimic a final product
     • Take more time