earlyprototype

Early prototype is the initial version of a product or system created during the early stages of development to explore ideas, test core functionality, and reduce technical and usability risks. It is typically not a finished product and may use simplified materials or software just enough to demonstrate concepts. Early prototypes are often low fidelity, focusing on essential interactions and flows rather than aesthetics or performance.

Different forms exist. Throwaway or experimental prototypes are built to learn and are later discarded or heavily revised; evolutionary prototypes are designed to be refined into the final product. In software, early prototypes may be interactive mockups or working code with limited features. In hardware, they may be breadboards, simple 3D-printed enclosures, or early PCB designs.

The primary purposes include validating requirements, testing user experience, assessing feasibility, communicating ideas to stakeholders, and guiding subsequent design decisions. The development process is typically iterative: define objectives, build a representation, test with users or technical staff, analyze results, and revise.

Limitations include the risk that low fidelity leads to misinterpretation of final capabilities, or that early decisions constrain later design. Mitigation strategies emphasize documenting learning, clarifying which features are settled versus tentative, and planning staged prototyping with increasing fidelity.

Historically, prototyping has long been part of engineering and product development. In software and systems engineering, formal prototyping methods gained prominence in the late 20th century as a way to manage uncertainty and user requirements, evolving into agile practices and approaches such as minimum viable products.