Prototyping is the creation and evaluation of an early, simplified version of a product, system, or solution.
Teams use sketches, mock-ups, simulations, physical models, or software builds. Therefore, they can explore ideas before full development begins.
First, the team defines the questions that the artifact should answer. Next, it selects a suitable level of detail. Then, users and stakeholders test the result and provide feedback.
Low-fidelity artifacts support fast exploration at low cost. In contrast, high-fidelity versions can test realistic interactions, technical feasibility, performance, or integration.
Effective prototyping requires teams to document findings, decisions, open questions, and revised requirements. Moreover, they should build only the elements needed for the investigation. Otherwise, unnecessary detail increases effort and may create false expectations.
The team may discard the artifact after evaluation or develop it further. As a result, the chosen approach should match its purpose and planned lifecycle.
This method supports early learning, clearer requirements, evidence-based decisions, and reduced development risk.
« Back to Glossary Index