Prototyping

What is Prototyping?

A prototype is a tangible representation of an idea—an artifact you can interact with to assess whether a concept works as intended. Prototypes range from low-fidelity (sketches, wireframes, paper mockups) to high-fidelity (interactive digital mockups, functional prototypes that mimic the real interaction). The core value isn’t the artifact itself but the learning it enables: by making an idea concrete, you can test it with users, identify flaws early, and explore design alternatives before committing engineering resources.

Prototyping is a learning tool, not a production tool. A prototype that fails to teach you something has wasted time. The best prototypes are built to answer a specific question: Will users understand this interaction? Do they prefer option A or B? Is this navigation structure learnable? Purpose drives fidelity. If you’re testing whether users understand the concept, a low-fidelity sketch is sufficient. If you’re testing subtle interaction behavior, you may need higher fidelity.

Fidelity Levels: When to Stop Iterating

Low-fidelity prototypes (sketches, wireframes, paper models) are fast to create, easy to modify, and communicate intention without getting bogged in visual details. They’re best early, when you’re exploring problem space and design concepts. Users focus on structure and interaction rather than getting distracted by “why is the button gray?”

High-fidelity prototypes (pixel-perfect mockups, interactive simulations, functional prototypes) look like real products and test actual interaction behavior. They’re expensive to create but necessary when you need to validate subtle interaction patterns or measure task completion rates. The risk is premature commitment: a beautiful prototype is easy to fall in love with, making teams reluctant to change it based on testing feedback.

Prototyping as Conversation

The most underrated purpose of prototyping is internal: it makes vague discussions concrete. When a team debates navigation structure or workflow, sketching possibilities together resolves ambiguity faster than hours of discussion. The prototype becomes a shared language, and disagreements become testable: “Users prefer the left nav because…” becomes a hypothesis you can measure.

Why It Matters for Product People

Prototyping is how you fail cheaply. Testing a flawed concept with users costs hours and teaches you what’s wrong. Building the flawed concept in code costs days or weeks and teaches you what’s wrong after significant resource investment. Prototyping compresses the learning cycle.

For executives, prototyping is the bridge between strategy and execution. It lets you test strategic bets (is there really a market for this?) before green-lighting engineering investment. Prototyping also prevents the sunk-cost fallacy: if you’ve prototyped a concept and users reject it, you haven’t invested engineering time making it “real.”

Related Concepts

Prototyping feeds design sprints (time-boxed prototyping and testing cycles) and design thinking processes. Results inform hypothesis-driven development and A/B testing design. High-fidelity prototypes can become the basis for interaction specifications that guide engineering.