Prototyping

Prototyping

1. Prototypes are a hypothesis

2. Testing a prototype

   • Most straightforward way to test is by watching users interact
   • Testing final products is uninformed and risky

3. Interactive Prototypes

   • Designer should set a response for each possible user action
   • Can be time consuming

4. Static Prototypes

   • Responses are given in real time
   • Wizard of Oz
     • Someone familiar with the design controls the user's screen based on user clicks
     • Useful to prototype some complex/intelligent functionality
   • Paper-prototype "computer"
     • Design expert holds paper design out and the user clicks, expert completes user action
   • Steal-the-mouse "computer"
     • Wizard of Oz technique but wizard navigates to pages on computer while user chooses

5. High fidelity prototypes

   • Faster system response
   • Can test specific UI components
   • Designer can fully observe test
   • Less likely to be affected by human error

6. Low fidelity prototypes

   • More time to work on design
   • Easier design changes
   • Less pressure on users
   • Designers feel less attached to designs
   • Stakeholders know work isn't done

7. Computer errors have a negative impact on users

8. Purpose is to acquire knowledge

9. Easiest form of prototyping is sketching

   • Has the least detail
   • Very low fidelity

10. Bodystorming is another technique

    • Using your body to simulate actions/behaviors
    • Very low fidelity

11. Paper prototypes

    • Can test well compared to sketches