Beyond Mockups: What to Build Before You Build

Hardware teams have four distinct validation instruments — proof of concept, mockup, prototype, and pre-production unit — each designed to answer a different question. The discipline is matching the right instrument to the right question, and understanding what each one can and cannot prove.

In a warehouse outside Zaragoza, a team of engineers at CAF (Construcciones y Auxiliar de Ferrocarriles) — a Spanish manufacturer of railway vehicles, equipment, and buses — spent nearly a year building a single railroad car. That car would never carry a passenger. The million-euro mockup was created for a single purpose: to let a focus group of Dutch commuters sit in the seats, plug into the sockets, and judge the sightlines before Nederlandse Spoorwegen committed billions to a fleet order.

A million euros may sound like a lot for a dummy. It is — but it’s a rounding error on a multi-billion-euro fleet order. More importantly, what that mockup delivers — direct evidence of user acceptance — is something no brochure, specification document, or rendering can deliver reliably.