News & Insights

Weak execution rarely looks catastrophic in the beginning. It looks administrative.

In Parts 1 through 3 of this series, the panel at MedTech World North America 2026 explored how protocol design, regulatory strategy, and enrollment planning can derail medical device timelines.

But according to veteran quality expert Mark Swanson, many delays are not caused by dramatic failures. They are caused by operational weaknesses that compound quietly over time.

Part 4 of What Breaks MedTech Timelines specifically focused on execution:

• quality systems

• documentation

• CRO oversight

• operational infrastructure supporting clinical trials

• 
  

The discussion featured:

• Mark Swanson, medtech quality and ISO expert with more than 25 years in quality systems and risk management

• Lian Cunningham, VP of Clinical Affairs at Endogenex

• moderated by Joseph Panetta, Ascend Clinical Research Fractional Chief Marketing Officer

“If It’s Not Documented, It Didn’t Happen”

One of the strongest moments in the panel came when Swanson described the role documentation now plays in modern medtech development.

His point was direct: “If it’s not documented, it didn’t happen.”

That statement reflects a growing reality in medical device clinical research: good intentions and verbal explanations are no longer enough.

Regulators increasingly expect:

• searchable electronic documentation

• traceable development history

• risk management files

• integrated quality systems that connect design, clinical, and operational execution

  
  

And importantly, these systems cannot be built retroactively once problems appear.

Quick takeawayModern clinical execution is inseparable from documentation quality. If your systems are disorganized, your timelines will be too.

Quality Systems Are Not Just for Manufacturing

Many startups still associate quality systems primarily with manufacturing readiness. The panel pushed back strongly on that misconception.

According to Swanson, quality systems now underpin nearly every aspect of clinical execution:

• supplier controls

• CRO oversight

• document management

• risk management

• protocol execution

• regulatory response readiness

  
  

Without those systems:

• sites may hesitate to participate

• regulators may slow review

• sponsors may struggle to answer basic operational questions during submissions

  
  

As Swanson explained, quality systems are what allow organizations to respond quickly when regulators inevitably ask for clarification. And they always do.

Quick takeawayWeak QMS doesn’t just create compliance risk. It slows every operational response around the trial.

CRO Oversight Is Part of the Sponsor’s Responsibility

Another important discussion centered around CRO expectations. Many early-stage CEOs assume that once a CRO is hired, operational responsibility largely transfers to the vendor.

Our panelists challenged that thinking.

Swanson noted, CROs themselves are suppliers and must be actively managed within the sponsor’s quality system.

That includes:

• oversight

• documentation standards

• communication pathways

• performance accountability

The discussion also highlighted an important distinction between:

• large global CROs

• smaller regionally embedded organizations with deeper local operational knowledge

Operational execution is often determined by details not visible on paper:

• site responsiveness (local relationships help!)

• coordinator turnover

• investigator bandwidth

• local startup/regulatory realities

• internal knowledge (the kind of knowing one has from being ‘on the ground.)

Those nuances can significantly affect timelines.

Quick takeawayHiring a CRO does not eliminate sponsor responsibility. Execution still requires active operational oversight.

The Problem With “Stage-Gate Thinking”

One of the more subtle but important points raised during the discussion was the danger of overly linear development thinking.

Swanson argued that many device companies approach development through rigid “stage gates”:

• finish one task

• move to the next

In reality, modern medtech development requires overlapping systems:

• clinical

• regulatory

• quality

• reimbursement

• operational planning

All must evolve together in a holistic, interconnected way.

When companies wait too long to build infrastructure, delays become difficult to unwind later.

As Panetta summarized throughout the session: clinical execution is not a collection of isolated activities. It is an interconnected and interdependent system.

The Bigger Lesson

Most execution failures do not begin with dramatic mistakes. It’s more like death by a thousand cuts. They begin with:

• weak documentation

• delayed infrastructure

• poor oversight

• fragmented systems

• assumptions that operational rigor can be added later (note- it cannot!)

By the time those weaknesses become visible, timelines are already slipping.

And unlike protocol amendments or enrollment issues, operational failures tend to compound silently in the background until regulators, sites, or auditors force them into the open.