Skip to content

Week Ten - Prototyping and Concept Testing

  • Understand the importance and benefits of prototyping in the design process.
  • Differentiate between validation and evaluation in concept testing.
  • Recognize various fidelity levels of prototypes and when to use each.
  • Identify the tools and methods suitable for different stages of prototyping.

MAD9034 10-1 - Prototyping

MAD9034 10-2 - Concept Testing

A prototype is an early model or sample built to test a concept or process.

Goals of Prototyping:

  • Test a design hypothesis.
  • Learn, improve, and gain confidence in a product or idea before investing time and money in the full implementation.
  • Early changes are easier and less costly to make.
  • Enables refining of design elements before the final version.
  • Validating a design introduces bias; it may discourage users from pointing out issues.
  • Replace “validate” with: test, research, evaluate, examine, study, analyze, watch how people use, see where the design succeeds and fails.

Validation vs. Evaluation

  • Usability: Layout, affordance/feedback, terminology.
  • Navigation: Ensure users can navigate effectively.
  • Functionality: Ensure interactive elements support user tasks.
  • Alternate Designs: Determine most user-preferred options.
Paper PrototypeDigital PrototypeDev Prototype
Early design stageAny design stageTest complex designs
before final implementation
Paper PrototypeDigital PrototypeDev Prototype

Prototypes can vary in their detail and realism. Choosing the right fidelity depends on the goals, audience, and stage of the design.

Low Fidelity

  • Used early in the design process.
  • Quick, easy, and iterative.
  • Test assumptions and identify major problems.

Mid Fidelity

  • Refines solutions tested in low fidelity.
  • Tests finer details and specific interactions.
  • Static wireframes.
  • Partially interactive digital interfaces.

High Fidelity

  • Closely represents the final product.
  • Used for the last line of testing before actual development.
  • Pixel-perfect designs.
  • Real working code with simulated interactions.
  • Actual content and visual design.

Wireframing tools

Concept testing captures the key essence (the value proposition) of a new product or service concept to understand if it meets the needs of the target audience.

  • Connecting with users.
  • Communicating effectively with users.
  • Identifying user responses.
  • Gauging user interpretations of designs.
  • Testing multiple design concepts.
  • Observing user interactions with on-screen elements.
  • Refining content, interactive elements, and overall sequences.
  • Testing multiple microinteraction solutions.

Here is a help article which looks at testing in more detail.

Low-fidelity prototypes allow for testing:

  • Concepts.
  • Understanding problems.
  • Identifying ‘blind spots’.
  • Gauging the scope of solutions.

Paper Prototyping: How to Create & Usability-Test Simple UI Prototypes (40 min tutorial)

Higher fidelity prototypes help test:

  • Usability.
  • Content relevance and clarity.
  • Efficiency.
  • Desirability.

It aids design iterations, leading to:

  • A deeper empathy and understanding of users.
  • Insights that might redefine your problem statement.
  • New solution ideas.
  • Design and prototype improvement.

Concept Testing Image

To maximize concept testing benefits:

  1. The Prototype

    • Remember, the prototype is under test, not the user.
    • Design the prototype with a specific question in mind.
  2. Context and Scenario

    • Focus on the primary use-case scenario.
  3. User Interaction

    • Set user expectations about the prototype and the test.
    • Avoid diving into prototype operation details.
  4. Observation and Feedback Capture

    • Ensure the user’s interaction is uninterrupted.
    • Record significant observations.

Usability Test with a Paper Prototype

  1. Recruit Users

    • Seek representative users.
    • Testing with 5 users typically identifies most problems.
    • Use ‘hallway testing’ if recruiting is challenging.
  2. Setup

    • Use a neutral, quiet environment.
    • Have adequate space and seating.
    • Include a facilitator, “product” operator, and ideally, a note-taker.
  3. Conducting Sessions

    • Begin with an introduction.
    • Guide users through tasks.
    • Observe without intervening.
    • Engage in post-test discussions.
  • Stick to observed facts.
  • Relate feedback to initial research questions.
  • Note answered and unanswered questions.
  • Be prepared for new questions to emerge.
  • Remember: Testing is iterative. Each round brings clarity.