Regulatory strategy for medical devices has long been understood as a compliance function: a set of requirements to satisfy before a product can reach the market. For a meaningful share of the industry, that understanding is no longer sufficient on its own, and continuing to rely on it exclusively is becoming a source of preventable risk.
A large part of the industry still structures its development process around this assumption. Product concepts are defined, development plans are approved, clinical studies are designed, and commercial priorities are set. Only then does Regulatory Affairs become deeply involved, translating months or years of work into a dossier intended to demonstrate conformity with the applicable regulatory framework. Other organizations, particularly those already navigating complex or innovative portfolios, have moved past this model and treat regulatory thinking as an input from the outset.
The traditional model treats regulatory as the final layer of a development process already largely determined. It works when the environment is stable, requirements are predictable, and documentation is the primary variable. For a growing share of technologies and markets, those conditions no longer reliably hold.
Across Europe and other major markets, regulatory strategy for medical devices is increasingly shaping decisions about how clinical benefit is demonstrated, how risk is managed, and how lifecycle strategy is planned, long before a submission reaches a notified body or competent authority. For organizations still operating the traditional way, regulatory thinking remains largely downstream of business decisions. For a growing number of others, it has become one of the inputs that drives them.
Recent discussions surrounding the European Commission’s proposed revision of the MDR and IVDR, widely referred to as MDR 2.0, together with the proposed EU Breakthrough Device pathway, point toward a common direction. Regulatory conversations are becoming less about isolated compliance checkpoints and more about whether an organization’s overall development strategy provides sufficient confidence in the expected clinical benefit across the product lifecycle.
For executive teams, this distinction carries real consequences. A regulatory function positioned as a compliance layer will tend to validate decisions after they have been made. A regulatory function positioned as a business decision layer will help shape those decisions from the outset, reducing avoidable uncertainty before it becomes a timeline or cost risk.
Why doesn’t regulatory strategy for medical devices begin at submission anymore?
For decades, a large share of the industry treated regulatory activity as the final stage of development. Engineering defined the product, clinical teams generated supporting evidence, commercial teams set market priorities, and quality teams built the documentation; Regulatory Affairs then coordinated the submission, managed conformity assessment, and guided the product toward authorization. That model is becoming harder to sustain, particularly for organizations working with more complex or innovative technologies.
Today’s regulatory environment is shaped by technologies that evolve faster than traditional development cycles, including artificial intelligence, software as a medical device, digital therapeutics, and increasingly personalized solutions that all challenge conventional approaches to clinical validation.
Regulators are adapting in parallel: implementation experience under the MDR, growing reliance on real-world evidence, and rising expectations around Post-Market Clinical Follow-up (PMCF) all point toward systems evolving alongside innovation rather than simply evaluating it after the fact.
The table below summarizes the practices that tend to separate organizations navigating this environment more smoothly from those still building the discipline:
| Practice | Common Gap | Stronger Practice |
| When regulatory gets involved | After development decisions are largely made | From the earliest planning stages |
| Evidence generation | Driven mainly by compliance | Shared across regulatory clinical commercial, and investor needs |
| Post-market activity | A downstream obligation | Planned before launch as part of the lifecycle strategy |
| Approval | The finish line | One milestone in a longer evidence strategy |
| Risk management | A quality system activity managed separately from development | A strategic input into how benefit-risk is positioned for regulators, payers, and clinicians simultaneously |
Organizations already operating in the right-hand column are not an emerging minority to be discovered; many have worked this way for years, often well ahead of what the regulation strictly required. The distinction is less about old versus new than about which practices hold up as the environment gets more demanding.
The MDR 2.0 proposal illustrates the same direction. The targeted evaluation behind it found that while the MDR and IVDR have strengthened safety oversight, they have also produced disproportionate compliance costs and unpredictable timelines, and that adaptive pathways for breakthrough and orphan devices simply didn’t exist.
The Commission estimates the combined simplification measures could save the sector more than €3 billion a year, without lowering the underlying safety and performance bar. The Breakthrough Device pathway, expected to be formalized through new Article 52a of the MDR and Article 48a of the IVDR, reflects the same logic on a narrower scale: devices with a high degree of innovation and meaningful potential clinical impact would be eligible for designation by an expert panel, followed by priority and rolling review.
What are the four shifts redefining regulatory strategy for medical devices?
Four connected changes, evidence becoming a business asset, uncertainty being managed rather than eliminated, market access turning into a lifecycle strategy, and regulators engaging earlier are pulling regulatory thinking into decisions that used to sit outside it.
Why has clinical evidence become a business asset, not just a compliance deliverable?
Clinical evidence has traditionally existed primarily to answer regulators’ needs. Today, the same data supports reimbursement discussions, health technology assessments, physician confidence, investor due diligence, and competitive positioning.
That changes the questions worth asking before a single patient is enrolled: how much evidence is genuinely needed before commercialization, which uncertainties justify additional pre-market investigation, and which can be reasonably resolved through PMCF and real-world data instead.
None of these are purely regulatory questions anymore; they shape development cost, timeline, and long-term commercial value.
Why is managing uncertainty now as important as eliminating it?
Few genuinely emerging technologies arrive with every question answered. Historically, regulators treated open questions as a barrier to clear before approval; that is shifting toward a more structured view of how uncertainty is identified, justified, and reduced across the lifecycle rather than eliminated up front.
The EU Breakthrough Device pathway puts that shift into practice. At a recent webinar hosted by our team on the initiative, Donald O’Connor, Clinical Manager at Ireland’s Health Products Regulatory Authority and co-chair of the MDCG task force on breakthrough devices, addressed the evidence question directly.
The pathway, in his view, is not designed to lower expectations for clinical data. What it requires is accepting “that there should be a balance” between what is demonstrated before market access and what continues to be built through structured post-market activity afterward.
Why has market access become a lifecycle strategy instead of an endpoint?
Market access is increasingly viewed as one milestone within a continuous evidence strategy rather than the finish line. Organizations are expected to plan how remaining uncertainty will be addressed after commercialization through activities such as PMCF and real-world evidence, making lifecycle planning part of regulatory strategy from the outset.
For much of the industry, regulatory approval used to be a clear finish line, with attention then moving to commercialization and post-market surveillance. That sequence is blurring for a growing share of organizations. Approval remains essential, but it increasingly functions as one milestone in a longer evidence strategy, and a well-designed PMCF strategy for medical devices is a large part of why.
Richard Holborow, Head of Clinical Compliance at the notified body BSI, described this shift from the notified-body side during the same webinar, explaining that conditions such as staff training and regular post-market reporting matter because “control and patient safety remain at the heart of us releasing this innovative technology.”
Why are regulators engaging earlier in development?
Earlier engagement allows manufacturers to validate development assumptions before major investments are committed while giving regulators greater confidence that the planned evidence strategy will support meaningful review. The objective is not to lower evidence standards, but to improve decision-making earlier in the product lifecycle.
The Breakthrough Device pathway introduces structured opportunities for early advice from expert panels before development decisions are locked in.
Dan Kosednar, VP of Regulatory Affairs at Histosonics, whose company received U.S. FDA breakthrough designation for its focused-ultrasound liver tumor device, cautioned during one of our webinars that engaging these pathways is not a light commitment, noting that understanding why you’re doing it and what benefit you’re seeking is important before committing the effort.
That is a genuinely commercial calculation: it depends on what a given designation is actually expected to deliver: faster review, clearer reimbursement signals, or earlier market entry. Innovation alone is not a sufficient reason to pursue it.
What business tradeoffs do regulatory decisions force?
Regulatory decisions force concrete tradeoffs across four dimensions: how much time to invest before submission, how deep to go on pre-market evidence, what post-market commitments to accept, and how to satisfy stakeholder expectations that now extend well beyond the regulatory review itself.
Timing. Accelerating market access can create real commercial advantage in competitive therapeutic areas, but shorter timelines often require greater reliance on post-market evidence generation or more narrowly scoped pre-market investigations.
Extending the clinical program before submission may reduce regulatory uncertainty during review but delays revenue, increases development costs, and can affect competitive positioning. Neither choice is automatically correct. The right balance depends on the technology, the clinical context, and how much residual uncertainty can responsibly be carried forward.
Evidence depth. Decisions about how much pre-market clinical evidence to generate are simultaneously decisions about cost, timeline, and risk.
Generating more evidence before submission strengthens the benefit-risk case and may reduce post-market obligations. Generating less may accelerate market entry but introduces uncertainty that regulators, notified bodies, and increasingly payers will expect to see resolved through structured post-market activity. Organizations that treat these as separate decisions tend to find them in conflict later.
Post-market commitments. Post-market obligations are no longer simply the residual of a regulatory review. They are increasingly negotiated as part of the overall evidence strategy, with scope, endpoints, and timelines that have direct implications for operational cost, resource allocation, and future product claims. Accepting broader post-market commitments in exchange for earlier market access is a business decision with regulatory consequences, and vice versa.
Stakeholder expectations. Regulatory review is no longer the only audience an evidence strategy must satisfy. The same clinical data is evaluated by notified bodies, payers, health technology assessment bodies, clinicians, and investors, each with different thresholds, different endpoints of interest, and different tolerances for residual uncertainty.
A benefit-risk case designed exclusively for regulatory approval may not hold up under payer scrutiny or clinical adoption review. Risk management, in this context, is no longer only a quality system activity. It is turning into a strategic input into how clinical benefits are framed and how uncertainty is justified across all these audiences simultaneously.
Market sequencing raises a further dimension. Deciding which jurisdiction to enter first shapes how evidence is generated, how resources are allocated, and how subsequent submissions elsewhere are approached. Scientific advice has become part of the same calculation: earlier conversations with regulators can validate development assumptions and surface evidence gaps before major investment is committed.
Why do leading organizations bring regulatory in earlier?
The gap between organizations that move through complex pathways smoothly and those that experience repeated delays usually is not technical expertise; it is whether regulatory thinking shapes decisions before formal regulatory activity begins.
Leading organizations no longer treat regulatory affairs as the function that prepares submissions; they position regulatory professionals alongside product development, clinical affairs, and commercial leadership throughout the development lifecycle.
Instead of asking whether a finished product will meet requirements, teams increasingly ask earlier whether the evidence being generated will satisfy regulators, clinicians, and future reimbursement stakeholders, and whether uncertainty has been identified soon enough to still influence development, rather than simply complicate the eventual review.
This doesn’t eliminate regulatory complexity, and medical device regulation will keep evolving alongside the technology it governs. But organizations that bring regulatory expertise in earlier are generally better positioned to adapt because assumptions can still be challenged while changing course remains practical and affordable.
Questions executive teams should be asking
As regulatory strategy becomes more tightly linked to business strategy, it’s worth periodically testing a few assumptions:
- Are we treating regulatory as a compliance function or as a business decision layer that shapes development from the outset?
- Are regulatory considerations shaping our development strategy early enough, or mostly validating decisions that have already been made?
- Does our clinical evidence strategy support only regulatory approval, or also reimbursement, physician confidence, and market expansion?
- Is our benefit-risk justification compelling not just for regulatory review, but for payer and clinical audiences as well?
- Have we identified which uncertainties genuinely require pre-market evidence, and which can be addressed through PMCF and post-market data instead?
- Are our commercial timelines realistic given current clinical evidence expectations?
- Have we evaluated where risk management decisions are creating downstream tradeoffs in evidence depth, post-market commitments, or stakeholder confidence?
- Are Regulatory Affairs, Clinical Affairs, Product Development, and Commercial teams aligned around the same long-term objectives?
These questions are unlikely to produce immediate answers. Their value lies in revealing where regulatory strategy is genuinely shaping decisions and where it is still operating as a downstream validation step. The gap between those two positions is often where avoidable delays and misaligned investments originate.
What should medical device companies do next?
Recognizing regulatory strategy as a business decision layer is the starting point. Translating that recognition into practice requires a few deliberate changes to how development programs are planned and run. The following five actions reflect where that shift tends to have the most practical impact:
- Bring regulatory input earlier: Regulatory expertise is most valuable before major development decisions become difficult to change, early enough to flag evidence gaps and challenge assumptions before significant investment is committed.
- Treat clinical evidence as more than a regulatory deliverable: Evidence strategies that also account for reimbursement, physician adoption, and market expansion tend to deliver more value per study than evidence built for compliance alone.
- Plan pre-market and post-market evidence together: Lifecycle evidence planning, including a clearly defined PMCF strategy, reduces uncertainty over time instead of treating post-market activity as an afterthought.
- Keep regulatory, clinical, product, and commercial teams aligned: Regulatory strategy delivers less value in isolation; closer collaboration keeps evidence generation, commercialization planning, and regulatory objectives moving in the same direction.
- Reassess assumptions regularly: Development strategies built on expectations from a few years ago may no longer reflect where the framework is heading; periodic reassessment helps organizations adapt before changing expectations become project risk.
These are not one-time adjustments. The regulatory environment will keep evolving, and the assumptions that guide development today may not reflect what regulators, payers, and clinical stakeholders will expect in two or three years. Organizations that treat these practices as ongoing disciplines rather than project milestones tend to be better positioned when the landscape shifts.
Conclusion
For many years, regulatory success was largely defined by a well-prepared submission supported by robust technical documentation and clinical evidence. Those elements remain fundamental. What is changing, for a growing part of the industry, is the role regulatory strategy plays in achieving them.
Increasingly, regulatory outcomes are shaped long before submission preparation begins. Decisions about clinical evidence, acceptable uncertainty, lifecycle planning, market sequencing, and stakeholder engagement influence not only how a product moves through regulatory review, but also how efficiently it reaches the market and adapts as expectations continue to evolve.
This changes where regulatory creates value.
Rather than validating decisions that have already been made, regulatory strategy increasingly helps organizations make better decisions from the outset. It provides a framework for balancing evidence generation, risk management, commercial priorities, and long-term product strategy while meaningful changes remain possible.
Organizations that integrate regulatory thinking early are often better positioned to manage uncertainty, maintain development momentum, and respond to evolving regulatory expectations without disrupting broader business objectives. The advantage is not simply stronger submissions. It is stronger decision-making throughout the product lifecycle.
Ultimately, regulatory strategy is no longer defined by its ability to support compliance alone for the organizations leading this shift. Its value increasingly lies in helping organizations make informed business decisions that strengthen both regulatory outcomes and long-term commercial success.
As regulatory frameworks, technologies, and evidence expectations continue to evolve, organizations that regularly reassess how regulatory strategy supports product development, clinical planning, and market access will be better positioned to adapt, whether they are beginning that shift or reinforcing an approach they have already built.
If your team is evaluating how regulatory strategy can contribute earlier to business decision-making, this may be the right time to start that conversation.