This is the Second Part of the Ecosystem Architecture Series.

This second part builds on the Philips analysis from the first article: Royal Philips: Metaphor or operating logic? and asks a broader question: what does it actually take for an organisation to shape the system it operates in, rather than simply adapt to it?

Philips is not just the subject of the analysis. It is the case that makes the wider architectural question visible.

In the first article in this series, the diagnosis was clear: Philips is speaking at system level while still operating largely at company level. That matters not only for Philips, but for any organization that aspires to ecosystem leadership without yet redesigning its architecture to match.

This artice asks some tougher questions.

That question became sharper in July 2026, when the Dutch government and Philips announced a ten-year MedTech investment of €102.5 million in public funding, matched by €50 million from Philips, focused on image-guided therapy powered by AI and robotics. This was not just support for Philips as a company. It was a nomination for a system-shaping role in a broader MedTech ecosystem.

The ambition is explicitly ecosystem-level: to strengthen the Dutch and European MedTech system by connecting start-ups, SMEs, hospitals, universities, researchers, and larger companies. That ambition is significant. The harder question is whether an organization can build the architecture that attracts world-class contributors and enables them to work at that level.

The Philips case matters because it shows the difference between speaking in ecosystem terms and building for ecosystem behavior. The lesson goes beyond one company: many organizations want ecosystem leadership, but few redesign their operating logic to support it.

In the first article, the point was not that Philips lacks platforms, partnerships, or AI capability. It was that those assets still sit inside a company-centred logic: intelligence flows inward, governance sits with Philips, and the actor network around it participates on Philips-defined terms rather than through a structure it genuinely co-owns.

This second article asks the harder question.

Not whether Philips should change — that case has already been made — but what change is actually required at the level of architecture, governance, and operating logic.

Within our analysis we have different Lenses- grouped upon a Structured, Strategic, Adaptive and External Signal Lens

What the Strategic Lens of the IIBE Reveals

The IIBE strategic lens asks a simple question: does the organization’s strategy operate at the level of the ecosystem it inhabits, or at the level of the enterprise it manages?

For Philips, the answer is both. And that is the source of the tension.

Public language from Philips’ leadership — at Davos, in quarterly calls, and around the MedTech commitment — speaks at system level: open ecosystems, integrated AI platforms, innovation through shared ambition. But the internal operating priorities still speak at enterprise level: extracting value from existing assets, restricting pilots and experimentation, and focusing on near-term margin improvement.

These two strategic registers are not in creative tension. They are pulling in different directions.

A system-shaping strategy requires investment in the conditions that make others want to participate: governance design, interface architecture, trust frameworks, and standards that attract actors who would not otherwise contribute. An extraction strategy does the opposite. It pulls resources away from those enabling conditions. You cannot ask others to innovate on your architecture while limiting the experimentation that would prove that architecture can work.

What the strategic lens reveals is not a communications problem. It is a design problem. Philips has not yet made a clear architectural choice about which destination it is designing for.

The strategic question is no longer whether Philips can speak ecosystem language. It is whether it can own the interfaces, standards, and governance architecture of a MedTech system rather than only the products and platforms within it.

So exploring within the Structural Lens you can evaluate differently.

The structural lens, for instance, asks a different series of questions, for example: Is the organization built to deliver what its strategy implies?

For Philips, the gap is not about scale. It is about design logic.

Two concepts matter here: dynamic orchestration and adaptive governance.

Dynamic orchestration means the architecture connecting actors in the ecosystem can sense what is changing and respond in real time, rather than waiting for the next update cycle.

Adaptive governance means the rules, trust frameworks, and decision mechanisms change as the ecosystem learns, rather than being fixed until the next review.

Those are not incremental improvements to a product-company operating model. They require a different organizational function altogether: a deliberate architecture above the existing platform and product structures that manages the conditions under which the ecosystem evolves.

In our view this is the role of the Living Bridge.

The living bridge is the function that keeps the system connected, keeps intelligence moving, and helps the rules evolve with the network. It seeks out pattern recognition, cross-domain synthesis and interpretive judgement under ambiguity.

The Living Bridge is the institutional capability that connects actors, routes intelligence across boundaries, updates governance in response to what the network learns, and balances stability with evolution. Without that function, the platform remains a platform. The ecosystem ambition remains a statement of intent. The architecture never becomes a system-shaping capability.

What the External Lens Shows

The external lens asks what the actor network outside Philips needs to see before it contributes its best rather than its most cautious contributions.

That question matters because a world-class MedTech system requires world-class contributors. Hospitals bring clinical workflows and outcomes data. AI developers build on shared infrastructure. Academic medical centres contribute research. SMEs bring specialist innovation. Researchers treat the system as a neutral commons rather than a company-controlled environment.

None of those actors will contribute fully unless they can clearly see at least three things.

• Firstly, governance that is neutral enough to protect their interests. That means rules, standards, and trust mechanisms that no single actor can dominate, including Philips.

• Secondly, interfaces that are open enough to enable genuine co-creation. Publishing an API is not the same as designing an open architecture. Open architecture means others can build in directions Philips did not specify.

• Thirdly, standards that are ambitious enough to attract serious partners. A world-class system is defined by the quality of its standards: data sharing, clinical workflows, AI validation, and outcomes measurement. Philips has the credibility to help set those standards. The question is whether it has the governance design to do so in a way that attracts rather than controls.

The external lens makes the design requirement plain: Philips must build for attraction, not control. The broader lesson is that ecosystem ambition only becomes credible when the architecture makes co-ownership possible.

Where the Gains and Risks Sit

The gains from becoming a genuine system shaper are structural, not incremental.

A system-shaping position creates a moat that product investment alone cannot replicate. Every additional actor, every new data flow, and every innovation at the intersections of the network compounds the value of the architecture. That is a different kind of strategic position from owning strong products or having good partnerships.

Philips already has useful foundations for that move: an installed base, clinical relationships, imaging and monitoring assets, and an AI portfolio. None of that is wasted by a shift to system shaping. On the contrary, it becomes more valuable if it sits inside a governed ecosystem architecture.

The risks of not making the shift are now more acute.

The first is competitive lock-in. Siemens Healthineers and GE HealthCare are both investing heavily in owned data and intelligence architectures. Each quarter spent managing bilateral relationships while competitors build owned system architectures widens the gap.

The second is partner confidence erosion. The actors needed for a world-class ecosystem are watching the architecture Philips actually builds, not just the language it uses. If the governance feels tightly Philips-controlled, participation will stay cautious.

The third is the cost of delay. The system-shaping position is open now, but it will not stay open indefinitely. The organization that designs the governance architecture, sets the standards, and builds the Living Bridge function first will capture compounding advantage. The organization that waits may find the position already taken.

What This Means More Broadly in Ecosystem Design

The Philips case is important because it shows a broader strategic pattern. Many organizations want ecosystem leadership, but few redesign their operating logic to support it.

That is the core lesson here: ecosystem ambition only becomes real when architecture, governance, and external design change together. Platforms, partnerships, and innovation programs are not enough on their own. Without a design that supports trust, co-creation, and adaptive governance, the organization will still behave like a company — even while it speaks like a system shaper.

That is why this case matters beyond Philips. It shows how difficult it is to move from participation in a system to shaping the system itself.

It brings us to the fourth lens: the Adaptive Lens

Adaptive capacity requires the important permission and resource to experiment, pilot, test, fail. Has the Philips organisation explicitly received that permission. Consequences often compound negatively as landscape evolves faster than restriction-mode organisation can track within Ecosystem design. This needs a certain clarity.

What This Means for Philips to determine

The board-level question is no longer whether Philips should talk ecosystem. It already does. The question is whether it is willing to redesign the organization so that the language is matched by the architecture.

That means three things in our view to be explored:

• First, Philips needs a clear architectural choice about what it is designing for.

• Second, it needs dynamic orchestration and adaptive governance as core capabilities, not as side projects.

• Third, it needs a Living Bridge function that can connect actors, evolve governance, and turn platform assets into system-level advantage.

That is the real decision now in front of Philips. Not metaphor or messaging, but architecture.

Shaping the system is not about executing the current model a bit better. It requires a different one altogether; one that attracts serious contributors, enables co-ownership, and creates value across the ecosystem rather than only inside the company.

**

In the next piece in this series, we apply the Optionality and Volatility lens to Philips, exploring which strategic options remain open, which are closing, and where the most acute risks are now unhedged.

Paul Hobcraft is the creator of the Intelligent Integrated Business Ecosystem framework (IIBE), advising enterprises and institutional bodies on ecosystem architecture, governance, and orchestration design.