Medical device manufacturers are finding that incremental changes alone aren’t enough to move the needle, despite ongoing efforts to reduce costs and streamline operations. Extended lead times, elevated inventory levels, stubborn margin pressure, and other challenges persist.
These issues often reflect a broader misalignment between how the business operates today and how its manufacturing footprint was originally designed. As product portfolios evolve, customer requirements change, M&A activities introduce overlap, and supply chain dynamics shift, the network that once supported growth can begin to constrain it.
Over time, this misalignment begins to affect more than isolated performance metrics. It influences how effectively organizations serve customers, manage working capital, and scale operations in response to changing demand. In that context, footprint decisions are no longer just matters of location or cost. They become strategic choices that shape both day-to-day performance and long-term competitiveness.
Consolidation often emerges as a logical path forward. However, these decisions tend to be more complex, and more consequential, than they initially appear. This is particularly true in the medical device space, where operational, quality control, and regulatory considerations can materially affect feasibility, timing, and outcomes.
Signals your footprint no longer fits the business
By the time organizations begin considering consolidation, the issues they’re trying to solve are rarely isolated or sudden. They tend to surface instead through a set of signals that are easy to recognize individually, but harder to connect to a common root cause.
Persistent operational and financial pressure despite improvement efforts
Organizations may experience ongoing high fixed-cost structures, dwindling margins, or low-capacity utilization despite prior productivity or cost reduction efforts. These conditions suggest that the issue may not be how efficiently work is executed but how it’s distributed across the network.
Supply chain isn’t optimized to existing customers and suppliers
Supply chain fragmentation, rising transportation costs, or declining delivery performance can indicate that the current footprint isn’t well-positioned to effectively support customer demand. In response, organizations may shift production to different locations across the network closer to customers, carry additional inventory, or introduce workarounds that increase complexity and costs over time.
Acquisitive growth creates opportunities for economies of scale and centers of excellence
Post-M&A network redundancy, new product introductions, or geographic expansion can lead to overlapping capabilities, underutilized assets, or distributed operations that are difficult to coordinate. Over time, these conditions can result in a footprint that no longer reflects the organization’s strategic priorities. Optimizing the network post-acquisition through rooftop consolidation or moving production across the network to create centers of excellence drives considerable cost savings while increasing efficiency and capacity across operations.
Individually, these pressures may be manageable. Taken together, they point to something more structural: a footprint that no longer aligns with how the organization operates. Without that lens, organizations risk continuing to triage symptoms rather than addressing the underlying cause.
For example, a regulated manufacturer had aggressive goals to shorten lead times while supporting a new product launch. The team was overly focused on needing another building. When strategic alignment work was performed, the real need emerged: adding a forward-positioned distribution capability for high-velocity products, protecting temperature-sensitive handling requirements, and preserving quality and compliance controls. That clarity changed the evaluation from a single-location search to a broader set of network questions — where to position inventory, what activities to keep close to production, and how to balance service performance with working capital.
Pressure-test scenarios before moving forward
Recognizing the need for change is only the beginning. One of the more common sources of friction, and why consolidation initiatives already underway might stall, is moving too quickly from conceptualization to specific solutions before fully understanding whether they will hold up under real-world conditions.
The value lies in the analysis that happens in between. But organizations often default to a single “preferred” concept rather than understanding how alternative scenarios perform under different conditions. That deeper layer of evaluation reveals how sensitive a network is to changes in demand, customer mix, and cost drivers such as transportation and labor.
Equally important is understanding the trade-offs each scenario introduces. Decisions that improve cost in one area may affect service levels, inventory positioning, or throughput in another. Without a thorough understanding of these interdependencies, organizations risk selecting options that appear viable on paper but prove difficult to execute in practice.
Why scenario modeling is particularly important for medical device manufacturers
For medical device manufacturers, quality and regulatory constraints can disrupt execution, and often only become visible when scenarios are modeled with enough operational detail to reflect real constraints. These constraints are often not the relocation itself, but the downstream requirements it triggers.
Moves may require additional validation/qualification time for equipment transfers, line rebalancing and recertification, and updated environmental monitoring requirements. Depending on the products and processes involved, scenarios can also carry new permitting considerations, plus labeling changes and UDI/traceability impacts that affect packaging and the broader documentation ecosystem which supports release and distribution.
These factors can also reshape risk during transition. A scenario that assumes a clean cutover can quickly become a dual-running reality, which increases complexity and elevates the risk/cost of audit findings during transition, especially if documentation, training, and quality releases lag the operational move.
Quality and regulatory requirements need to function as go-live criteria, not after-the-fact checks. Detailed scenario analysis is often the only practical way to see how these considerations trade off against the savings case.
In another situation, an organization moved quickly from a high-level concept to implementation without sufficient scenario analysis. The team had selected a change in their distribution approach and began executing leases, adjusting the systems configuration, and modifying staffing levels. As demand shifted and transportation constraints tightened, the original design couldn’t meet service targets without significant expediting costs and temporary storage. The team ultimately had to resequence the rollout, add an interim overflow solution, and renegotiate several elements of the plan. The net impact wasn’t only added cost but time. The project timeline extended, and the expected savings were delayed while the network operated in a “hybrid” state longer than planned.
Turning scenarios into executable plans
Even when a consolidation scenario appears sound, execution introduces a different set of constraints. One of the more common failure points is the gap between how a plan is designed and how it must be delivered across the organization. That gap tends to show up not in the network model itself, but in the assumptions surrounding it.
A scenario can reflect the right footprint on paper while relying on conditions that aren’t fully tested, such as the pace of systems integration, the availability of labor with the right skill sets, or the time required to prepare a site to absorb additional production. These assumptions are rarely visible in early-stage analysis, but they shape whether a plan can be executed as intended.
What becomes clear during execution is how interdependent these factors are. Changes in one area, such as facility readiness, IT timelines, or logistics design, can quickly ripple into others, altering cost-to-serve, transition timing, and service performance. Without a shared understanding of these dependencies, organizations can find themselves revisiting decisions late in the process, when options are more constrained and costly to unwind.
In many cases, execution challenges are compounded by capacity constraints across internal teams. Organizations are often asking the same functional leaders to manage day-to-day operations while also leading complex footprint changes, from scenario validation through implementation. Bringing in experienced third-party support at the right points in the process can help alleviate this strain, provide specialized analytical capabilities, and accelerate decision-making without overloading internal resources.
Cross-functional alignment tends to be the differentiator. Consolidation efforts touch a wide set of stakeholders, including finance, IT/ERP and WMS/TMS teams, operations and engineering, quality and regulatory, procurement, and transportation. When these diverse perspectives are incorporated early, before capital is committed and timelines are set, they can surface constraints that materially affect feasibility.
Readiness is less about validating a plan at the end and more about shaping it from the beginning. The organizations that navigate consolidation more effectively are those that treat execution realities as inputs to decision-making, not downstream considerations. When that alignment is in place, the path from scenario to implementation becomes more predictable, and the risk of late-stage disruption is significantly reduced.
In a separate footprint-planning effort, a recommendation was developed by a limited core team without fully engaging key functions (including life cycle cost analysis, real estate, IT, operations, and logistics) until late in the process. When the broader team finally assessed the plan, several issues surfaced: site options with attractive rent weren’t viable after factoring utility upgrades and material handling buildout; IT effort and timing were underestimated for systems integration; and logistics constraints changed the true cost-to-serve by lane. These late discoveries required scope changes and delayed key milestones. More importantly, they reduced overall implementation savings because the organization had already committed to choices that were difficult to unwind without penalties.
What changes when assumptions hold through execution
- Investment decisions are grounded in full trade-offs. Leadership has clearer visibility into how CapEx, OpEx, working capital, and service interact, allowing decisions to reflect total impact, not isolated cost improvements.
- Execution is more stable from the outset. Requirements related to systems, automation, labor, permitting, and quality validations are surfaced earlier, reducing the need for midstream redesigns and workarounds that extend timelines.
- Cross-functional alignment holds through execution. Roles, responsibilities, and decision ownership across functions and sites are clearer, limiting the friction and rework that often emerge at handoffs.
- Risk is understood and managed. Organizations enter execution with a clearer view of how the network responds to supplier interruptions, lane shifts, and volume swings, and know when adjustments need to be made.
- Performance is measurable in practical terms. Outcomes are tied to identifiable levers — inventory positioning, transportation, productivity, and consolidation decisions — making it easier to track results after go-live.
A successful consolidation reflects how well the organization understood its constraints before acting. When realities across operations, systems, quality, and logistics are incorporated early, consolidation becomes less about reacting during execution and more about carrying a plan forward as intended, preserving both the timeline and the value that it was intended to create.
