A prototype is an early version of a product, system, interface, or solution that supports learning and evaluation.
Teams use it to explore ideas, clarify requirements, test feasibility, and collect stakeholder feedback. Therefore, it helps reveal misunderstandings before full development begins.
Low-fidelity versions may use sketches or wireframes. In contrast, high-fidelity versions may show realistic layouts, interactions, or selected functions.
An exploratory prototype supports requirements elicitation and shared understanding. Experimental versions test technical assumptions. Meanwhile, evolutionary versions may develop gradually into the final solution.
Teams should choose the level of detail according to the intended purpose. Moreover, they should explain limitations clearly. Otherwise, stakeholders may mistake an early version for a finished product.
The team should also decide whether to discard or extend the artifact after evaluation. As a result, expectations and development decisions remain clear.
Effective prototyping reduces uncertainty, improves requirements, and prevents costly rework.
« Back to Glossary Index