When Growth Starts Creating Complexity

UK manufacturers remain ambitious despite continued economic pressure. The Make UK Executive Survey 2026, produced with PwC, found that 68% plan to increase investment in new product development during the year, while 65% believe the opportunities available to manufacturers outweigh the risks.

Those figures point to continued confidence in product development as a route to growth. They also highlight a practical challenge for engineering leaders. New products continue demanding engineering attention long after the initial concept has been approved. Validation activity follows, while customer feedback and ongoing support requirements continue shaping the product long after its initial release.

The resulting workload does not always arrive with a corresponding increase in engineering capacity. Manufacturers continue to report skills shortages, while many also identify access to engineering talent as a barrier to wider technology adoption.

Product Ranges Rarely Become Simpler

A manufacturer may begin with a relatively focused range of products. The engineering team understands the designs, the reasoning behind previous decisions and the consequences of change.

That familiarity becomes harder to maintain over time. A product that began as a single design may evolve into multiple variants serving different customers or markets. Existing products remain in service while new developments move forward. Design decisions made years earlier continue to influence current projects.

Engineering work changes as product ranges expand. Engineers must work with more information and understand how products relate to one another. A modification that once affected a single design may now influence several related variants, increasing the amount of context needed before changes can be made confidently.

Growth Changes How Work Moves Through the Business

Team expansion can appear straightforward on an organisational chart. In practice, adding engineers changes how information, decisions and knowledge move through an organisation.

A small design team can rely heavily on direct conversation. Project history is usually understood by most of the people involved because they participated in the decisions. Questions are answered quickly because the context is easy to access.

As organisations grow, that becomes harder to sustain. A second site may begin contributing to the same products. New engineers arrive without the context that existing employees take for granted. Acquisitions can bring together capable teams that use different methods, standards and processes.

Work still progresses, but more effort is required to understand existing products, interpret historical decisions and maintain consistency across projects. Many of the resulting pressures are explored further in our article, Engineering Shouldn’t Feel This Difficult.

Why Capacity Becomes Harder to Scale

The impact of growth is rarely dramatic. A review takes slightly longer because more people need to contribute, while an engineer may spend part of the morning establishing which product variant contains a particular change. An experienced colleague is pulled into a discussion because the reasoning behind an earlier decision was never formally recorded.

Individually, these situations appear manageable. Repeated across multiple projects, they begin to consume a meaningful amount of engineering time.

Experienced engineers and engineering managers often feel the effect most strongly. The people responsible for delivering projects also become the people most frequently asked to explain existing products, support onboarding and provide historical context. Engineering capacity that could be directed towards development work is gradually absorbed by coordination activities.

At the same time, engineers are working with growing volumes of product information. Models, drawings, revision histories and supporting documentation all remain valuable because they capture decisions that continue to influence future work. Information is rarely missing. The difficulty is often the time required to locate it, understand its relevance and apply it effectively.

Industry Expectations Are Rising

Beyond the operational pressures created by growth, engineering organisations are also being asked to demonstrate greater control over development activity, product information and design decisions.

The UK Government’s Defence Investment Plan, published in June 2026, commits £298 billion of defence investment over four years and places considerable emphasis on digital capability, integrated systems and more sophisticated engineering programmes. The implications extend beyond defence primes and into wider supply chains, where expectations around traceability, design governance and engineering control are likely to become increasingly important.

The broader manufacturing market is moving in a similar direction. Manufacturers continue investing in product development and expanding into new opportunities, but growth brings additional engineering demands alongside it.

Most engineering organisations already have access to capable technology. Increasing attention is being paid to how effectively engineering teams can use that technology as products become more sophisticated and development activities become more demanding.

When Existing Systems Come Under Review

Reviews of engineering systems often follow a period of organisational change. An additional site may need to work on the same product range, or an acquisition may introduce different engineering practices into the business. Processes that worked effectively when teams were smaller can become harder to maintain as products, projects and engineering responsibilities expand.

These developments rarely indicate a fundamental problem. More often, they encourage engineering leaders to examine whether the environment supporting product development has evolved at the same pace as the business itself.

CAD platforms frequently become part of this discussion because they sit at the centre of product development activity. They influence how engineers create new work, access previous work and share information throughout the business. As organisations become larger, those systems often have a growing influence on consistency, collaboration and engineering effectiveness.

Some businesses respond by refining established processes. Others focus on making engineering knowledge easier to access or improving the way information is managed. In some cases, the discussion extends to a broader review of engineering systems, including CAD migration.

These decisions are typically driven by operational requirements rather than software features alone.

Preparing Engineering for the Next Stage of Growth

The outlook for UK manufacturing suggests that organisations will continue pursuing growth through product development and expansion into new markets.

Engineering capacity will play a significant role in determining how much of that ambition can be delivered. Recruitment remains important, but the effectiveness of a larger team depends on the environment into which those people arrive. Engineers need access to the information and context required to make informed decisions, while established knowledge needs to remain useful long after it was originally created.

By the time these discussions take place, the underlying causes are often familiar. The business has expanded, products have evolved and engineering teams are operating in a different environment from the one that existed only a few years earlier.

Recognising these patterns early allows engineering leaders to make informed decisions before growth begins placing unnecessary pressure on the teams responsible for delivering it.

The response will differ from one organisation to another. What remains consistent is the need to ensure that engineering capability and engineering capacity develop at the same pace as the business itself.

Related Reading

Engineering Shouldn’t Feel This Difficult: Why Companies Review Their CAD Systems

Considering a CAD Review?

Learn more about switching CAD systems

Explore Engineering Data Management