Ecosystem Design and Thinking - Building Your Innovation & Ecosystem Intelligence

The Financial Absurdity: Why 1920s Accounting Is Killing 2026 Ecosystem Value

Measuring the Ecosystem Value that Compounds

Ask any CFO what happens when a factory machine, a truck, or a software license gets used every day, and they will give you the standard accounting answer: It depreciates. It wears down, loses value, and eventually gets written off.

Now ask that same CFO how they balance sheet a multi-partner AI network, a shared data infrastructure, or a collaborative industry ecosystem. They will apply the exact same logic. They will mark it down as an operational cost or let it depreciate.

Also how many times have you found your development project, full of future potential, get stopped because of funding constraints or annual reviews and that constant questioning of “where is the return of investment?” Yet the promise, learning and exploring new avenues of intelligence have all been deemed as a full cost and fully depreciated, not recognised for their future value of the knowledge gained.

Does that make sense? When something improves, expands in knowledge and the more it is “used” it appreciates in understanding and value yet it gets the depreciate treatment.

This is a massive financial paradox.

Enterprises are pouring billions into artificial intelligence, multi-actor alliances, and dynamic supply chains, yet they evaluate these investments using accounting rules invented during the Second Industrial Revolution. We are running 21st-century intelligent ecosystems on financial models built for factories and accounted for with rules invented during the Second Industrial Revolution.

Emergence: Converting Ecosystem Intelligence into Knowledge and Value

From Flow to Knowledge provides New Emerging Value

Emergence occurs when we are converting Ecosystem Intelligence into Knowledge and Value

The architecture that breaks through the four invisible ceilings does not replace what organisations have built. It elevates it — transforming accumulated intelligence into flowing knowledge, that provides the new value that compounds with every actor the network touches making their contributions. We are achieving the power with Ecosystems

Emergence: Converting Ecosystem Intelligence into Knowledge and Value

It is not always visible when it happens. The investment continues. The partnerships are active. The platforms are performing. The AI is deployed. And somewhere in the gap between what the ecosystem is producing and what the original ambition implied it would produce, a different question begins to form — not how do we do this better, but what does this become when it is designed differently.

This is the third part of a three part series : From Flow to Knowledge: Moving Ecosystem Intelligence into Value

This post three delivers the architectural answer — the transition from accumulation to flow, fusion as what flow makes possible, the Living Bridge as the institutional function that holds dynamic orchestration and adaptive governance together, and emergence as what becomes possible when the design is right. Closes with the invitation rather than the prescription.

Here we explore what the Sensing-Meaning-Flow diagnoses within the ceilings that are presently stopping an organisation to “break through” and build new value. Applying a sequence of Flow-Fusion-Emergence breaks through it and converts what was stalling into compounding knowledge value. What emerges converts Intelligence into Knowledge and new Value that looks to Compound.

This sits within the beating core of the IIBE framework, its intelligent engine

Royal Philips: Will It Shape the MedTech System — or Be Shaped by It?

Royal Philips- Shaping or Being Shaped for its MedTech future?

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.

Royal Philips: Metaphor or operating logic?

Philips faces a strategic fork: remain a company‑centred network that contributes into others’ systems, or step up as an ecosystem orchestrator that shapes how value, data and innovation flow across the field. Using the IIBE lens, this article shows why neutral governance, open architectures and dynamic orchestration matter – and how they can help Philips avoid becoming a subordinate contributor while rivals lock in the upper tier.

Infographic showing Philips’ strategic fork with two paths: Tier 1 ecosystem orchestrator with neutral governance, open platforms and strategic optionality, and Tier 2 subordinate contributor with a company‑centred network, control trap and subordinate trajectory. — Philips must choose between staying a company‑centred contributor or becoming a true ecosystem orchestrator, using neutral governance and open platforms to unlock innovation at system scale.

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.

The Siemens Evolution: three very different Ecosystem building stories hitting limits

Billions invested in components are yielding linear returns. Think Ecosystems

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.

Siemens Healthineers are missing a beat or two in Ecosystem Management

Working with Ecosystems. Logo is copyright of Siemens Healthineers

In my research to build out the diagnostic framework of the Intelligent Integrated Business Ecosystem (IIBE) it has been aimed specifically at organisations with ambitions of building towards something like the Siemens Healthineers’ stage: that of building extraordinary assets, holding genuine ecosystem ambition, but the orchestration architecture not yet designed as the essential missing piece.

I find Siemens Healthineers an organisation where you can build a detailed case study around this core positioning of the IIBE

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.

If you take their Varian integration as an example, It is is one of the clearest live cases I can find in healthcare. The acquisition thesis was ecosystem logic. The integration execution has been operational logic. Those two things require different architecture to reconcile — and that gap is where the most significant value is currently sitting not fully captured.

Germany’s industrial memory loss: Why an engineering engine is losing the ecosystem play

Germany may be about to do something few thought possible: lose not just factories and jobs, but the industrial memory that made it Europe’s most admired manufacturing power. Using Paul Hobcraft’s Intelligent Integrated Business Ecosystem (IIBE) lens, this article argues that Germany’s core problem is not a lack of engineering talent, but a failing ecosystem architecture. It explores how offshoring, fragmented governance and weak learning loops are dissolving supplier coherence and regional capabilities, and shows why moats like “Made in Germany” were structural outcomes, not birthrights. Finally, it outlines where a realistic reset could start – in targeted proving grounds around automation, industrial energy and precision manufacturing – and what OEM leaders, Mittelstand owners and policymakers must each do if Germany is to remain a serious industrial force in the next European chapter.

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 Business Ecosystem Architecture needs to be Executive-Ready

Accelerating inside our existing system is increasingly hard

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.

Underestimating what ecosystems really need

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.

Business Ecosystems are more than your Companies thinks they are

Recently I have been evaluating a cohort of Seven leading companies on where they are on Business Ecosystem thinking

The seven organizations are

Hitachi Energy
ABB
Maersk
Johnson Controls
DHL
Allianz
Siemens Healthineers (not Siemens AG)

Firstly you gain the universal tension they all feel

Firstly, it seems every company is caught in the same structural bind:

Their value creation now depends on actors they don’t control
(utilities, ports, regulators, integrators, OEMs, hospitals, carriers, developers, insurers, cities).
Their strategic bets require multi‑actor coordination
(energy transition, digital grids, smart buildings, logistics visibility, embedded insurance, connected care).
Their existing operating model is built for bilateral relationships, not multi‑actor ecosystems.
Their platforms and digital initiatives have already shown the limits of “technology + partners.”

This is their shared pain point they all can elevate into a compelling need for Ecosystem change if they have the 1)ambition and desire and 2) the understanding of what it takes..