Most corporate boards are blind to the fact that they are quietly accumulating Enterprise Option Debt that their balance sheets cannot pay back in future times, when needed. Conventional accounting looks backwards to measure past performance but it is structurally incapable of assessing future survival.

This is a ecosystem diagnostic of Royal Philips that points towards a potentially dangerous, invisible convergence gap where there is growing risk their strategic choices are contracting and exposure might be spiking in a trajectory that needs questioning. Not by external sources but by internal ones capable of making their own assessments of this Optionality and Volatility laid out here.

Asset Entrapment, Invisible Capital Erosion and Valuation disconnects are needs system-level addressing in declining optionality, unhedged volatility and a growing convergence gap in the public narrative or market need and operational reality.

The Optionality & Volatility Lens within the IIBE framework surfaces what no other existing conventional assessment can achieve

A verifiable public baseline and a qualitative concern threshold, read together through the IIBE Optionality and Volatility lens — and why the gap between them is the most important strategic finding in this series

That is what the Optionality and Volatility lens reads, for Philips at this specific moment, what it surfaces is more consequential than any single quarterly metric — because it describes not where the organisation is but what it is still capable of becoming, and what stands between the current trajectory and that possibility.

Fourth and final in a series. The first asked whether Philips is building an ecosystem or borrowing its language. The second asked what architecture a genuine system-shaping role requires. The third put Philips, Siemens Healthineers, and GE HealthCare through the nine IIBE dimensions side by side. This piece applies the Optionality and Volatility lens promised at the end of that diagnostic series.

This piece introduces a methodological distinction that matters for how the findings should be read that often presents a radically different story on an organization. Reading time 15 minutes

Most assessments of an organisation read where it is now.

Results. Order intake. Margin structure. Capital committed. All of it useful. All of it measuring execution — how well the organisation is running the model it has already chosen. None of it designed to ask what that model is preserving or foreclosing, and what unpredictable value change — positive and negative — the architecture underneath it is exposed to, hedged or not.

Two scores are presented — not two competing assessments, but two readings of the same diagnostic instrument at different depths of information. The first is built entirely from public sources. The second applies if qualitative organisational signals, gathered through research and judgment over time, are accurate. The gap between them is not a discrepancy to be resolved. It is the finding.

The Two Scores — and What Separates Them

The IIBE Optionality and Volatility lens produces two distinct readings for Philips, shown here together for the first time:

These are not two versions of the same number. They are two readings of the same organisation at different depths of available information — and understanding precisely what separates them is essential to reading either one correctly.

The public baseline of 5.8 on optionality and 6.2 on volatility is built entirely from independently verifiable sources: financial disclosures, results presentations, Capital Markets Day materials, competitive positioning data, on-record leadership statements, and publicly available intelligence on the competitive landscape. Any serious external analyst could construct this read. It is not a weak score — a company sitting at 5.8 on optionality still has meaningful strategic room, and a 6.2 on volatility reflects serious but not existential exposure. This baseline is the floor of the diagnostic.

The concern threshold of 3.8 on optionality and 7.4 on volatility applies if qualitative organisational signals are accurate. These signals do not appear in any public filing, possibly offering a consistent underlying pattern — visible over years — of a company whose internal investment posture is perhaps diverging from its public language. The direction of these signals is consistent with the CEO’s own public acknowledgment in March 2026 that slower growth leaves less room to invest in innovation.

Whether the concern threshold implies is something only those with access to the internal architecture can verify alongside its risk and financial appetite . The board should test the concern threshold against its own internal knowledge — not accept it, not dismiss it, simply test it.

The gap between 5.8 and 3.8 on optionality, and between 6.2 and 7.4 on volatility, is not a measurement error. It is the most important strategic signal in this entire series.

A gap of that size between what public data shows and what gathered intelligence signals suggest — if those signals are accurate — describes an organisation whose external narrative and internal reality are diverging at a pace that is not sustainable in either direction. That convergence will resolve. The O&V diagnostic is designed to make it visible before the resolution happens, while the board still has choices about which direction it goes.

What the O&V Lens Is — and Why It Is Different

Designed Optionality under Volatility is the deliberate architectural capability of an ecosystem to retain, activate, or reconfigure strategic choices as uncertainty increases — without requiring collapse, exit, or emergency intervention. It treats volatility not as a risk to be absorbed, but as a condition to be engineered for.

This lens was developed in the IIBE framework following a careful analysis of Northvolt — an organisation that collapsed in spectacular fashion. The O&V lens is an instrument that surfaces the structural signature questions of what might be coming. Low optionality paired with high, largely unhedged volatility is a specific and shows up in what the organisation is still capable of building next, and what it is exposed to before it gets there.

There is no implication that Philips is Northvolt. The financial position is very different as Philips has a materially stronger, well installed base providing genuine buffers if needed and the turnaround discipline of the last two years is real and should be credited as such.

The diagnostic value of the O & V lens itself — is its capacity to surface structural risk that conventional assessment is not designed to see. That is its value here, applied to a company working through highly competitive and market challenges

The O&V lens is a cornerstone of the IIBE framework precisely because it asks questions that no other assessment instrument in current use asks in this form. Not what happened last quarter. Not what the strategy presentation says. But what the architecture is preserving or foreclosing, and what it is exposed to, hedged or not — read at two depths of information simultaneously so that the gap between them becomes visible as the finding it is.

What the Optionality Lens Surfaces

Optionality asks a simple but unforgiving question: what future architecture is the organisation still capable of building, given the decisions it is making today? Options are not free. They require active investment — in pilots, in experimentation, in capability that may not pay off — to remain open. Innovation capability atrophies quickly when that investment stops.

On the public baseline alone, Philips retains meaningful optionality. The installed base across imaging, monitoring, and intervention remains a genuine foundation. The enterprise agreements with WellSpan, AdventHealth, the Poland platform deal, and the Karolinska partnership demonstrate bilateral execution capability at scale. The “no product without AI” mandate has been maintained. The Digital Connected Care Coalition — arguably the most advanced multi-actor governance structure any major MedTech company has built — demonstrates that the design capability required for genuine ecosystem orchestration is present within Philips. It is not missing. It is perhaps pointed at the wrong problem or not seen for its broader value.

That last observation is the most important in the optionality analysis — and it applies equally at the public baseline and at the concern threshold, though its implications differ at each level. The Coalition’s governance model is a proven architecture for multi-actor coordination across multiple stakeholders. The commercial ecosystem question Philips needs to answer — how do you govern a network of actors contributing to a shared MedTech infrastructure — is the same design problem. Redirecting that capability is cheaper than building it from zero. That makes this option more recoverable than the others, which is not a reason for comfort but a reason for urgency: a low-cost path back to optionality that is being left unused is a more pointed diagnostic finding than “the capability does not exist.”

Four specific options are under pressure at the public baseline — and move to genuinely exposed at the concern threshold level that need clarifying:

The hospital-to-home orchestration option requires sustained pilot investment to design the governance layer that would allow Philips to coordinate care genuinely beyond the hospital wall. At the public baseline this option is open but underfunded. At the concern threshold, a restricted-experimentation posture closes it faster than any competitive pressure could.

The image-guided therapy AI and robotics architecture option is increasingly dependent on external funding rather than internal investment at the scale required. The fact that the most significant investment in this domain arrived from outside Philips’ own capital allocation is itself diagnostic — it signals that the internal investment posture had allowed this option to drift toward closure before external intervention reopened it. The Dutch Governments proposals (discussed in early posts) are genuinely exciting

The partner ecosystem intelligence layer option — as noted above — is the most recoverable, because the capability exists. What is missing is the recognition that the Coalition and the commercial ecosystem question are the same design problem, and the capital allocation decision to redirect accordingly.

The emergent clinical AI option — an owned, iteratively developed intelligence layer across Philips’ imaging and monitoring estate — requires exactly the iterative pilot development that a restricted-experimentation posture cuts off. At the concern threshold this option is closing at the moment its competitors are investing most heavily in precisely this capability.

Book-to-Bill There is one further optionality signal that sits squarely in the verifiable public data and is worth naming plainly. In recent comparative reporting, GE HealthCare’s organic orders grew 11.1%, pushing book-to-bill to 1.15x and backlog to a record $23.9 billion. Siemens Healthineers’ equipment book-to-bill reached 1.27. Philips’ order intake declined 1% in the same quarter — the first decline after six or seven consecutive periods of growth. Management attributes this to large monitoring orders timing into the following quarter, and the underlying book remains at record level. That explanation may be entirely correct. But a single data point where IF Philips moves in the opposite direction from both rivals, at the moment both rivals are accelerating, is exactly the kind of signal the O&V lens is designed to flag before it becomes a trend.

What the Volatility Lens Surfaces

Volatility asks a different question: what sources of unpredictable value change is the current architecture exposed to, and how much of that exposure is actually hedged — as opposed to simply not named?

At the public baseline, the negative exposures are concrete and largely outside Philips’ direct control. The Department of Justice investigation into the Respironics recall remains open — an unquantified liability that could materialise on its own timeline without warning. US tariff policy on medical devices is live and shifting, with supply chain complexity creating exposure that a more domestically-manufactured competitor absorbs differently. These are known unknowns that public data cannot resolve.

The competitive exposure is where the public baseline and the concern threshold diverge most sharply. At the public baseline, the competitive gap in data intelligence architecture is visible but still closeable. Siemens Healthineers has built patient twinning, precision therapy, and digital AI as explicitly interconnected, internally-owned pillars. GE HealthCare has committed more than $5 billion to innovation investment and holds more AI-enabled FDA authorisations than any other MedTech company. Philips delivers a growing amount of its AI capability — Smart Reading among them — through partnership rather than owned architecture. At the public baseline this is a gap. At the concern threshold, with internal innovation investment restricted during the same period both rivals are accelerating, it becomes a widening structural divergence that may have longer term consequences

The Schneider Electric precedent is worth citing here. Schneider separated AVEVA — its data intelligence and industrial software capability — on the belief that partnered access was sufficient. It later concluded that was a mistake, brought it back into the organisation to bring the data under their control. Schneider also recently bought a controlling stake in Cognite for $3.1 billion to rebuild their owned position of significant promise. Philips is not at that point. It is, arguably, at the point just before it — where the choice between owning and accessing is still open, but where every quarter of differential investment between Philips and its rivals narrows the window within which that choice remains genuinely available.

On the positive side, two assets sit in the volatility picture that are not fully reflected in the public baseline.

The external commitment to image-guided therapy through AI and robotics — €102.5 million in public Dutch Government funding matched by €50 million from Philips — is a substantial and externally generated reopening of strategic room that the internal posture had been closing. It is unusual precisely because it did not originate inside Philips’ own capital allocation. It was offered to Philips because of what it has been trusted to build before. That makes it a positive volatility event of a specific kind: one that arrives from outside and creates obligation as much as opportunity. Whether Philips captures it depends on whether the internal investment posture shifts to match the external commitment.

The second positive asset is quieter and more structural. Philips sits at the centre of Brainport Eindhoven — the most sophisticated regional innovation ecosystem in the Netherlands, and the same network from which ASML grew. That proximity has not yet been deliberately connected to the external commitment in a way that activates its full optionality value. It represents an underleveraged asset with real architectural potential that the concern threshold scores do not yet reflect — and that a board paying attention could choose to activate further at a more accelerated pace than currently outlined.

The Convergence Dynamic — Why the Gap Is the Finding

Low optionality and high, largely unhedged volatility together produce a specific kind of strategic fragility: an organisation with less room to absorb a shock at exactly the moment its exposure to shocks is rising. That combination does not appear as a warning in a results presentation. It appears in the gap between what the architecture is publicly described as building and what the investment posture is actually funding.

The gap between the public baseline and the concern threshold — 2.0 points on optionality, 1.2 points on volatility — is not a measurement discrepancy. It is the structural signal that the public narrative and the internal reality may be diverging at a pace the organisation has not yet named publicly and may not yet have fully named internally.

That divergence is not sustainable. It resolves in one of two directions.

Either the internal posture improves to match the external narrative — pilots are refunded, experimentation is reopened, the Coalition governance capability is redirected toward the commercial ecosystem problem, the data intelligence architecture is brought in-house rather than accessed through partners, and the external commitment becomes the catalyst for a genuine investment posture shift. In that direction, the concern threshold scores become unnecessary — the public baseline was the more accurate read, and the gap closes from below.

Or the external narrative deteriorates to reflect the internal reality — the competitive gap in data intelligence widens to the point where it becomes visible in results, partner confidence erodes as the governance architecture fails to deliver on system-shaping ambitions, and the optionality cost of delay becomes the structural constraint it is currently still possible to avoid. In that direction, the concern threshold scores were the more accurate read, and the gap closes from above.

The O&V diagnostic does not determine which direction the convergence goes. That is a board-level decision still being made. What the diagnostic does is make the convergence dynamic visible with enough precision that the board can act on it before the resolution happens rather than after it. That is what existing conventional assessment cannot reach — not because the tools are inadequate, but because they are not designed to read what is being preserved or foreclosed, only what has already been achieved.

The Questions This Leaves for the Board

This series has asked progressively harder questions of Philips. The first asked whether ecosystem language described an architecture or borrowed one. The second asked what a genuine system-shaping architecture would require. The third asked where Philips sits against its two closest rivals across nine architectural dimensions. This piece asks the question that sits underneath all of them:

Which options are we still funding the right to use — and which risks have we decided not to name?

That question cannot be answered from outside the organisation, only applying the analytical tools to support their evaluations. It requires the board to hold the public baseline and the concern threshold simultaneously — not to choose between them, but to test the distance between them against internal knowledge that only the board possesses.

If the concern threshold is substantially wrong, the public baseline remains a serious and substantive diagnostic finding in its own right. If the concern threshold is substantially right, the convergence dynamic is already underway and the window within which the board can choose its direction is narrower than the public metrics suggest.

The O&V lens does not prescribe which path to take. It surfaces what each path costs in optionality and what each path carries in volatility — read at two depths of information, with the gap between them named as the finding it is. That is what the diagnostic is designed to do. And it is the dimension of strategic assessment that the most sophisticated boards will increasingly need, as the gap between what organisations say they are building and what they are actually funding becomes the most consequential strategic variable of the next decade.

Philips has the installed base, the clinical relationships, the proven governance capability in the Coalition, and now an externally generated catalyst of significant scale. Whether it also has the internal investment posture to convert those assets into the architecture, that a genuine system-shaping role requires — that is the question the O&V lens surfaces, and the one only the board can answer.

Any board trapped in an inward, backward-looking compliance loop cannot validate a system-level crisis until it hits the bottom line. Knowledge is not locked today with corporate walls – it is distributed all around them.

Is today’s existing architecture burning down future choices? Accumulating Option Debt can choke future cash flow tomorrow? Do not get caught defending an obsolete corporate fortress while the entire battlefield has shifted.

Paul Hobcraft is the creator of the Intelligent Integrated Business Ecosystem (IIBE) framework, working with large industrial enterprises and institutional bodies on ecosystem architecture, governance, and orchestration design. The O&V lens — Optionality and Volatility — is a proprietary diagnostic instrument within the IIBE framework, designed to surface what existing conventional assessment cannot reach.

paul4innovating.com  ·  ecosystems4innovating.com ·  MedTech Ecosystem Architecture Series

The post Royal Philips: Two Scores, One Diagnostic, What the O&V Lens Surfaces first appeared on Applying Ecosystem Architecture.

This is third in a series. The first piece asked whether Philips is building an ecosystem or borrowing its language. The second asked what architecture a genuine system-shaping role requires.

This piece puts Philips, Siemens Healthineers, and GE HealthCare through the same nine-dimension IIBE assessment side by side — asking what a like-for-like architectural read reveals that a quarterly results comparison cannot.

One critical issue to ask : This looks beyond comparing scores at the harder structural question underneath as we compare: has any of them actually built an ecosystem, or are all three still running sophisticated versions of the same bilateral sell?

This is about a 15 minute read.

In this nine IIBE dimensions we look across rivals to see differences and opportunities offering competitive positioning and opportunity points and where it places Philips in its approaches.

Each scores a company 0–10 on a specific architectural capability — not performance, not intent as stated in a press release, but what the organisation has actually built. The score is not a financial rating — it’s a judgment about ecosystem readiness, built by weighing multiple public inputs against the framework’s diagnostic criteria

Applied consistently across Philips, Siemens Healthineers, and GE HealthCare, the comparison stops being about who is winning this quarter and starts being about who, if anyone, has genuinely escaped the bilateral logic all three are competing inside.

The Scores, Side by Side

Philips appears twice in this table deliberately. The first column is what the nine dimensions produce from public information alone — results, Capital Markets Day positioning, press releases, the same kind of material available on any of the three companies. The second is the same assessment revised after weighing qualitative organisational intelligence on Philips’ actual investment behaviour — signals not available, and not attempted, for Healthineers or GE HealthCare.

The two Philips columns are not two independent measurements. They are the same company read at two different depths of information, and only one of those depths has been applied consistently across all four columns. That asymmetry is worth holding in mind: the Philips-specific finding is more informed than the cross-company comparison itself.

* The revised Philips column is based on qualitative signals that do not appear in any public filing — these are signals, some consistent with the CEO’s own public acknowledgment that slower growth leaves less room to invest in innovation. They are a diagnostic hypothesis serious enough to act on, not an established fact — and the reader should weigh the revised column accordingly against the more conventionally-sourced public read alongside it.

They rest on access and judgment built over time, not on a citable record, the same way they would with any analyst or journalist working sources rather than only filings as a diagnostic hypothesis serious enough to act on, not as an established fact, This includes signals on stalled pilot projects with no clarity on next steps, budget and headcount reductions or shifts within teams in specific innovation functions. These signals speak to ambition and risk appetite, but they are not independently checkable by a reader.

The nine dimension scores that shift upward on the public assessment as specific for Philips can be summarised briefly on where the present internal assessment might be to where it is “projected” in the public understandings.

Clarify identified gaps as building clear intent

It is these identified “gaps” that need articulating specifically to narrow them in my evaluations otherwise the lower score stands.

Dimension 1 — Strategic intent: 5 to 7. Taking Public language as ecosystem-adjacent and genuine in its ambition. Jakobs’ Davos positioning, the connected care narrative, the platform innovation framing all read as real strategic intent from the outside. Is It?

Dimension 2 — Value architecture: 5 to 6. EMaaS, the AdventHealth partnership, the enterprise service model transition all represent genuine value architecture movement visible publicly. Will they build this out?

Dimension 3 — Partner orchestration: 3 to 6. From the outside the Digital Connected Care Coalition, the hospital partnerships, and the AWS collaboration read as a developing orchestration capacity rather than purely bilateral management. How will these evolve?

Dimension 6 — Innovation architecture: 3 to 6. The BlueSeal, Rembra, Verida innovations and the “no product without AI” mandate read publicly as a maintained innovation posture rather than a structurally inhibited one. This needs clarifying

Dimension 7 — Resilience: 5 to 6. The public financial recovery narrative — margins expanding, order intake growing, balance sheet rebuilt — reads as genuine resilience improvement. This is where Philips have placed the mephasis, 2026 quartely results will determine this

Dimension 9 — Dynamic orchestration: 3 to 5. From outside there is no visible evidence of restriction — the adaptive capacity gap looks like a design gap rather than a deliberate inhibition. This is discussed further in this post.

Six Major Things the Table Reveals

First — on the public read alone, Philips looks broadly competitive with both rivals.

65 against 68 and 71 is a gap, not a chasm. On several dimensions the public-only Philips score matches or nearly matches Healthineers outright — governance, data intelligence, moat architecture. Anyone assessing Philips purely from what it says and reports would reasonably conclude it is in the same tier as its rivals, running a few points behind. That conclusion would not be unreasonable. It would also be incomplete.

Second — the ten-point revision does not fall evenly. It concentrates precisely where it should.

Partner orchestration and innovation architecture each drop three full points — the two largest single-dimension movements in the table. Data intelligence drops one point despite the “no product without AI” mandate remaining genuine, because owning the mandate is not the same as owning the infrastructure behind it. Governance, resilience, and moat architecture each move by only a single point, because those dimensions rest on things already built — compliance systems, installed base, balance sheet — rather than on what gets funded next. The revision lands exactly where an extraction-first capital posture would be expected to show up first. That is itself a diagnostic signal.

Third — Dimension 9 is the one place where both Philips readings already agreed.

Dynamic orchestration scored lowest of all nine dimensions in the public-only assessment — 5/10, a full point below the next-lowest dimension. No insider intelligence was needed to reach that conclusion. The single dimension every company in this comparison is weakest on is also the one where Philips’ own public conduct, read without any internal intelligence at all, already pointed to the same conclusion the deeper read confirmed. That is a useful piece of corroboration for the revision comparision as a whole.

Fourth — the gap between Philips and its rivals is real but concentrated, not uniform.

On governance and trust architecture, all three cluster within a single point. The dimensions where the gap widens sharply are innovation architecture — 3 versus 6 and 8 — and data intelligence — 6 versus 8 and 8. Precisely the two dimensions that require sustained capital investment in experimentation and owned intelligence infrastructure. The gap is not that Philips lacks ecosystem vocabulary or governance discipline. The gap is specifically where a restrained internal investment posture would be expected to show up first.

Fifth — GE HealthCare’s advantage is structurally different from Siemens Healthineers’, even though their overall scores sit close.

Healthineers’ strength is asset-based — the imaging data estate, the Varian oncology position, moat architecture built over decades. GE’s strength is closer to genuine platform design — the Edison Developer Programme brings in third-party AI developers and academic institutions under something closer to shared infrastructure than either rival has built. GE scores highest on partner orchestration precisely because Edison is doing something the other two are not: letting outside actors build on its rails rather than simply selling into a customer base. That distinction matters for understanding which competitive gaps are closeable through investment and which require a different architectural logic entirely. This gives GE a real edge if they take this into a fully build ecosystem approach.

Sixth — and this is the finding that matters most — every company scores in the same narrow band on Dimension 9.

Dynamic Orchestration and Evolution Capacity: 3 to 5 across all three. That is not a coincidence. It is the finding that validates the whole diagnostic exercise rather than simply describing Philips’ position within it.

Why Dimension 9 Is the Finding, Not a Footnote

Dynamic orchestration asks whether a company has built the sensing-and-response mechanism that lets an ecosystem actually evolve — a function that notices what emerges from a partner network, interprets it, and routes it back into how the architecture operates. In the IIBE framework this is called the Living Bridge. No company evaluated here has one.

That includes GE HealthCare, which has built the most platform-mature architecture of the three. Edison aggregates data across modalities and vendors, hosts a genuine developer ecosystem, and produced roughly forty third-party innovations in the past year through its accelerator model. And it still tops out at 5/10 on dynamic orchestration — because Edison optimises the relationship between GE and each partner individually. It does not yet let partners create value for each other in ways that compound back into the network without GE mediating every interaction.

It includes Siemens Healthineers — four years into the Varian integration — where the internal language is still education, co-location, and relationship-building rather than co-created value at the network level. And it includes Philips, scoring lowest of the three — not for lack of the underlying design skill, which the Digital Connected Care Coalition already demonstrates, but because that skill has never been pointed at the commercial architecture where dynamic orchestration would actually need to operate.

This is the point worth making plainly. The two companies with the deepest data estates and the largest innovation budgets in the sector have not solved this either. If capital and data alone were sufficient, GE’s $5.1 billion innovation commitment and Healthineers’ imaging data moat would have produced it by now. They have not — because dynamic orchestration is not a spending problem. It is a design problem. And none of the three has yet chosen to design for it specifically.

That is the strongest available evidence that the gap this series has been describing at Philips is not just a Philips ‘issue’. It is a category-wide architectural absence that happens to be more acute at Philips because of where its capital allocation currently sits.

The Bilateral Trap — and Why It Does Not Move for Shareholders

Every large deal named across all three companies this year is structurally the same thing. Healthineers with Cleveland Clinic and Vanderbilt. GE with Sutter Health and Catholic Health. Philips with WellSpan and the Poland platform agreement. Each a large, multi-year, bilateral contract. Each genuinely valuable commercially. None of it evidence of ecosystem architecture — because in every case value still flows through the vendor, negotiated and priced deal by deal, rather than through a governed network where partners build value independently of the vendor’s direct involvement.

That pattern persists for a reason that has nothing to do with any of the three lacking vision. It has everything to do with what public markets currently reward. Ecosystem architecture requires multi-year investment in infrastructure whose payoff is genuinely uncertain and shows up on nobody’s quarterly guidance. Bilateral deals show up immediately — in orders, in backlog, in the numbers an analyst can model.

The market has already chosen for them. The result is a structural trap: strong volume, compressing underlying margin, and every vendor’s rational response to margin pressure being to protect this quarter rather than fund next decade’s architecture. It is precisely the dynamic that keeps all three capped at Dimension 9 — and the one that will continue to do so until one of them makes the architectural decision to break out of it first.

All three companies could hit every number analysts are modelling for the next three years and still be exactly where they are today on the one dimension that determines whether any of them stops competing on price- they are all stuck in a bilaterial trap as they begin the “race to the bottom”.

Siemens AG’s Counter-Evidence: Structural Courage Exists

It is worth being fair to what the Siemens Group has shown it is capable of — because it complicates any argument that public markets simply forbid bold structural change.

Siemens AG has committed to fully deconsolidating Healthineers — not trimming a stake, but distributing shares directly to its own shareholders and exiting the business entirely, with a vote scheduled for the February 2027 AGM. This follows the earlier separation of Siemens Energy, which endured genuinely difficult years before recovering on the back of surging grid and gas demand. This is a group that has demonstrated real willingness to make structurally uncomfortable portfolio decisions and absorb the short-term cost.

Healthineers itself is separately weighing a carve-out of its Diagnostics unit alongside a leadership refresh — a new EMEA head, an incoming CHRO, and the arrival of Martin Stumpe as CTO from Google Brain with an explicit mandate to expand AI capabilities dramatically. Whether that combination is specifically intended to put data architecture more centrally in the business is not confirmed by the public record. It is a reasonable question to hold open.

What the Siemens picture shows is that boldness toward architecture is possible within the same ownership and market constraints that appear to prevent it elsewhere.

What These Nine Dimensions Validates — and What It Does Not

Applying the same nine dimensions across three comparable companies does something a single-company diagnostic cannot: it separates what is specific to Philips from what is structural to the sector.

The gap in innovation architecture and data intelligence is real and specific to Philips’ current capital allocation — that finding holds up under comparison rather than dissolving. But the absence of dynamic orchestration is not a Philips finding. It is a category finding, present at identical severity in the two companies best resourced to have solved it, who have plainly not.

That is the genuine validation for a diagnostic-first approach to this sector. Not that it proves any one company is behind, but that it shows precisely where conventional performance metrics — margin, order growth, capital committed — run out of explanatory power, and where the structural question takes over.

Specifically for Philips for its future

For Philips you have to ask If Philips’ strategic ambition is to become a system shaper in European MedTech and beyond, then it needs to preserve certain options: shared-governance capability, interoperable interfaces, partner incentives, clinical-data rights and sustained experimentation.

If, instead, its ambition is to be a focused, high-quality technology supplier and selective partner, then some of the apparent option closure needed to be made may be deliberate. That would be a different strategic choice, and it may be worth making that choice explicit.

Making this distinction clearer could pre-empt the natural counterargument that tighter capital allocation, selected partnerships and reduced experimentation are simply sensible sequencing after Respironics. It would also sharpen the board question: not whether Philips is “wrong,” but whether its capital allocation, governance and architecture are consistent with the role it genuinely intends to play.

The final piece in this series follows and applies the Optionality and Volatility lens to Philips — examining what strategic options are open, which are closing, and where the volatility the organisation faces is most acutely unhedged. It introduces a methodological distinction that takes the diagnostic one level further: two scores, one diagnostic instrument, and why the gap between them is the finding that existing conventional assessment cannot reach.

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

paul4innovating.com  ·  ecosystems4innovation.com

·  MedTech Ecosystem Architecture Series

The post Royal Philips in Competitive Context: Measured Against Its Major Rivals first appeared on Applying Ecosystem Architecture.

We need to ask a broader question here: 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.

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.

The diagnosis is 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 second part of a series that builds on the Philips analysis following on from the first article: Royal Philips: Metaphor or operating logic?

This article raises some of those tougher questions when you are building collaborative Ecosystems.

That question of shaper or shaping 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.

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 Ecosystem design questions.

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 applied in a Ecosystem diagnostic that are grouped around a Structured, Strategic, Adaptive and External Signal Lens set of questions.

First, What the Strategic Lens of the IIBE Reveals

The IIBE strategic lens asks multiple different questions but one of these is a simple one: 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.

You can explore these needs for applying Dynamic Orchestration, Adaptive Governance and the Living Bridge in more detail in the post: “The Architecture That Changes Everything in Ecosystems is Dynamic and Adaptive“

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:

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

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

• 3, 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.

The post Royal Philips: Will It Shape the MedTech System — or Be Shaped by It? first appeared on Applying Ecosystem Architecture.

Roy Jakobs has been saying the right words for a while now. At Davos in January 2026, freshly reappointed as Philips CEO, he called for an “open ecosystem” in which Philips adopts other companies’ AI into its workflows rather than trying to build everything itself. By March, he was describing Philips’ shift from standalone devices toward integrated AI platforms, while also warning that slower growth leaves less room to keep investing in innovation. Then in July, alongside the Dutch government’s €102.5 million MedTech commitment, he returned to the same theme: “innovation thrives when we come together around a shared ambition”.

That is not random messaging. It is a CEO describing something close to an orchestrator strategy. The question is whether Philips’ actual architecture matches what its CEO is now saying in public.

A simple test helps. If Philips disappeared from HealthSuite tomorrow, would the hospitals, AI vendors, and researchers connected to it keep building together on their own? Or would the whole thing simply stop? If the honest answer is “it would stop,” then Philips does not yet have an ecosystem in the full sense. It has a company-centred network using ecosystem language. That distinction – metaphor versus operating logic – is the most useful lens for reading Philips’ current strategic fork.

Metaphor versus operating logic

Using the Intelligent Intergrated Business Ecosystem (IIBE) lens, the difference is straightforward. The IIBE is designed to expose how a company’s architecture really works – where power, governance, and value sit in practice, not in slides. Ecosystem as metaphor means a company describes its partnerships, marketplaces, and platforms in ecosystem language while the real decisions still sit inside its own governance, incentives, and control logic. Ecosystem as operating logic means governance, data flows, experimentation, and value capture are deliberately designed so that outside actors can build, scale, and benefit on infrastructure the anchor company does not fully dictate.

Philips’ HealthSuite and ECG AI Marketplace are real enough, but structurally they still look like Philips-owned rails with Philips-defined terms. That is company-level logic borrowing system-level language. It is not unusual; many important ecosystems begin this way. The real issue is whether Philips evolves beyond that stage or gets stuck there.

The pendulum Philips keeps repeating

Philips has spent decades swinging between two different failure modes. For much of its history, it over-indexed on invention without reliably capturing the value. NatLab helped produce the compact cassette, the CD with Sony, early LED advances, and the semiconductor capabilities that later fed into ASML. Innovation was not the missing ingredient. The persistent weakness was converting breakthrough invention into durable, compounding, owned advantage.

Then came the swing the other way. After the Respironics crisis, Philips did what a company in shock should do: preserve cash, tighten operations, and rebuild credibility. Jakobs’ turnaround is real; Philips has reported improving sales, margins, and order intake despite tariff and geopolitical pressure. But a crisis response can easily harden into a strategic habit. When pilots narrow, experimentation slows, and near-term extraction dominates, the company may protect the core while quietly losing the next layer of strategic freedom. Philips has already seen what this looks like in practice: from the full value of the CD, to semiconductor depth, to the upside of ASML, important positions have slipped when architecture and governance lagged behind invention.

This is where the innovation-portfolio problem matters. Philips does not just appear to swing between experimentation and extraction; it appears to do so without a stable, explicit portfolio of bets across horizons. In a true innovation portfolio, some capital protects the core, some extends adjacencies, and some creates future options. Without that balance, the pattern becomes predictable: one era produces too many disconnected experiments; the next kills or starves them in the name of discipline; and the company never builds a repeatable pathway from invention to new architecture. In IIBE terms, the portfolio gap shows up as an architecture that can’t reliably turn pilots and incremental projects into system‑level capabilities and commercial scale. Research on innovation portfolios repeatedly shows that firms overloaded with incremental projects rarely generate the growth they seek, while weak portfolio design often kills breakthrough options before they scale.

The ASML lesson, properly read

This is where the Philips story becomes more interesting than the standard cautionary tale. The usual version says Philips co‑founded ASML and then failed to hold onto the value. That is true at one level, but incomplete at the level that matters.

ASML emerged in 1984 as a joint venture between ASM International and Philips, at a time when Philips did not want to carry the full cost and risk of lithography R&D on its own. In other words, ASML was not only a story of strategic foresight. It was also a story of constrained capital, risk sharing, and partial release. Philips did not create ASML by perfectly orchestrating an ecosystem from the centre; it helped create the conditions for ASML by allowing something strategically important to become more independent than its normal control instincts might have preferred.

Philips has been here more than once. ASML is the clearest case, but the later spin‑off of its lighting business into what is now Signify – separating health tech from connected LED lighting under capital and focus pressure – followed a similar pattern: when the scope and investment needs of an activity became too large to run as just another Philips division, independence and new governance followed.

That changes the lesson. Philips’ greatest ecosystem successes may not have come from holding tighter, but from loosening its grip early enough for independent governance, partner trust, and external complementors to emerge. The point is not that Philips should simply “let go” in some vague romantic sense. The point is more exact: when innovation becomes too complex, too distributed, and too capital‑intensive for one company to control end‑to‑end, value shifts toward whoever designs and governs the shared architecture.

The real strategic move: orchestrate others’ innovation

That is the sharper thesis Philips now needs. If a company is under real capital discipline and no longer wants to fund broad internal experimentation at scale, the only credible way to continue benefiting from innovation is to become a great orchestrator of other people’s innovation. In IIBE language, that is the work of dynamic orchestration and adaptive governance: creating movement and shared value in the ecosystem, and making sure the trust infrastructure and rules can adapt as more actors join. That means owning the interfaces, standards, governance rules, and system architecture that let external actors experiment and scale on your rails – without turning the whole thing back into a one‑company system.

This is not the same as “spend more on R&D,” and it is not the same as “extract more from what we already own.” It is a third move. Philips does not need to outspend Siemens Healthineers or GE HealthCare in every AI domain. It needs to become the indispensable coordination layer in the domains that matter most to MedTech. That is the difference between participating in innovation and architecting its direction.

The IIBE’s core question here is simple: will Philips be a neutral orchestrator, or simply coordinate activities within boundaries it already controls?

Tier 2 or Tier 1

Seen through that part of the IIBE lens, Philips’ current positioning looks uncomfortable. In many of its AI and data plays, Philips still resembles a Tier 2 actor: a supplier contributing data and algorithms into environments others govern, rather than a Tier 1 orchestrator that sets the shared architecture and the interfaces others must plug into. Tier 2 actors can make money. They do not usually shape the system.

A Tier 1 orchestrator sits higher in the architecture. It shapes the rules, governs the platform, and captures the optionality that comes from being central rather than adjacent. That distinction matters because optionality – future strategic room to move – is now the scarce asset. Once a company settles into a subordinate layer of someone else’s architecture, climbing back up becomes expensive and politically difficult. And every year Philips waits, the easier it becomes for rivals to lock in that upper tier.

The Dutch bet and what it really asks

That is why the July 2026 announcement matters more than the headline amount suggests. The Dutch government and Philips jointly announced a ten-year MedTech investment: €102.5 million in public funding, matched by €50 million from Philips, aimed at image-guided therapy powered by AI and robotics. The ambition is explicitly ecosystem-level: to strengthen the Dutch and European MedTech system by connecting start-ups, SMEs, hospitals, universities, and larger companies.

This is not a rescue package. It is a nomination. The Dutch state is, in effect, asking Philips to play a system-shaping role in a sector where innovation will increasingly depend on shared data, clinical workflows, software layers, and institutional trust. That is a much bigger ask than running a better internal platform.

It also brings a hard behavioral constraint into view. Hospitals, researchers, and AI partners will only contribute seriously to a shared innovation system if they believe the governance is neutral enough to protect their interests. If Philips uses public money to build a bigger version of a Philips-controlled network, the ecosystem language will stop persuading people long before the architecture starts compounding.

The control trap

This is the trap some industrial platforms fall into: trying to become the orchestrator by increasing ownership rather than increasing trusted coordination. The result is a platform that is technically central but politically unattractive. Partners join cautiously, share selectively, and hold back their best assets because they do not want to strengthen a proprietary gatekeeper.

For Philips, that is the key design challenge. The company does not need less control in the abstract; it needs the right kind of control. It should control the interfaces, quality standards, and system coherence that make a MedTech ecosystem reliable. But it cannot control the whole field so tightly that hospitals, AI developers, and academic centres feel they are simply feeding Philips’ next proprietary advantage. In behavioral terms, the ecosystem only works if other actors see enough gain, enough fairness, and enough autonomy to keep contributing.

Why the IIBE lens matters

This is exactly why the IIBE framework is useful here. It forces the question away from rhetoric and toward structure, and its full evaluation takes an organisation through extensive diagnostic and discovery so boards can see where their ecosystem design is strong, and where it quietly closes their options. Is Philips operating at company level while speaking at system level? Is it preserving strategic optionality or quietly closing it? Is it orchestrating a partner system or merely extending its own enterprise boundary?

Those are not abstract questions. They are board-level questions about capital allocation, governance design, trust, and future value capture. Philips’ fork is not simply whether to innovate more or cut harder. It is whether to remain a company-centred actor with ecosystem vocabulary, or become a genuine orchestrator of MedTech innovation in a world where no single player can own the whole stack.

The choice, stated plainly

So the choice now looks sharper than it first appears.

One path is familiar: keep running a Philips-led network, optimise extraction, limit experimentation, and accept a role as a strong but ultimately subordinate player inside larger architectures shaped by others.

The other path is harder but more consequential: build the governance, interfaces, and shared architecture that allow other actors to innovate around Philips without requiring Philips to fund all the experimentation itself. That is the only path by which a more disciplined Philips can still capture the upside of innovation at system scale.

What makes this more than an abstract choice is timing. The orchestrator role is still available in MedTech AI today; it will not be if two or three better-capitalized rivals succeed in entrenching their architectures first. In that scenario, Philips’ current Tier 2 position becomes the ceiling, not the starting point.

That is what makes Philips such a revealing case for business ecosystem thinking. It shows the difference between talking about ecosystems and building one. And it shows why, in turbulent times, the companies that still benefit from innovation are not always the ones that invent the most. Often, they are the ones that learn to orchestrate best.The Dutch government has bet that Philips can do the second. Roy Jakobs’ public language suggests he understands this direction.

The unresolved question is whether Philips is prepared to redesign not just its strategy deck, but its operating logic. In the next piece in this series, Paul Hobcraft uses the full IIBE to show what dynamic orchestration and adaptive governance look like in practice and needing to be applied to Philips through this IIBE lens, and how this can give boards a clearer basis for deciding which path to take and what to avoid.

The post Royal Philips: Metaphor or operating logic? first appeared on Applying Ecosystem Architecture.

Siemens offers three distinct IIBE stories related to Ecosystem building – each is within the expansion of ecosystem thinking and design. Different arguments applied to three related entities at different stages of the same structural transition. AI is only part of their solutions.

The need here is all about hitting ecosystem buttons across all of them with a fully developed evaluation, analysis and emerging proposition can offer the move that transforms individual conversations into something structurally compelling. This post outlines part of this and focuses on Ecosystem Architecture..

My work operates at the intersection of ecosystem architecture and AI strategy — specifically on how organisations principally design the governance and orchestration layer, that allows intelligence to compound across a multi-actor network rather than accumulate within a single node.

I see the architectural question as the “golden thread” that runs through these individual Siemens entities and their future direction each oif them can travel, if they recognize it as their essential next step.

Each Siemens entity is navigating increasing operational pressure in China, the US and Europe, a major leadership and preparation for full independence or changes of branding identity — all within the next 18 month window and further acceleration into Manufacturing and Technology entities.

Each Siemens entities need their own compounding value architecture — their own unique moat that is not just at product depth but built from genuine ecosystem orchestration intensity. The IIBE argument becomes a part of this post-independence strategic necessity, not just an interesting framework, applied today, but to bring this part of the strategic need to fruition for taking each entity to their next level of growth and value, in my view a compounding one.

Applying the IIBE lens to the three separate Siemens entities.

So, by applying my IIBE framework, especially the different lens application – which became the Siemens Ecosystem Architecture Assessment — that maps all three entities, their current positions, their structural gaps, and the compounding value that an IIBE architecture creates across and between them. Interestingly the present German Growth Dilemma needs all three Siemens entities within the next phase of German industrial competitiveness and why I think the ecosystem architecture argument unlocks part of this dilemma.

An ecosystem architecture asks a key question: who creates the value when that intelligence being collected moves or is not fully translated. Can organizations today leave on the table when all the potential for leveraging emergent partner value into more effective network effect strategic moats? It is the potential growth foundation of an ecosystem intelligence layer — one that creates value for every actor in the network and, in doing so, creates a form of strategic centrality that no competitor can replicate simply by building better products. This network effect becomes the unique moat, all involved can gain value.

I call this the “Living Bridge” where deliberate (dynamic) governance and intelligence architecture combines and makes the whole greater than the sum of its bilateral parts.

Lets be clear, a platform is not an ecosystem. A partnership network is not an ecosystem. Even a vision as compelling as screening to survivorship (Siemens Healthineers) is not, by itself, an ecosystem. Each of these things becomes an ecosystem when there is a deliberate architecture governing how intelligence moves, how actors create value for each other, and how the ‘whole’ compounds beyond what any bilateral relationship can produce.

The distance between ecosystem ambition and ecosystem architecture is not a criticism of where each of these Siemens entities are positioned today, they each offer today good shareholder returns. It is offering a precise description of where the next significant design decision sits to grow those returns further out.

Recognising What Ecosystems Actually Require

The most important shift in understanding that ecosystem architecture requires is this: an ecosystem is not a larger version of a partnership model. It is a structurally different thing.

Partnership models optimise individual relationships. Ecosystem architectures create conditions in which actors generate value for each other — with or without central coordination of each specific interaction. The orchestrator’s role shifts from managing relationships to designing the environment in which relationships self-organise productively.

So where are the three Siemens entities today – briefly:

Siemens AG — the orchestration maturity story

They have built the environment. They are executing strongly towards the transformation into a One Tech company program. Xcelerator as a well structured and positioned platform highly relevant and progressing, producing solid results, the partner network is real, the digital-physical convergence position is genuinely rare. The IIBE argument here is about the next phase of value creation — moving from platform provision to intelligent orchestration. Cross-industry pattern transfer, governance architecture that releases the divisions rather than constraining them, compounding network intelligence rather than hub-and-spoke data flows. The question becomes do they recognize they are pushing the current ceiling better than anyone but still hitting the ceiling?. The story for them is they have done the hard part. Here is what unlocks the multiplier on what they have already built and how.

Siemens Healthineers — the technology and data architecture story

This is the most complex and most sensitive of the three. The Healthineers is undertaking a leadership transition and the most intriguing part of this is Martin Stumpe. Stumpe founded the Cancer Pathology project at Google Brain, led AI for precision medicine at Tempus, then served as Chief Technology and AI Officer at Danaher before joining Healthineers as CTO from June 1. He is not a MedTech insider elevated through the Siemens system. He is a genuine AI architecture thinker arriving from outside — Google Brain, NASA, Danaher — with no prior loyalty to how the current Healthineers technology stack is structured.

My read — that Stumpe has been brought in to deliver something not yet publicly announced around technology and data extraction. The IIBE argument here is about what makes that data intelligence architecture genuinely compounding rather than proprietary and self-limiting. A data estate orchestrated across a governed multi-actor ecosystem — pharma partners, care pathway actors, payers, genomics — produces exponentially more intelligence than the same data estate held within a single organisation’s boundaries. The potential here is really exciting.

Siemens Energy — the resilience and maintenance moat story

This is the most counterintuitive of the three — and potentially the most interesting precisely because of that. Presently the order rush is consuming all available attention. When demand is this strong, the pressure to question the business model is essentially zero. Why redesign the engine when it is running at full speed?

They are about to go into a major rebranding effort where Siemens Energy is starting its preparations for independent brand launch bringing together Siemens Energy and Siemens Gamesa together under one name : Omterra. Why? When they were spun off from Siemens AG the Siemens license was available for a limited period. Rebranding is really tough especially from a recognized global name into what they are proposing: Omterra.

Siemens Energy is really growing into a compelling IIBE case study. The energy transition ecosystem challenge — how you orchestrate across renewables, grid technology, gas services, hydrogen, industrial decarbonisation — is arguably the most complex multi-actor ecosystem challenge in the global economy right now.

But that is exactly the moment when the structural question becomes most important — and mostly ignored from underpinning what is the potential within Siemens Energy. The maintenance contract contributions have provided an essential recurring revenue stream — the ongoing service relationships with installed base customers — is the embryo of an ecosystem position that no one inside the organisation has yet named as such. Those maintenance relationships are not just revenue. They are data, they are trust, they are operational intimacy with energy infrastructure assets across geographies and technology types. That is an ecosystem intelligence asset of extraordinary value — currently being harvested as a margin line rather than architected as a strategic moat.

The IIBE story for Siemens Energy is not about reframing the current business — it is about what happens when the order rush normalises and the competitive landscape shifts. Who owns the intelligence layer of the energy transition ecosystem?

Who governs the data flows between the physical assets, the grid operators, the industrial customers, the hydrogen producers, the storage operators? The company that architects that layer now, while the relationships are being built through the maintenance contracts for example within Siemens Energy, creates a moat that pure equipment manufacturers perhaps cannot replicate.

Schneider, GE Vernova, ABB, Honeywell Technologies, Rockwell Automation and others all have the potential to realize the value within Ecosystem design and thinking, all are at different levels of Ecosystem maturity. Who sees and grabs the potential taking data into intelligence and beyond into Knowledge and Network Effect Moats of unique value.

What this three-story map tells you about sequencing

Each story is at a different stage of organisational readiness.

Siemens AG is intellectually ready — they have the inbuilt vocabulary and the platform, the gap is named, the timing is immediate. Healthineers is structurally ready but the story is still forming — Stumpe needs time to land in role and define his agenda before the conversation has full traction. The window is three to six months. Siemens Energy is strategically ready but operationally preoccupied — the conversation will land when the order rush plateaus or when a board member has the space to think beyond current demand. The window — twelve to eighteen months — but the groundwork laid now will be invaluable when that independence moment arrives.

Each Siemens entity tells a story differently but the recognition of where Ecosystem thinking and design fits for positioning the future needs a higher level of strategic addressing.

The single most important observation

These are not three separate client conversations. They are moving towards one ecosystem argument applied to three related entities at different stages of the same structural transition. My “circling them” thinking independently – building the framework, seeding the thinking, accumulating the network about them for years with no commercial stake in their current architecture. That independence is the asset.

I feel I have been watching this transition develop from the outside and has built the only architecture that addresses what all three are now facing simultaneously, to help in the realization of Ecosystems and what it can mean to them.

The post The Siemens Evolution: three very different Ecosystem building stories hitting limits first appeared on Applying Ecosystem Architecture.

The Dual-Force Model of AI + Intelligent Integrated Business Ecosystem (IIBE)

AI Isn’t the Strategy: Why Ecosystems Are the Real Moat (and AI Is the Accelerator)

What this gives — above and beyond internal AI

Why an “AI-only” strategy plateaus

AI delivers real wins—productivity, cycle-time reduction, better forecasting, faster content and software creation. But in isolation, it tends to hit structural ceilings:

• It accelerates what you already know. If the training data and feedback loops are mostly internal, you become faster—inside a closed room.
• It commoditises quickly. Tooling spreads. Best practices spread. Your competitors catch up. Sustainable advantage moves to unique data and unique distribution.
• It struggles with cross-boundary complexity. Many real problems (supply chain resilience, regulatory shifts, decarbonisation, health outcomes) don’t sit inside one org chart.
• It can sound confident without being grounded. Models are excellent at fluent answers; they’re not a substitute for “ground truth” and external validation.
• It doesn’t create trust. Partnerships, co-investment, shared risk, and joint go-to-market still run on relationships and governance—not prompts.

So the strategic question becomes: if AI becomes ubiquitous, what stays scarce? In most industries, the scarcities are proprietary cross-domain data, distribution through partners, and coordinated judgment under uncertainty.

That’s where ecosystems enter.

The Dual-Force Model

AI + Intelligent Integrated Business Ecosystem (IIBE)

A definitive definition for strategy and innovation teams

What this gives — above and beyond internal AI

The AI + IIBE “dual-force” model: additive vs. multiplier effects

Think of AI as an engine: powerful, fast, and getting cheaper every quarter. An ecosystem is the road network: where the engine can go, what it can reach, and how much value it can create with others. Put differently:

• AI-only (additive): you do today’s work faster and cheaper.
• AI + IIBE (multiplier): you create new data, new distribution, and new joint capabilities—so the advantage compounds.

Concrete applications (where the dual-force model matters most)

• Systemic risk (supply chain, resilience, compliance): ecosystems provide early signals; AI turns them into scenarios and coordinated responses.
• Complex customer outcomes: when value depends on multiple actors (payer/provider, OEM/suppliers, public/private), AI helps orchestrate while the ecosystem provides the levers.
• Category creation: new markets usually require partners to align on standards, proof points, and routes to market—AI speeds the learning, but the ecosystem creates the market.
• Talent scarcity: ecosystems extend access to expertise; AI makes distributed knowledge searchable, reusable, and operational.

A quick checklist: are you building AI, or building an AI-powered ecosystem?

• Our top AI initiatives are tied to cross-boundary outcomes, not only internal efficiency.
• We have a clear view of which partners matter most for data, distribution, or credibility.
• We can name at least three data seams (handoffs/exceptions) we want to capture and learn from.
• We have shared governance (even lightweight) for decisions, data, risk, and escalation.
• We run at least one shared feedback loop where signals lead to action and learning.
• We’ve defined how we measure trust (privacy, quality, safety, performance, reliability) across the network.

Conclusion: AI accelerates—ecosystems compound

If AI is becoming ubiquitous, the durable advantage is less about having “more AI” and more about having a better environment for AI to learn, act, and create value: an ecosystem with shared outcomes, shared data seams, and shared governance. Build the ecosystem deliberately, then let AI do what it does best—compress time, surface patterns, and scale execution.

The post The Dual-Force Model of AI and Ecosystems first appeared on Applying Ecosystem Architecture.

Germany may be about to do something few believed possible: lose not just industrial output, but the industrial memory that made it Europe’s most admired manufacturing power. Since the pandemic, the country has lost nearly a quarter of a million manufacturing jobs, industrial production has fallen every year since 2022, and more than 31 per cent of industrial firms now say they are less competitive globally. Paul Hobcraft’s Intelligent Integrated Business Ecosystem (IIBE) offers a sharp way to read this. It helps explain how a country can still have world-class firms, skills and institutions, yet begin to lose the architecture that allows them to learn, align and adapt together.

Some will argue that Germany is simply going through the same shift every mature economy faces. Lower-value production moves elsewhere; higher-value engineering, design and coordination stay at home. In that reading, Germany is not declining. It is upgrading.

It is a neat story. It is also too easy.

The problem is that this argument confuses less production with better positioning. It assumes that when factories, specialist suppliers and production stages leave, the knowledge somehow stays behind. But industrial know-how does not sit neatly in patents, reports or strategy decks. It sits in repeated problem-solving between firms, in apprenticeship systems, in supplier relationships, and in the daily friction of making difficult things work well at scale. When enough of that disappears, a country does not just make less. It knows less.

That is why Germany’s current drift matters. The metals and electronics employers’ federation, Gesamtmetall, has warned that Germany is now “permanently damaged” as a business location. The market share of German carmakers in China fell by roughly a third between 2022 and 2025. The supplier base is under visible strain, and confidence among Mittelstand firms in the government’s ability to restore growth has dropped sharply. This is not normal industrial change. It is a system losing coherence.

Why the old strengths no longer hold by themselves

For decades, German industry rested on three powerful strengths: engineering quality, dense supplier networks, and trust built over time between large manufacturers and specialised Mittelstand firms. These strengths created something close to an industrial flywheel. The more firms worked together, the more knowledge accumulated; the more knowledge accumulated, the stronger the whole system became.

The mistake was to treat these strengths as permanent assets rather than as outcomes that had to be renewed. This is where the IIBE lens helps. It argues that durable advantage emerges in sequence. First, actors need good intelligence about what is changing. Then they need alignment around what matters. Then they need clear roles and decision rights. Only after that can a system build the kind of trust, network effects and defensible position that people like to call a moat.

Germany behaved as if the moat came first and would remain by default. It did not. As energy costs rose, competition intensified, and anchor firms shifted more activity abroad, the underlying conditions that reproduced Germany’s advantage began to weaken. What looked like a strong industrial base increasingly became a set of strong firms making individually rational decisions inside a weakening system.

A simple example of how memory is lost

Imagine a machinery cluster in southern Germany. A large anchor customer keeps its headquarters and engineering centre at home, but moves more production abroad to cut costs. That decision may look sensible in isolation. But it changes the local system.

A specialist component supplier nearby loses volume and delays investment. A smaller tooling company no longer gets early feedback from factory-floor changes and starts losing its edge. Fewer apprentices are hired because local demand looks less certain. The regional technical college finds it harder to place students. Nothing dramatic happens in a single week. But over a few years, the cluster becomes thinner, slower and less capable of solving difficult production problems together.

That is industrial memory loss. It is not one big closure. It is the gradual disappearance of the shared learning loops that once made the region distinctive.

What the IIBE reveals

The real value of the IIBE is that it does not just describe ecosystems in broad terms. It helps diagnose why they stop compounding.

One useful part of the framework is its system architecture stack. In plain terms, it asks four questions: what exists in the system, how it works, how it changes, and why it holds together over time. Germany still looks strong on the first question. It has major firms, specialist suppliers, training systems, research institutes and industrial capabilities monitor-industrial-ecosystems. The trouble starts with the next three.

How the system works is no longer clear. There is no shared logic for how firms, suppliers, policymakers and regional institutions should respond together when costs rise, markets shift and old export assumptions break down. How the system changes is also weak. Germany has plenty of data and warning signals, but limited capacity to convert them into joint adaptation. And why the system holds together has become uncertain. Is the aim still to defend old strengths, or to redesign Germany’s role in a new European industrial landscape? The answer is not obvious because the architecture has not been made explicit.

Another useful part of the IIBE is its diagnostic lens. It asks where coherence is breaking down. In Germany, five tensions stand out.

• Strategic direction is fragmented. OEMs, suppliers and policymakers are each reacting to pressure, but not around a clear shared direction for the system.
• Governance is reactive. Challenges in energy, skills, digitalisation and competition are handled separately rather than through a joined-up design of the industrial system.
• Learning is too weak. The country sees the signals, but does not turn them into coordinated response fast enough.
• Partner confidence is eroding. When smaller firms no longer believe the system can generate value for them, participation weakens.
• Resilience is thinning. After several years of declining production, the buffer that once made German industry feel unshakeable has worn down.

Germany has had the signals, but not the response

It would be wrong to say that Germany did not see the warning signs. The signals have been visible for years: weaker competitiveness, rising energy costs, supplier strain, a shrinking foothold in China, and growing uncertainty in industrial investment.

The deeper problem is that signals do not matter unless a system can make sense of them together and act on them together. This is another place where the IIBE is useful. It distinguishes between sensing, meaning and flow. A system can collect data. It can even spot patterns. But unless those patterns are turned into shared judgment and then into coordinated movement across actors, the data changes very little.

Germany has largely had sensing without enough meaning and flow. Business groups warn, survey results deteriorate, policymakers debate, firms adapt one by one, and the overall system continues to drift. The issue is not the absence of information. It is the absence of a strong enough architecture to turn information into collective redesign.

Why this matters for different readers

If you lead a large German industrial company, this article should feel uncomfortable. Decisions that make sense for your balance sheet can weaken the supplier coherence and regional intelligence that your future competitiveness still depends on. You may be optimising your footprint whilst quietly hollowing out your own ecosystem.

If you run a Mittelstand firm, the article offers a different kind of clarity. It explains why operational discipline alone no longer feels sufficient. The issue is not simply that costs are up. It is that the system around you is becoming less coherent. The question is no longer only how to survive. It is which future ecosystem you want to be part of, and what role you want to play in it..

If you shape policy, the implication is sharper still. Subsidies and rescue measures may slow decline, but they will not rebuild industrial strength if the underlying architecture remains broken. The real task is to redesign how actors coordinate, how intelligence is shared, and how adaptation is organised across the system.

Where Germany could start

This does not mean trying to save every factory or reversing every offshoring move. It means selecting a few places where Germany still has dense capabilities and where better coordination could restart compounding.

That is where the IIBE idea of a proving ground becomes useful. A proving ground is a bounded domain where the actors already exist, the strategic stakes are high, and the structural confusion is visible enough that a focused intervention can reveal what needs redesign.

Germany has several such candidates.

• Advanced automation and robotics, where German firms still have depth but need stronger coordination to avoid losing control of the wider system monitor.
• Industrial energy systems, where the transition to cheaper, cleaner and more reliable energy demands coordination far beyond any single firm.
• Precision manufacturing supply chains, where the Mittelstand still holds specialist strengths but needs clearer roles, stronger shared learning and better long-term incentives.

In practical terms, a proving ground would mean three early moves. First, map the real actors, dependencies and bottlenecks in one domain. Second, identify where learning, governance and incentives are breaking down. Third, redesign the minimum rules, roles and data-sharing needed to get the system compounding again. The aim is not a grand national plan. It is to create a few places where Germany learns how to become adaptive again.

The story this tells

Germany still has the talent, the capital, the research strength and the industrial depth to matter enormously in Europe’s next industrial chapter. But that will not be enough if the system that connects those strengths keeps thinning out.

The real danger is not that Germany suddenly stops being good at engineering. The danger is that it remains good at engineering whilst losing the ecosystem conditions that made that engineering powerful at scale. That is what industrial memory loss looks like.The memory is still there. But it is no longer safe.

The post Germany’s industrial memory loss: Why an engineering engine is losing the ecosystem play first appeared on Applying Ecosystem Architecture.

Current accounting fails ecosystems. Traditional accounting assumes assets wear out, value declines with use and treats relationships as expense, knowledge is seen as overheads, coordination is a cost and trust is intangible and is left untracked.

Ecosystem assets are the capital class that becomes more valuable every time it is used. Investing in them is not a cost – it is the foundation of compounding advantage. In some ways applying this logic offers a real breakthrough, it reframes the entire investment conversation in ecosystems – and you can turn compounding from a metaphor into a management system.

It is time for us to consider treating Ecosystem assets as an appreciating capital asset class – because they grow stronger through use – and our accounting must shift from measuring cost/return to measuring what is being built and how fast it appreciates.

*** Depreciation logic was built for assets to die.

Most organisations that attempt ecosystem strategy eventually face the same frustration: the investment case never quite holds together. Early returns are modest. The assets being built — knowledge pools, trust networks, partner capabilities, shared intelligence — do not appear on the balance sheet. The CFO asks what the ROI is. The answer requires a level of abstraction that the finance function cannot operationalise. The capital allocation conversation stalls. Investment is reduced. The ecosystem underperforms. The original skepticism is confirmed.

Restricting Leaders on the realization of Ecosystems

One could even go further here “depreciation logic doesn’t just mis-value ecosystem assets – it actually forces leaders into making poor decisions that can structurally weaken their future”
 
The most important ecosystem assets are systematically under-valued by standard accounting logic — because they appreciate through use, and accounting assumes assets depreciate through use. This is not a technicality. It is the structural cause of chronic ecosystem under-investment.

I would argue you cannot build a compounding ecosystem with a depreciation worldview.

Why? Because in ecosystems:

• knowledge pools deepen with use and exploration (think of AI here)

• trust capital strengthens with repeated interactions and establishing common positions

• relationship networks expand and bring new value and diversity of understanding

• capability combinations multiply and build a greater robustness

• AI and digital intelligence compound and bring new perspective and understanding

• Adaptive capacity simply accelerates

These are compounding assets whose value increases through combination, coordination, shared intelligence, partner capability, repeated use, network reinforcement and AI-driven learning loops.

The new investment logic is replacing the old question “what does this cost and what does it return” with the new, ecosystem-aligned question “What does it build, and at what rate does what is being built appreciate?”

This feeds the logic of compounding value systems:

• value grows non-linearly
• returns accelerate over time
• the asset base strengths with use
• the system becomes more intelligent
• the ecosystems becomes more adaptable

This is a category-defining shift as it reframes ecosystem investment from

• Expense into new capital formation
• project into new capability
• output into new intelligence
• deliverables into new compounding engines of value and opportunity.

Thinking in appreciating assets enables boards and more importantly CFOs a way to see, value and justify ecosystem investment using a logic that matches how ecosystems actually create value.

Is this the missing accounting logic that is holding ecosystems back?

The not-so obvious insight here is by classifying ecosystems assets as appreciating you unlock

+ New valuation models

+New investment theses

+New governance structures

+New growth strategies and

+New balance-sheet categories

More importantly you finally rid yourself of that absurdity of treating trust, intelligence and partner capability as “soft” or “intangible.

We need to “chase” the hardest assets to build and the strongest drivers of compounding growth

The three governance shifts that need to be considered

Implementing the appreciating asset framework within existing governance structures requires three specific shifts in how investment decisions are structured and reported:

• Replace depreciation reporting with appreciation tracking: for the six ecosystem asset classes identified, replace the depreciation/amortisation line with an appreciation trajectory report. This is a management reporting change, not an accounting change. It requires defining the appreciation measures for each asset class and including them in the strategic performance dashboard alongside financial metrics.

• Establish a compound return horizon: ecosystem investment decisions should be evaluated against a compound return horizon — typically three to five years — rather than a single-period ROI. This requires the strategy and finance functions to agree on a compound return model: what is the architecture’s compound rate today, what is the target rate, and which investments raise the rate most efficiently? This is analogous to the discount rate conversation in conventional capital allocation — it requires the same rigour but operates on a different logic.

• Protect architecture investment from operational pressure: the most common cause of ecosystem underperformance is not poor design; it is the systematic defunding of Horizon 3 architecture investment under Horizon 1 operational pressure. The appreciating asset framework provides the governance argument for protecting this investment: it is not overhead, it is appreciation. Cutting it does not save cost; it reduces the compound rate of the architecture’s most valuable assets establishing the long term value of Ecosystems.

Finally

The organisations that govern ecosystem investment well are not those with more sophisticated accounting. They are those that ask a different question: not ‘what does this cost and what does it return?’ but ‘what does this build, and at what rate does what it builds appreciate?’

** Extracts from a paper “Appreciating Assets: A New Investment Framework for Intelligent Ecosystems” by Paul Hobcraft

The post Treating Ecosystems as a new asset class first appeared on Applying Ecosystem Architecture.

Most organisations today are trying to move faster than the system they sit inside.
The slowdown isn’t execution. It’s structural.

They are operating inside ecosystems —
but without an ecosystem architecture.

And that missing architecture is now one of the most important, least recognised constraints on growth, innovation, and transformation.

Why this architecture is missing

Ecosystems emerged faster than the organisational tools around them are built to manage them.
Companies built:

• strategies,
• operating models,
• digital platforms,
• partner programs,
• transformation offices,
• innovation portfolios,

…but none of these were designed for multi‑actor systems where value is created between organisations, not inside them.

The result is predictable:

• ecosystems exist,
• ecosystem language exists,
• ecosystem ambition exists,

but ecosystem architecture does not.

No one ever built the structural layer that aligns:

• actors,
• capabilities,
• intelligence,
• incentives,
• and value creation potential

across the system.

So every organisation is left trying to accelerate inside a system that cannot absorb the acceleration.

What an ecosystem architecture achieves

An explicit ecosystem architecture turns an ecosystem from:

• a collection of partners,
• a set of platforms,
• a network of relationships,
• or a portfolio of initiatives

into an intelligent, adaptive system that can:

• sense,
• learn,
• coordinate,
• and compound value
  across actors.

It aligns strategy, capability, and value creation potential across:

• your partners,
• your portfolio,
• your product offering,
• and the wider system you depend on.

It gives leaders something they’ve never had before:

a structural view of the system they are trying to change.

What is gained when organisations finally consider this

When organisations adopt an explicit ecosystem architecture, three things happen immediately:

1. Friction becomes explainable

The delays, stalls, and boundary failures that looked like “execution issues” suddenly reveal themselves as structural misalignments.

2. Progress becomes predictable

You can see where the system will resist, where it will accelerate, and where alignment is possible — before investing time, money, or political capital.

3. Value creation compounds

Capabilities stop working in isolation.
Partners stop moving at different speeds.
Digital and AI stop scaling in pockets.
The system begins to behave as one coherent whole.

This is the shift from:

• ecosystem as aspiration
  to
• ecosystem as architecture
  to
• ecosystem as advantage.

Why leaders fail to see this — and why it matters now

Leaders see the symptoms:

• pilots that don’t scale,
• data that doesn’t flow,
• partners that don’t align,
• AI that works locally but not across the chain,
• initiatives that slow at the boundaries,
• value that fragments across actors.

But they rarely see the cause:

the system has no architecture.

And without that architecture:

• innovation fragments,
• digital stalls,
• transformation slows,
• partnerships underperform,
• and strategy becomes disconnected from capability.

This is why an explicit ecosystem architecture is now one of the most important missing pieces in modern organisations.

It is the layer that explains everything they are struggling to resolve —
and the layer that unlocks everything they are trying to achieve.

The IIBE offers the architecture to resolve this problem

What is important is that the Ecosystem Architecture Positioning needs to be Executive-Ready but it really does need to be recognized as the problem to be resolved to unlock your ambitions, growth and value opportunities .

Without the architectural structure Ecosystems perform well below their potential in value, return and growth ,

The time is to change that and that is through the IIBE – the framework for managing Business Ecosystems

The post The Business Ecosystem Architecture needs to be Executive-Ready first appeared on Applying Ecosystem Architecture.

Most companies still underestimate what “ecosystem” really means and why they need to go deeper into the causes of their Ecosystems not delivering what they would want. .

They think it’s a partner program. Or a platform. Or a digital initiative. Or a slide with circles and arrows.

But here’s the shift that’s already happening — quietly, structurally, and faster than most leaders realise:

Your business is no longer operating in a market. It’s operating in an ecosystem.

And that changes everything.

I wrote recently “Business Ecosystems are more than your Companies thinks they are” focusing on seven of the bigger companies and their lack of fully developing and working through Business Ecosystems. Each of them is falling short in my analysis. This post is a shorter “awareness bridge”.

These seven organizations are

Siemens Healthineers, Hitachi Energy, ABB, Maersk, Johnson Controls, DHL, Allianz

I could name many more failing at extracting the real value of Ecosystems for their business.

Because when your growth depends on actors you don’t own, don’t control, and can’t replace — utilities, ports, regulators, integrators, OEMs, hospitals, carriers, developers, insurers, cities — you’re no longer dealing with “collaboration.”

You’re dealing with architecture.

And this is where so many organisations — even the most advanced — are stuck:

• They’ve already launched ecosystem initiatives.
• They’ve already felt the stall, the friction, the incoherence.
• They’ve already paid for the missing capability.
• They just haven’t named it yet.

Ecosystem architecture.

Not technology. Not partnerships. Not platforms. Not integration.

Architecture.

The structure that makes multi‑actor value creation actually work.

I’ve been analysing seven major companies across energy, industry, logistics, insurance, and healthcare — and the pattern is unmistakable:

They’re all ecosystem‑dependent. They’re all ambitious. They’re all stuck for the same reason.

If your organisation is feeling this tension, you’re not alone — and you’re not imagining it.

You’ve crossed a line. The operating environment has changed. And the tools you’ve been using were built for a world that no longer exists.

I’ve written a deeper piece on this shift — and why ecosystem architecture is becoming the defining capability of the next decade.

If you’re sensing this rupture in your own organisation, this will resonate:

Business Ecosystems Are More Than Your Company Thinks They Are

The post Underestimating what ecosystems really need first appeared on Applying Ecosystem Architecture.