10 Prototype and wireframing Flashcards
What simulates a working product and allows it to be tested with users, in order to improve the product’s design?
Prototype
What is characteristic of prototypes?
Interactive
An aid for development but shouldn’t be used alone
Typically don’t include annotations
What is NOT a benefit of low-fidelity prototypes?
Optimal for testing with users
You are working as a UX designer on a project and wish to test a rich mapping interaction. Which level of prototype should you use?
A high-fidelity prototype
What is NOT considered a weakness of high-fidelity prototypes?
Capable of creating only limited interactions
What is an annotated specification of controls, rules and feedback?
Wireframe
What is NOT a characteristic of wireframes?
Recommended for usability testing
You are working as a UX designer on a project with a relatively tight budget, but need to test basic product interactions with users. Which level of prototype should you use?
A mid-fidelity prototype
What is recommended when writing annotated notes?
Proof read in one go
Go through notes with developers
Be open to changing the rules
What is a prototype?
Simulates a working product
Simulates the interactive experience
Allows the product to be tested with users
Communicates the solution to stakeholders
Prototypes are a work in progress
The purpose of the prototype is to improve the design
What are the benefits of prototyping?
Helps improve quality of designs Identifies issues before build Reduces the risk of building flawed products reduces costs in the medium term helps validate or invalidate assumptions Helps shore ideas
How can a prototype help manage stekaholders?
Communicate design ideas clearly
Reduce ambuigity - everybody is talking about the same design
facilitates executive feedback and buy-in
facilitates better decision making
showcase design flare (shows the benefits of good design)
What are the benefits of low-fidelity prototypes?
Quick
Cheap
Catches potential problems early
Low skill level needed
What are the benefits of low-fidelity prototypes?
Quick
Cheap
Catches potential problems early
Low skill level needed
What can you learn from a low-fiedelity prototype?
Broad concepts and mental models
finding out if the user “gets it”
optimizing flow