8.2 Understanding Prototypes

Introduction

The textbook explains that a prototype is an early, preliminary version of a product. It is a sample or model built to test a concept or process before the final product is developed. In simple words, a prototype is a first draft of a product that helps you see, touch, and test your idea before investing time and money in building the full product.

Definition

A prototype is a preliminary version or working model of a product. It is used to test and validate ideas, gather feedback, and refine the design before full-scale production.

Main Idea

The main idea is that prototypes help you learn quickly and cheaply. Instead of spending months or years building a full product, you

build a simple version first, test it, and improve it based on feedback. The textbook emphasizes that prototypes are essential tools for reducing risk and improving the final product.

Core Concept

What is a Prototype? A prototype can be: Physical: A model made of cardboard, clay, or 3D-printed materials Digital: A wireframe, mockup, or clickable app screen Functional: A working version with some features Non-functional: A visual representation only Why Prototypes Are Important The textbook explains that prototypes help: Test Ideas: See if the concept works1. Gather Feedback: Get input from users early2. Identify Problems: Find issues before full development3. Save Money: Avoid costly mistakes4. Save Time: Iterate quickly5. Communicate Vision: Show others what you are building6. Refine Design: Improve based on real use7. Types of Prototypes The textbook describes different types of prototypes: Low-Fidelity Prototypes1. High-Fidelity Prototypes2.

Detailed Explanation

1. Low-Fidelity Prototypes Definition: Low-fidelity prototypes are simple, rough, and quick to create. They focus on basic layout, structure, and flow rather than visual design. Characteristics: Simple materials (paper , cardboard, sketches) No or minimal interactivity Quick to make Cheap Easy to change Focus on concept, not details Examples: Paper sketches of a mobile app Cardboard model of a physical product Sticky notes arranged on a wall Simple wireframes Advantages: Fast to create Inexpensive Encourage feedback (people feel comfortable criticizing rough versions) Easy to discard and start over Disadvantages:

May not accurately represent final look Limited interactivity May miss details When to use: Early in the design process When exploring multiple ideas When you need quick feedback 2. High-Fidelity Prototypes Definition: High-fidelity prototypes are detailed, realistic, and close to the final product. They look and feel like the real thing. Characteristics: Detailed design Interactive Use real materials or software Close to final product More time and cost to create Examples: Clickable app prototype (using Figma, Adobe XD) 3D-printed working model Functional electronic prototype Detailed mockup with real colors and fonts Advantages:

Realistic user testing Accurate feedback Close to final product Can be shown to stakeholders Disadvantages: Time-consuming to create Expensive Harder to change May feel "finished" (people less likely to criticize) When to use: Later in the design process When testing specific features When presenting to stakeholders Before final development Comparison: Low-Fidelity vs. High-Fidelity Aspect Low-Fidelity High-Fidelity Detail Low High Cost Low High Time Fast Slow

Interactivity Minimal High Realism Low High Feedback Concept-level Detailed Ease of change Easy Difficult When to use Early Later The Role of Prototypes in Product Development The textbook places prototypes in the product development process: Idea Generation: Come up with ideas1. Prototyping: Build a model2. Testing: Test with users3. Refinement: Improve based on feedback4. MVP: Build Minimum Viable Product5. Launch: Release to market6. Prototypes are used in steps 2 and 3. Figure References The textbook references figures to illustrate prototypes (though specific figures are not described in detail here).

Intermediate Level

In product development, prototypes help teams learn and improve. Example: Developing a Mobile App Step 1: Low-Fidelity Prototype Sketch screens on paper Show to potential users Get feedback: "The login is confusing" Step 2: Refine Design

Improve login screen Sketch new version Step 3: High-Fidelity Prototype Build clickable prototype in Figma Test with users Get feedback: "The button is too small" Step 4: Refine Again Fix button size Test again Ready for development Prototypes help you catch problems early.

Important Points

• Prototype = preliminary version of a product.1.
• Used to test ideas, gather feedback, identify problems.2.
• Two main types:3.
• Low-Fidelity
• High-Fidelity
• Low-Fidelity: Simple, rough, quick, cheap (paper , sketches).4.
• High-Fidelity: Detailed, realistic, interactive, close to final.5.
• Low-Fidelity used early; High-Fidelity used later .6.
• Prototypes save time and money.7.
• Prototypes reduce risk.8.
• Prototypes improve final product quality.9.
• Prototypes are part of the product development process.10.

Remember

• Prototype = preliminary version
• Purpose: Test ideas, gather feedback, identify problems
• Types:
• Low-Fidelity (simple, rough, cheap)
• High-Fidelity (detailed, realistic, interactive)
• Low-Fidelity = early, concept-level
• High-Fidelity = later , detailed
• Benefits: Save time, save money, reduce risk, improve quality
• Process: Idea Prototype Test Refine MVP Launch
• Warning: Do not skip prototyping

Common Mistakes

• Skipping prototyping – Leads to costly mistakes.1.
• Starting with high-fidelity – Wastes time and money.2.
• Not testing with users – Misses real problems.3.
• Ignoring feedback – Defeats the purpose.4.
• Getting too attached – Hard to change when needed.5.
• Prototyping too long – Delays development.6.
• Not documenting – Loses learning.7.

Quick Revision

A prototype is a preliminary version or working model of a product. It is used to test and validate ideas, gather feedback, and refine the design before full-scale production. Prototypes help test ideas, gather feedback, identify problems, save money, save time, communicate vision, and refine design. There are two main types: low-fidelity prototypes (simple, rough, quick, cheap — paper sketches, cardboard models) and high-fidelity prototypes (detailed, realistic, interactive — clickable app prototypes, 3D-printed models). Low-fidelity prototypes are used early in the design process; high-fidelity prototypes are used later . Prototypes are an essential part of the product development process, reducing risk and improving the final product.

60-Second Revision

Prototype = preliminary version Purpose: Test ideas, gather feedback, identify problems Types: Low-Fidelity (simple, rough, cheap) High-Fidelity (detailed, realistic, interactive) Low-Fidelity = early, concept-level High-Fidelity = later , detailed Benefits: Save time, save money, reduce risk, improve quality Process: Idea Prototype Test Refine MVP Launch Warning: Do not skip prototyping Example: Paper sketch of an app (low-fidelity), clickable Figma prototype (high-fidelity)