Why MedTech’s Most Critical Leadership Gap Is Getting Harder to Ignore
Engineering expertise and regulatory accountability almost never sit in the same person. In 2026, a new FDA inspection framework is making that gap visible in ways it wasn’t before.
The FDA began conducting inspections under a fundamentally new framework on February 2, 2026. If your quality management system was built without serious engineering input, or if your engineering and regulatory functions have been operating in separate lanes, that is no longer a background risk. It is a current exposure.
Medical device companies tend to have strong engineers. Many also have capable regulatory and quality professionals. What is genuinely rare is someone who has held real accountability in both domains at the same time—not as an advisor to each side, but as the person whose name is on the engineering decisions and the QMS outcomes simultaneously. That combination is hard to build. It is also easy to undervalue, right up until an inspection reveals exactly where the gap was sitting.
Why the Two Paths Almost Never Converge
Career development in MedTech separates early. Engineers go deep into systems architecture, hardware, firmware, verification and validation, and manufacturing. Regulatory and quality professionals develop expertise in standards interpretation, QMS design, submission strategy, and inspection readiness. Both take years of focused work to build real competency, and neither is a shortcut to the other.
Organizational structure reinforces that separation. In most device companies, engineering and quality/regulatory report to different executives, are evaluated against different outcomes, and rarely sit in the same leadership conversations. That is not a design flaw. It is a practical response to the depth each discipline requires. But it does create a structural gap that produces costs in specific, predictable ways.
The workforce data reflects how persistent the underlying shortage is. A 2025 MedTech workforce analysis found that clinical and regulatory expertise remains in critical shortage across the industry, with limited candidate pools creating real bottlenecks in product approvals and inspection timelines.¹ A separate 2025 quality industry report identified shortfalls in experienced quality engineers as a direct contributor to delays in compliance activities, audits, and device clearance.² What neither study captures is the more specific shortage of professionals who can operate credibly across the engineering and regulatory boundary at the same time. That is the gap that tends to go unquantified until something forces it into view.
Why 2026 Changes the Calculation
The FDA’s Quality Management System Regulation (QMSR), effective February 2, 2026, replaces the legacy Quality System Regulation by incorporating ISO 13485:2016 by reference.³ On its surface this is a harmonization exercise. In practice it materially changes what an FDA inspection examines, and that change has direct implications for organizations where engineering and regulatory are not well integrated.
The QMSR inspection framework, operationalized through Compliance Program 7382.850 effective February 2, 2026,⁵ replaces the legacy Quality System Inspection Technique (QSIT).⁴ The differences are not cosmetic:
Dimension Legacy QSIT Approach New QMSR / CP 7382.850 Approach
(withdrawn Feb 2, 2026) (effective Feb 2, 2026)
Inspection Four discrete subsystems: Total Product Lifecycle (TPLC): investigators
structure Management Controls, Design follow risk across all interconnected
Controls, CAPA, Production processes—no subsystem walls
& Process Controls
Primary Procedures and records reviewed Risk-based decision-making embedded in
evidence within each subsystem boundary how the organization actually operates
—documentation-driven functions
Cross-functional Disconnects between QMS documentation Functional silos are explicitly exposed—the
exposure and engineering/manufacturing practice lifecycle follow-through surfaces gaps
were rarely surfaced—inspectors stayed between documented procedures
within subsystem lanes and actual practice
Management Management review records checked for Management must be an active participant
role completeness; compliance largely in risk-based approvals at process
delegated to quality function transitions—not just a signatory
Risk language The word “risk” appeared once in the The word “risk” appears more than 25 times
old QSR under section 820.30(g) in ISO 13485:2016—evidence of risk-based
thinking throughout operations is required
Two implications stand out. First, management can no longer treat compliance as something delegated entirely to the quality function. Second, the new framework is explicitly designed to expose functional silos. An inspection that follows the product lifecycle will surface disconnects between what the QMS describes and what engineering and manufacturing actually do.⁶ To put a number on the shift: the word “risk” appears more than 25 times in ISO 13485:2016, compared to once in the old QSR under section 820.30(g).⁷ The standard is not asking for more paperwork. It is asking for evidence that risk-based thinking shapes how the organization actually makes decisions.
What the Gap Actually Costs in Practice
FDA warning letters, consent decrees, and failed 510(k) submissions carry real financial consequences. Consent decrees in the device industry have resulted in manufacturing shutdowns lasting years, with remediation costs that routinely reach into the tens of millions of dollars. Warning letters have delayed product launches and triggered stock impacts for publicly traded companies. These outcomes share a common thread: a quality system that did not accurately reflect what the organization was actually doing, and a gap between engineering reality and regulatory documentation that was allowed to compound.
The five failure modes below come up consistently in complex device programs, particularly those involving multi-domain Class II devices with significant supplier integration. Each is predictable once you know what to look for:
Failure Mode What It Looks Like What It Costs
Engineering and Schedule pressure silently defers The gap accumulates quietly until an
Regulatory Answer compliance obligations. Documentation inspection surfaces it—correcting it after
to Different Priorities drifts from engineering reality. the fact is considerably more
QMS grows progressively inaccurate. expensive than preventing it.
QMS Documentation Procedures built on frameworks Employees cannot follow procedures in
Does Not Reflect the from previous programs at practice. The QMS becomes a parallel
Product previous companies—not universe. Compliance theater surfaces
mapped to how the actual immediately when an inspector asks staff
device is procured, assembled, to walk through a specific procedure.
and verified.
Supplier Responsibility Regulatory teams without engineering On a device with 15–20 complex assemblies,
Gets Blurred depth cannot distinguish which cumulative misallocation of documentation
assemblies are supplier-designed vs. effort is substantial—in time
internally designed. Internal resources and risk file complexity.
get redirected into documentation
the supplier should own.
Complaint Operational pressure drives maintenance Patterns that individually pass the
Classification classification over formal complaint maintenance threshold can collectively
in Capital Equipment classification. Recurring failure meet the complaint definition.
modes go uncaptured as complaints Caught late, the compounding
across the post-market dataset. cost of quality follows.
Safety and Risk External evaluators applying IEC 60601-1 In a process running for months across 5–6
Evaluation Requires clauses to assemblies where those standards and every assembly in the
Both Disciplines clauses do not apply. Without device, the cumulative cost of
technical standing to contest unnecessary concessions is real—in
interpretations, every acceptance time, risk file complexity, and test burden.
generates unnecessary documentation.
What It Looks Like When Engineering and Regulatory Work Together
The failure modes above share a root cause: the QMS was not built to reflect the actual product. The difference when it is built that way is significant.
On one complex, multi-domain device program, we undertook a complete QMS rebuild. SOPs were rewritten from scratch in collaboration with regulatory counsel and mapped directly to how the device was actually designed, procured, assembled, and verified. What emerged from that process was more valuable than better documentation. The organization developed a shared framework and a common language.
For the first time, engineering, quality/regulatory, and business operations were all working from the same picture of how the product was structured: what was designed internally, what was purchased as a complex outside assembly, how verification would be performed, and at what level. That framework was then incorporated into regulatory training so that everyone from technical staff to senior management was oriented around the same understanding.
Outcome Why Dual Accountability Creates It
Faster decisions The same person owns both the engineering schedule and the regulatory compliance
posture—both sides of every tradeoff are visible simultaneously
No cross-functional There is no reporting line to hand the problem across and wait for it to return;
gap no information lost in translation between engineering and quality
QMS reflects Documentation is written by someone who understands the product at engineering
reality depth—procedures describe what actually happens, not what used to happen at a
previous company
Shared language Engineering, quality/regulatory, and operations work from the same picture of product
structure, verification approach, and supplier responsibility
QMSR-ready by An organization that builds its QMS around risk-based, product-grounded
design processes is in a materially better position when inspectors follow the lifecycle
None of that was achievable by engineering or regulatory working in parallel. The framework had to reflect engineering reality to be credible. It had to satisfy regulatory requirements to be compliant. And it had to be written in language the whole organization could actually use.
What This Means for Organizations in 2026
The QMSR does not create the engineering-regulatory gap. What it does is make that gap considerably harder to conceal during an inspection. And those inspections are happening now. As of February 2, 2026, FDA investigators are conducting reviews under CP 7382.850. Companies that are inspected in 2026 are not preparing for a future framework. They are operating inside it.
Organizations managing this transition well tend to share one characteristic. They have someone who can look at the QMS, understand what the engineering reality actually is, and make an honest assessment of whether the documentation reflects it. That assessment requires both perspectives to be present and active at once. It is not a regulatory exercise. It is not an engineering exercise. It sits at the intersection of both.
If your organization is working through the QMSR transition, preparing a 510(k) submission, or trying to get engineering and regulatory working from a common framework, that intersection is worth a direct conversation.
About the Author
Dan Raymond is the Founder of Springboard Solutions LLC. Dan has held simultaneous accountability for engineering and quality/regulatory functions on complex, multi-domain Class II medical device programs, including full ownership of QMS design, 510(k) submission strategy, ISO 14971 risk management, and IEC 60601-1 safety evaluations⁸ alongside engineering architecture and verification. Springboard Solutions works with MedTech companies navigating the intersection of both disciplines.
603-475-6490 | draymond@springboardsolutionsllc.com
#MedicalDevices #MedTechLeadership #SpringboardSolutions
References
1 Skills Alliance. Medtech Talent Trends 2025. October 2025. https://www.skillsalliance.com/medtech-talent-trends-2025/
2 Corena. The Biggest Quality Challenges for Medical Device Companies in 2025. July 2025. https://co-re-na.com/the-biggest-quality-challenges-for-medical-device-companies-in-2025/
3 U.S. Food and Drug Administration. Quality Management System Regulation (QMSR). Effective February 2, 2026. https://www.fda.gov/medical-devices/postmarket-requirements-devices/quality-management-system-regulation-qmsr
4 U.S. Food and Drug Administration. Guide to Inspections of Quality Systems (QSIT Guide). August 1999 (withdrawn February 2, 2026). https://www.fda.gov/files/Guide-to-Inspections-of-Quality-Systems.pdf
5 U.S. Food and Drug Administration. Compliance Program 7382.850: Inspection of Medical Device Manufacturers. Effective February 2, 2026. https://www.fda.gov/media/80195/download
6 Alston & Bird. Major Shift for QMSR Transition for Medical Device Applications. November 2025. https://www.alston.com/en/insights/publications/2025/11/fda-shift-qmsr-transition-medical-devices
7 AAMI. QMSR: What You Need to Know about Global Harmonization of Medical Device Regulations. October 2025. https://aami.org/news/qmsr-what-you-need-to-know-about-global-harmonization-of-medical-device-regulations/
8 International Electrotechnical Commission. IEC 60601-1: Medical Electrical Equipment, Part 1: General Requirements for Basic Safety and Essential Performance. https://webstore.iec.ch/en/publication/2603
