4: Storyboard and Prototyping Flashcards
What are the differences between a storyboard and a prototype?
Prototype: Limited representation and rapid approximation of product design idea used to gather feedback
Storyboard: Sequence of diagrams or drawings or scene sketches used to convey a scenario or use case
One is used to illustrate that actual design idea, look and feel. Other is used to convey the use cases and scenarios,
Why should prototypes be tested on users?
interactive exploration with envisioned product
clarifies vague requirements with something concrete
test feasibility and compatibility
sells ideas
gather feedback from relevant users.
people cannot describe what they want but quick to recognise what they do not like
What are the differences between a low and high fidelity prototype?
Low-Fi prototypes:
- cheap and easy to produce, low tech concept to convey ideas
- Can be done using pen and paper
- conceptual design
High-Fi prototypes:
- closely resemble the final product
- functional and interactive
- physical design
Why is the choice of prototype fidelity important
the appropriate choice needs to be made to focus the feedback on the different aspects of the design, to avoid wasting time and allow for rapid prototyping
At which stage of the UCD process should each fidelity of prototype be used? Why?
Low-Fi prototypes should be used when testing the conceptual designs at the start of the design phase since it is easy and cheap to produce, and allow greater flexibility and exploration of ideas.
High-Fi prototypes should be used to test the usability and identify any issues in the flow when handling the product later in the development stage. This allows detailed feedback on the product.
What are the benefits and disadvantages of a video prototype?
advantages - cheap - fast - great tool for communication portable, self-explanatory, convey ideas to others - ties interface design to task
disadvantages
- needs to know how to edit videos
- needs to create a paper prototype to film
What are the pros and cons of using a Wizard of Oz prototype?
pros
- faster, cheaper, more iterative
- easy to create multiple variations
- more “realistic” vs paper prototype
- able to identify bugs and problems
- places user at the centre of the development
cons
- may misrepresent imperfect technology
- may simulate technologies that do not exist
- require training to be consistent
- exhausting
- some features may be impossible to simulate effectively
- may be inconvenient