Many product development efforts end in outcomes no one chose: warranty failures, certification delays, fragile supply chains, environmental burdens — each surfacing after the design has been frozen and is costly to change. What is missing is not methods but structure. Existing frameworks address fragments of the problem: the V-model secures traceability, Design-for-X methods cover individual design dimensions, and set-based concurrent engineering identifies premature convergence as a driver of late rework. None provides a sequence for the full set of design dimensions, each at the moment it can still shape the design. This paper introduces the 360° Product Development Model, in which nine recognised design disciplines are organised as viewports around a shared baseline, across five lifecycle phases. The sequence in which they contribute is not a matter of choice, but emerges from their dependencies: each contributes once its prerequisites are known, and before the decisions that depend on its knowledge are made. Each phase concludes with a baseline lock that stabilises the shared knowledge state before the next iteration begins. The model does not replace existing methods; it gives each its moment. The model makes visible how the decisive choices are so often settled by default, filled in by whichever viewport drew the design space first rather than chosen in view of the rest. It offers a mechanism for preventing premature convergence, and makes a falsifiable prediction: where a viewport is engaged before the viewport it depends on, the conflict arises between exactly those two.
No takes yet. Share an insight, caveat, or question.
Wouter Hagedoorn (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: