Signs that internal capacity is stretched, and what to do about it
The project was supposed to take six months.
Nine months later, everyone is still working hard. Meetings are full. Calendars are packed. The team is capable, experienced and committed.
But the programme still isn’t moving quickly enough.
Sound familiar?
When development slows, the instinct is often to look at the process.
Do we need better project management? More agile working? Another stage-gate review? More accountability?
Sometimes.
But there is another explanation that MedTech leaders should consider.
Your team isn’t slow. It’s overloaded.
And there is an important difference.
The pressure on MedTech development teams is growing
Medical device development has never been straightforward. But the demands on R&D organisations are increasing.
According to McKinsey’s 2025 analysis, MedTech R&D spending is growing by approximately 10% annually, while average development timelines now exceed four years.
The same research highlights increasing technical complexity, the growing importance of digital technologies and the need for new skills and organisational structures.
Source: McKinsey, Talent, tech, and team: The formula for medtech R&D success, July 2025. [1]
Meanwhile, Deloitte’s 2026 MedTech outlook highlights an industry balancing rapid innovation, portfolio restructuring and continuing pressure to improve operating efficiency. [2]
For development leaders, the challenge is clear.
Deliver more innovation, manage greater complexity and do it without allowing costs or timelines to spiral.
But what happens when the organisation simply doesn’t have enough capacity?
Busy isn’t the same as productive
MedTech development teams rarely work on one thing at a time.
They are supporting existing products. Managing regulatory changes. Resolving quality issues. Working with manufacturing. Responding to commercial requests. Supporting customers. Investigating new technologies.
And somewhere amongst all of that, they are expected to create the company’s next generation of products.
McKinsey’s Medtech Pulse research identifies effective portfolio management, empowered product teams, systems engineering and access to external innovation networks as important contributors to R&D performance. [3]
The implication is important.
Improving development productivity isn’t simply about asking engineers and designers to work harder.
It is about how development resources are organised, prioritised and deployed.
Ask yourself:
How much uninterrupted time does your core development team actually spend developing?
And how much is consumed by keeping everything else moving?
Five warning signs your team is overloaded
Overloaded teams don’t necessarily look dysfunctional.
In fact, they can look highly productive.
Everyone is busy. Everyone has actions. Everyone is attending meetings.
But the warning signs appear elsewhere.
1. Development milestones keep moving
Projects rarely stop completely. They just progress more slowly than expected.
A two-week delay becomes a month. A missed decision pushes back prototyping. Testing is rescheduled because a specialist is unavailable.
2. Your most experienced people become bottlenecks
The same senior engineers, designers and technical specialists are needed across multiple programmes.
Their expertise is valuable, but their availability becomes the limiting factor.
3. Innovation repeatedly loses to operational priorities
A manufacturing issue, regulatory change or customer requirement demands immediate attention.
The next-generation product can wait.
Until next month.
And then the month after.
4. Decisions take longer than the technical work
Teams spend more time coordinating resources, securing approvals and navigating competing priorities than resolving the underlying development challenge.
5. Good ideas remain permanently on the development roadmap
The opportunity is recognised.
The commercial case looks promising.
But nobody has the capacity to investigate it properly.
How many of these signs would your development organisation recognise?
The hidden cost isn’t just delay
The visible cost of an overloaded team is slower development.
The less visible cost is the innovation that never happens.
A promising technology isn’t investigated.
A new product concept never reaches prototype.
An acquired product portfolio isn’t rationalised.
A potentially valuable market opportunity is missed because internal resources are committed elsewhere.
McKinsey’s research into MedTech value creation highlights the importance of R&D productivity, effective portfolio management and disciplined development execution in creating commercial value. [4]
The challenge isn’t necessarily that organisations are investing too little in R&D.
It is whether that investment is being directed towards the right opportunities and converted into commercially valuable products.
What is the opportunity cost of the programmes your organisation never starts?
And perhaps more importantly, does anyone actually measure it?
Hiring more people isn’t always the answer
When development capacity becomes constrained, recruitment seems the obvious solution.
But permanent headcount isn’t necessarily the right answer to a temporary or specialist requirement.
Finding experienced MedTech engineers, industrial designers, human factors specialists and digital development expertise can take time.
New employees need onboarding, management and integration into existing processes.
And the skills required during early innovation may be very different from those needed during verification, validation or manufacturing transfer.
McKinsey’s 2025 research identifies access to talent, multidisciplinary collaboration and flexible organisational structures as important factors in successful MedTech R&D. [1]
Sometimes the answer isn’t simply adding more people to an already stretched organisation.
Sometimes it is creating dedicated capacity outside the day-to-day demands of the business.
Create protected innovation capacity
Imagine taking one strategically important development challenge and giving it to a small, experienced multidisciplinary team.
A team with a clear commercial objective.
Access to the right internal experts.
And the capacity to focus.
Rather than competing continuously with operational priorities, that team can investigate unmet needs, challenge assumptions, develop concepts, build prototypes, test with users and resolve technical uncertainty.
McKinsey’s Medtech Pulse report specifically identifies engagement with external innovation networks as one of the characteristics associated with stronger R&D performance. [3]
The opportunity is not simply to outsource more work.
It is to use external expertise selectively to create momentum where internal capacity is constrained.
Consider the possibilities.
Could a new product concept be explored without diverting your core engineering team?
Could a feasibility programme run in parallel with an existing development project?
Could specialist design or human factors expertise be brought in precisely when required?
Could an early-stage programme progress far enough to support a confident investment decision before significant internal resources are committed?
What would become possible if your most important innovation programmes had protected development capacity?
External doesn’t have to mean disconnected
One legitimate concern about external development partners is the risk of creating a disconnected team.
A consultancy disappears for three months and returns with an elegant concept that doesn’t fit the company’s technical, regulatory or commercial requirements.
That isn’t an effective model for MedTech innovation.
Medical device development requires coordination across engineering, quality, regulatory, clinical, manufacturing and commercial disciplines.
The FDA’s guidance on human factors and usability engineering reinforces the importance of integrating user needs, intended use and risk considerations throughout device development. [5]
Its guidance on design and development documentation also highlights the importance of structured development activities and appropriate documentation within medical device quality management systems. [6]
The most effective external development model therefore combines two things.
Integration with the organisation’s technical, regulatory and commercial requirements.
And:
The independence and protected capacity to challenge assumptions, explore alternatives and maintain development momentum.
External teams should complement internal expertise, not attempt to replace it.
What should you keep inside?
This isn’t an argument for outsourcing product development indiscriminately.
Your internal team holds critical institutional knowledge, technical history, regulatory understanding and long-term product strategy.
Those capabilities remain essential.
But does your organisation need to maintain every specialist capability internally?
Should your senior engineers be spending their time investigating early-stage concepts when they are also responsible for critical product programmes?
Could selected innovation activities be progressed more effectively by a dedicated external team?
The objective is to use internal expertise where it creates the greatest strategic value, while accessing external capacity where it can accelerate progress.
The question therefore isn’t:
“Should we outsource development?”
A better question is:
“Which programmes would move significantly faster if our internal team didn’t have to carry the whole load?”
Give good teams room to perform
When talented teams start missing milestones, the answer isn’t always to push harder.
Sometimes leaders need to examine the system around them.
How many programmes are running simultaneously?
How fragmented is specialist resource?
How much development time is consumed by sustaining engineering and operational demands?
Which strategically important programmes are repeatedly deprioritised?
And what opportunities aren’t even being investigated because everyone is already at capacity?
At Maddison, we work alongside MedTech organisations to provide focused innovation and development capacity when strategically important programmes need to move.
Combining industrial design, engineering, human factors and commercial thinking, we help teams investigate opportunities, resolve development challenges and turn promising ideas into viable products.
Not to replace internal teams.
To give them room to perform.
Because sometimes the fastest way to accelerate innovation isn’t to make your team work faster.
It’s to stop asking them to do everything.
Maddison
Design That Means Business.
References
[1] McKinsey & Company (2025).
Talent, tech, and team: The formula for medtech R&D success. 24 July 2025.
Research examining increasing R&D complexity, development timelines, talent requirements and organisational effectiveness.
[2] Deloitte (2026).
Three Key Trends Likely to Shape Medtech in 2026. 25 January 2026.
Industry outlook examining portfolio restructuring, innovation priorities, margin pressures and operational efficiency.
[3] McKinsey & Company (2023).
Medtech Pulse: Thriving in the Next Decade.
Industry research examining R&D productivity, portfolio management, organisational effectiveness and external innovation networks.
[4] McKinsey & Company (2024).
Medtech Value Creation: The New Priority.
Analysis of the relationship between development productivity, operational performance and commercial value creation.
[5] US Food and Drug Administration (2026).
Applying Human Factors and Usability Engineering to Medical Devices. Final guidance, August 2026.
Recommendations for integrating human factors and usability engineering into medical device development.
[6] US Food and Drug Administration (2026).
Human Factors: Premarket Information, Device Design and Documentation Processes.
Information on medical device design and development requirements, quality management systems and human factors documentation.