MVP vs EVT
also: minimum viable product · MVP · prototype vs production
An MVP tests whether customers want the product; EVT tests whether a production-intent design works. Mixing them up wastes tooling or ships prototypes.
In software, an MVP can ship and be improved weekly. In hardware, the equivalent learning usually comes from prototypes, pilots, pre-orders and hands-on trials long before production-intent engineering. Engineering validation (EVT) is a different milestone: proving that a design intended for manufacturing meets its requirements.
Rushing into EVT before the core value is validated risks spending on tooling and certification for a product that will need to change. Staying in prototype mode too long, or shipping prototypes as products, risks reliability, safety and certification problems in customers' hands.
A common path is to validate demand and core function with works-like and looks-like prototypes and small pilots, freeze the requirements, then begin EVT.
Founder takeaway
Validate the problem, the price and the core function with prototypes and pilots before committing to production-intent EVT design.
engineer review pending