Loading content
Rapid prototyping enables quick, iterative creation of tangible mockups and minimal prototypes to validate assumptions early. It focuses on fast user and stakeholder feedback, reduces uncertainty and supports focused decisions in product and development processes. The method is practical, cross-disciplinary and well suited for discovery phases.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Rapid prototyping is a fast, repeatable way to turn an idea into a tangible model, test it with people, and improve it through feedback.
Rapid prototyping grew from prototyping in software and product development. The practice combines early design models with short learning loops; ISO 9241-210 places prototyping within human-centred design.
Treat the prototype as a learning instrument: state the uncertain assumption, build only enough surface or behaviour to test it, observe use, then decide whether to discard, change, or deepen it. Speed comes from constrained scope and short feedback, not from skipping the important question.
The prototype needs only the realism required by the current question.
An explicit assumption defines what the prototype should help learn.
Feedback leads to a deliberate change, discard, or next test.
Rapid prototyping reduces the risk of turning unclear needs into expensive implementation. It fits interactions, workflows, and technical feasibility, provided findings are recorded and prototypes are not mistaken for production-ready quality.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.