Driving complex engineering product development to market requires a holistic, effective way to track progress and hold strategic alignment throughout the entire programme lifecycle and its delivery milestones.
As discussed in a previous instalment, new product development (NPD) refers to the complete process of bringing a new product or service to market — from upfront product-line or service-platform strategy, business analysis, and marketing, all the way through to commercialisation, maintenance, and operations. It is a delivery framework for guiding work and setting operational and financial boundaries across a project or programme, bringing consistency and integrity across quality, schedule, and cost.
The ability to plan, forecast, and measure progress is a critical success factor — it's what allows teams to course-correct and realign people, resources, processes, data, and enabling tools through successive planning iterations. Hass (2008) recommended particular attention to planning and structuring for large, long-duration projects: selecting the appropriate management approach, progressively elaborating the plan, using a systemic and reliable estimating method, performing rigorous time and cost management, using stage-gate management, and conducting thorough risk management.
While there is no correct number of milestones or duration between them, they lose value when there are too many or too few [...] there should be enough milestones at major intervals to gauge whether or not the plan is proceeding as expected.PRINCE2 project management methodology
This article elaborates on the purpose and effectiveness of key milestone delivery and associated NPD governance when driving complex engineering programmes.
NPD aims to drive dynamic organisational design, fit-for-purpose and effective activity management to foster collaboration and innovation, while minimising cost and shortening development times. The ability to tailor and adapt the delivery framework to the type of project is essential to purposely align the associated delivery, engagement, and commercial models with business and product development strategies.
Tailored NPD strategy
Tailoring means adapting to a specific context — primarily to ensure effectiveness (doing the right thing) and efficiency (doing it right). According to Wheelwright and Clark (1992): "Few development projects fully deliver on their early promises [...] In some instances, poor leadership or the absence of essential skills is to blame. But often problems arise from the way companies approach the development process. They lack what we call an aggregate project plan." To understand specific resource-requirement patterns, they divided development projects into five types:
- Derivative
- Breakthrough
- Platform
- Research and development (as a precursor to commercial development)
- Alliance and partnership driven projects
Managing and implementing change covers at least two core dimensions: "the degree of change in the product and the degree of change in the manufacturing process" (Wheelwright and Clark, 1992). Add to that the ability to drive new technology development, new infrastructure requirements, new legislation adoption, new sourcing models, new funding models, and new market introduction. There is no silver bullet in project or programme management — a fortiori when the initiative is complex.
In turn, NPD drives new core-process definition, continuous improvement, and both transformational and incremental change through the implementation of new delivery platforms and tools, coupled with the ability to shift the organisation and forge its long-term operating culture.
Stage-gate management
Delivery milestones are typically associated with development gates. These combine managerial decisions into a single event — the objective being to assess progress against performance targets and to make a call on project continuity. The framework includes elements of control across the NPD structure and its enabling processes, and is often linked to investment and delivery-payment milestones with the supply chain.
As Varandas et al (2017) highlighted, "although those NPD structures encompass a graphic representation of linear stages, most of them are cyclical with loops and feedback in the information flow." Modern NPD frameworks embed the ability to enhance management practices, consider the entire product lifecycle, introduce support tools, align organisational strategy with NPD, integrate the supply chain and customers into the process, analyse the implications of knowledge management, improve information flow, define clearer responsibilities, and provide decision support.
Each gate links to specific outputs — deliverables, decisions, acceptance criteria — against stakeholders and decision makers. A gate is not meant to be a rigid, purely functional review; cross-functional activities and outputs rarely reach maturity at the same time. Each combined phase and stage-gate is a guiding map from point A to point B, with levels of flexibility that are continuously reviewed and acknowledged as part of the governance.
Gateway countdown process
Gate and phase sequencing typically follows the product development "V-model", leveraging model-based systems engineering (MBSE) principles to define, cascade, and deliver outputs against product attributes and the enterprise architecture — from requirements through functional, logical, and physical outputs.
Data is released as the product matures. This is typically reflected in the NPD framework as decision points triggering other activities (purchasing, corrective actions, change actions, manufacturing, re-engineering). Data exchange and output verification is ongoing, while final validation is often driven through a formal gateway review process.
Approaching a programme gate should drive the right behaviours. Gateway countdown processes become highly ineffective when they are time-constrained and carry a heavy bureaucratic burden — especially when they don't clearly link to day-to-day activities and governance. Gateway governance and operational governance need to be closely integrated to give teams an ongoing line of sight to strategic objectives and how they're being measured.
Data-management experts often recognise the inefficiencies in driving mass data-maturation activities: they imply a "hockey stick approach" to releasing — frequently most prominent when approaching a gateway. Hence the importance of defining:
- Clear maturity targets and acceptance thresholds throughout the phase, not just at the culminating gate.
- Clear accountability and people empowerment to drive those targets, in collaboration with other delivery functions and suppliers.
- Robust continuous-review governance and data-driven decision criteria — continuously managed and updated (not static, but allowing flexibility and agility).
- Clear data visibility and traceability, toward a robust "plan for every part" and its associated delivery interdependencies.
- A fit-for-purpose digital roadmap to select and implement the technical automations and tools that support that complexity management.
In essence, the above is what product lifecycle management (PLM) is about: end-to-end change traceability, accountability, strategic alignment, and continuous delivery improvement — covering not just the enabling tools and processes, but the people, the collaborative structure, and the governance driving relevant data output and organisational maturity alignment.
Combined gate validation and review processes produce the essential artefacts to sign off overall development efforts — marking the fact that the organisation is progressing against the right pace, quality, and cost expectations. Business analytics, traffic-light status, and management by exception drive the ongoing corrections and adjustments toward that goal. What are your thoughts?
References
Varandas A, Miguel AP, Salerno MS (2017); New product development: examining its evolution and the introduction of environmental issues; Product Management and Development, 15(1): 8-19.
OGC (2009); Managing Successful Projects with PRINCE2, 5th Edition; The Stationery Office Ltd.
Hass KB (2008); Managing Complex Projects: A New Model; Management Concept Press.
Wheelwright SC, Clark KB (1992); Creating Project Plans to Focus Product Development; HBR. https://hbr.org/1992/03/creating-project-plans-to-focus-product-development
