Definition
A preliminary model of a product or feature used to explore ideas and test assumptions before building production code. Prototypes range from low-fidelity paper sketches to high-fidelity interactive mockups in tools like Figma. PMs use prototypes to gather early user feedback, reduce development risk, and communicate intent to stakeholders more effectively than specifications alone.
Why It Matters for Product Managers
Understanding prototype is critical for product managers because it directly influences how teams prioritize work, measure progress, and deliver value to users. PMs use prototypes to gather early user feedback, reduce development risk, and communicate intent to stakeholders more effectively than specifications alone. Without a clear grasp of this concept, PMs risk making decisions based on assumptions rather than evidence, which can lead to wasted engineering effort and missed market opportunities.
How It Works in Practice
In practice, product teams apply this technique during the discovery phase of product development:
Effective use of prototype prevents teams from building features based on assumptions and ensures that investment flows toward validated user needs.
Common Pitfalls
Related Concepts
To build a more complete picture, explore these related concepts: Design Sprint, Usability Testing, Fake Door Test, and Wizard of Oz Test. Each connects to this term and together they form a toolkit that product managers draw on daily.