A prototype is an early, cheap version of a product built to answer a question before the real thing is made: will people understand it, want it, and can it be built? HCI researchers Stephanie Houde and Charles Hill (1997) argued that a prototype should be described by what it tests, its role in the user’s life, its look and feel, or its implementation, not by how polished it looks.
How prototyping works
Where you see it today
Design and AI tools now turn a written description into a working prototype. Figma introduced Figma Make in May 2025 as a prompt-to-app feature for generating high-fidelity prototypes, and Anthropic launched Artifacts in Claude in June 2024, which shows generated code or website designs in a window next to the chat.
Because AI makes a prototype cheap, teams can build several in parallel instead of one after another. A Stanford experiment found that novice designers who made several prototypes before feedback produced better-performing and more diverse web ads than those who iterated serially (Dow et al., 2010).
The Design Sprint, created by Jake Knapp at Google in 2010 and published as the book Sprint in 2016, compresses work into five days that end with a realistic prototype tested with real customers. Product and venture teams still use it to test an idea before committing a budget.
In Lean Startup practice, a minimum viable product is the first step of the build-measure-learn loop: a prototype released to learn from real behaviour. The risk in the AI era is mistaking a fast demo for a validated product.
Prototype types compared
How to use it
- Write the question the prototype must answer in one sentence before you build anything.
- Choose the lowest fidelity that can answer that question; polish invites feedback on the wrong things.
- Build two or three different versions in parallel and test them side by side.
- Watch at least a few real users try it, and record where they get stuck rather than what they say they like.
- Label every prototype as throwaway or evolving, so a demo is not shipped as a product by accident.
AI has pushed the cost of a working prototype towards zero, so the scarce skill is asking the right question and reading the test honestly. The Business Engineer view: the advantage moves from who can build a demo to who can turn many cheap experiments into a validated product.
Read: Is Vibe Coding Becoming Production Coding? →Explore everything we publish →Related: Minimum viable product · Design thinking · Design sprint · Rapid prototyping · Paper prototyping
Frequently asked questions
What is a prototype?
An early, simplified version of a product built to test an idea, a design or a technical question before the full product is made.
What is the difference between a prototype and an MVP?
A prototype tests a specific question and is often thrown away; an MVP is released to real customers to learn whether they will use or pay for it.
What are low- and high-fidelity prototypes?
Low-fidelity prototypes, such as sketches, test flow and understanding cheaply; high-fidelity prototypes look and behave like the real product and test feel and feasibility.
How has AI changed prototyping?
Tools such as Figma Make and Claude's Artifacts generate working prototypes from a prompt, so teams can test several versions quickly; the test still has to be run with real users.
Sources
- Houde & Hill (1997), What do Prototypes Prototype?, Handbook of Human-Computer Interaction
- Buchenau & Fulton Suri (2000), Experience prototyping, DIS 2000
- Dow et al. (2010), Parallel prototyping leads to better design results, more divergence, and increased self-efficacy, ACM TOCHI
- Figma (2025), Introducing Figma Make
- Anthropic (2024), Claude 3.5 Sonnet and Artifacts
- Knapp, Sprint: the Design Sprint (official site)
- The Lean Startup, Principles (official site)
The full guide
The complete explainer, cleaned up and reformatted for mobile.
A prototype is a sample version or simulation of a product that is used to evaluate a process or concept. The intention of creating a prototype is to test and validate ideas before they are communicated to stakeholders and ultimately, the product development team. Prototypes can be as simple as a storyboard sketch drawn on paper that captures the user experience or as detailed as a full-scale mock-up.
What makes up a prototype?
A fundamental reason for developing prototypes is their ability to pinpoint and solve user experience issues. Indeed, the involvement of end-users in the process allows UX teams to optimize the user experience as the product takes shape. This ensures that solutions can be implemented as required, which allows the company to avoid expensive last-minute fixes.
Prototypes must possess four core characteristics
- Interactivity – this describes the degree of functionality that is open to the user. For example, it may be fully functional, partially functional, or view-only. Good prototypes should also be able to carry out the functions of the product itself.
- Precision – a good prototype should have a precise shape, size, or material quantity. Precision is expressed as either low-fidelity (process simulations) or high-fidelity (realistic, working simulations).
- Representation – the prototype should also be a good representation of the design, not only in terms of appearance but also in the way the product works.
- Evolution (improvisation) – this describes the entire lifecycle of the prototype. Some are created and tested before being discarded and replaced with an improved iteration. Other prototypes may be created and successively improved upon over time to form the end product. The best prototypes are improvised with the least amount of effort.
How does prototyping work?
While exact procedures will vary from one organization to the next, there are three general steps to prototyping. These are discussed below:
- Prototype – the team starts by building a visual and functional prototype based on requirements set forth by the client. User experience and design best practices are both considered at this stage.
- Review – here, the developers share the prototype with their teams and evaluate it according to how well it satisfies the needs of the client. The prototype is then shared with the client who may provide additional feedback to the team’s initial evaluation.
- Refine – when feedback is provided, the developers can then set about improving or refining various aspects of the prototype.
Note that there is a common misconception that the process only needs to be completed once or twice and at the end of the design process. Depending on the complexity of the design, the team may be required to cycle through four or five prototyping sessions or continue to iterate until all stakeholders are satisfied.
Examples And Case Studies
- Software Development:
- Creating a clickable interactive mock-up of a mobile app to test user flows and functionality before actual development.
- Building a rough wireframe of a website’s layout and navigation to visualize the structure before designing and coding.
- Product Design:
- Automotive Industry:
- Architecture:
- Creating a detailed physical scale model of a building to understand its spatial layout and aesthetics.
- Using computer software to generate a 3D virtual prototype of a planned urban development to simulate traffic patterns and public spaces.
- Fashion Design:
- Industrial Manufacturing:
- Crafting a functional prototype of a new machinery component using 3D printing to test its performance under stress.
- Developing a prototype of a new consumer electronics device to check its functionality and user interface.
- Electronics:
- Building a breadboard prototype of a new electronic circuit to test its functionality before designing a printed circuit board (PCB).
- Creating a 3D-printed enclosure prototype for a new IoT device to assess its form and functionality.
- Medical Devices:
- Developing a prototype of a new medical instrument to evaluate its ergonomics and usability by healthcare professionals.
- Crafting a functional prototype of a prosthetic limb to ensure proper fit and range of motion.
- Game Development:
- Creating a playable prototype of a video game level to test mechanics, controls, and overall gameplay.
- Building a physical prototype of a board game to playtest rules, balance, and player engagement.
- Space Exploration:
- Constructing a prototype of a new space vehicle’s heat shield to test its ability to withstand re-entry temperatures.
- Developing a scaled-down model of a satellite to simulate its deployment and orbital behavior.
Key takeaways
- A prototype is a sample version or simulation of a product that is used to evaluate a process or concept. Prototypes help teams pinpoint and solve user experience issues earlier in the process and avoid expensive fixes later on.
- A prototype possesses four main characteristics: interactivity, precision, representation, and evolution (improvisation).
- Prototyping involves a three-step process where teams develop a prototype, seek client feedback, and then refine the prototype according to that feedback. The process should be repeated multiple times, particularly for more complex products.
Key Highlights
- Prototype Definition: A prototype is a sample version or simulation of a product created to evaluate and validate concepts and processes. Its purpose is to identify and address user experience issues before involving stakeholders and the product development team.
- Prototyping Characteristics:
- Interactivity: Prototypes vary in their degree of functionality, from fully functional to partially functional or view-only. Good prototypes should allow users to interact with the product’s functions.
- Precision: Prototypes should exhibit precise dimensions, sizes, or material quantities. This precision can range from low-fidelity process simulations to high-fidelity, realistic, working simulations.
- Representation: A prototype should accurately represent the product’s design, appearance, and functionality.
- Evolution (Improvisation): Prototypes can undergo iterative development. They might be tested and discarded, or progressively improved to eventually become the final product. Effective prototypes are improved with minimal effort.
- Prototyping Process:
- Prototype: The process starts with creating a visual and functional prototype based on client requirements, considering user experience and design best practices.
- Review: The prototype is evaluated by the development team to assess how well it aligns with client needs. Client feedback is collected and considered as well.
- Refine: Based on the feedback received, the prototype is refined and improved. The cycle of feedback and refinement can be repeated several times.
- Complexity and Iteration:
- Prototyping is not a one-time process and may involve multiple iterations, especially for complex designs.
- The misconception that prototyping happens only at the end of the design process is incorrect. Iterative prototyping helps refine the product over time and align with stakeholder expectations.









