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 Building Your Innovation & Ecosystem Intelligence.

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 Building Your Innovation & Ecosystem Intelligence.

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 Building Your Innovation & Ecosystem Intelligence.

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 Building Your Innovation & Ecosystem Intelligence.

I have been building out a series of IIBE Framework papers looking at how the European Union through its European Innovation Council (EIC), a major EU initiative supporting deep-tech startups and research, can move its new scaling mandate underpinned by deploying a recently announced Euro 5 Billion fund.

The EIC is the right institution for this. Not because it is the only EU institution with a scaling mandate, but because it is the only institution that already operates above the national interest level, already has portfolio-level visibility across node types, and is already at the moment — the first Scaleup Europe Fund investment tranche — when integrating this governance architecture is most effective. The extension of EIC’s remit from financing scale to governing the ecosystem conditions for scale is not a departure from its mandate. It is the logical completion of it.

I worked through four documents looking at a combination of ideas that look to challenge political geography and optimize functional architecture. We should look for imaginative ways for true ecosystems of capital, intelligence, connections and resources can flow freely to the points where that expertise is the strongest across Europe. We need to think beyond boundaries into optimized performance. Can we think differently across Europe when it comes to innovation, make our institutional flows stronger?

My first document looked at a different way to overcome the existing country or entity (allocation and rigidity issue) for a higher level of optimizing the system. Not who gets allocated at country level the central funds. As the EU has a default unit of analysis on country they inhibit how ecosystems can generate and compound value.

The right unit is the node, a structured unit defined by its function. Where a country asks “what do we produce?”, a node asks “what structural function do we perform, and for whom?” The EU-27 as a Node System has real merit to explore. This paper argues that the European ecosystem’s scaling challenge is not primarily a funding challenge. It is a governance architecture challenge. The node map of Western Europe reveals an ecosystem with extraordinary latent capability. The concept of nodes as the architecture for Ecosystem across Europe offers European sovereign advantage.

What Europe has not built is the node architecture that converts those positions into compounding systemic advantage. The control points generate revenue and geopolitical relevance. They do not generate the self-reinforcing cycle of intelligence flow, governance adaptation, and systemic advantage that defines a genuinely intelligent integrated ecosystem. My second document deals with control points.

My second document was looking at genuine control points, those positions of structural irreplaceability in global technology and value chains. The issue is compounding. Control points are a specific position in a technology stack, standards architecture or infrastructure layer at which a single actor holds a capability that the rest of the system requires and cannot replicate easily or bypass. ASML is a good example. They are irreplaceable and offer system dependency. Europe holds irreplaceable leverage here and it is looking at these control points as greater compounding ones. These can scale faster and hold European sovereignty.

The control point generates revenue and employment but does not compound into broader systemic advantage, because the node architecture that would allow it to do so is absent. The control point is an isolated asset, not a system-level lever.This is the dominant European failure mode — and it is directly visible in the EIC’s existing portfolio.

Europe has invested — sometimes deliberately, often accidentally — in acquiring control points of genuine structural significance. ASML, Ericsson/Nokia, SAP, imec, Airbus, and the Brussels Effect regulatory architecture are not minor competitive advantages. They are positions of irreplaceable leverage in global value chains that the rest of the world’s technology system depends on.

My third document is shifting thinking from Capital Scale to Ecosystem Scale and the governance architecture for the EIC Scaleup Europe mandate. This looks at different scaling ambitions and their structural limits.The EIC’s 2026 trajectory is clear and significant. The Scaleup Europe Fund — with EQT appointed as fund manager and €2.5 billion already committed from the EIC and private LPs including Novo Holdings, Allianz, APG, and the Wallenberg family — represents Europe’s most concrete attempt to prevent foreign capital from acquiring its best technology before it scales. That ambition is correct. But the architecture does not yet match it.

The EIC’s scaling mandate is the right ambition. But deploying €5 billion into companies that hold Europe’s most significant control points, without the node architecture to compound their leverage, produces larger isolated assets — not structural advantage.

My fourth document is where this post is directed at– building a Fusion Readiness Assessment. I am suggesting when an idea is ready to scale, will it have scaling compound.

Let me explain this Fusion Assessment in some detail.

The Problem the EIC Has Not Yet Solved– Fusion

The EIC funds ideas. It develops them, tests them, accelerates them. At each stage of its pipeline — Pathfinder, Transition, Accelerator — it applies criteria to determine whether an idea is ready to move forward. Those criteria are good ones: technology readiness, market validation, team quality, financial milestones.

They assess the idea. They do not assess whether the ecosystem around the idea has reached the conditions under which scaling will compound rather than merely grow.

That distinction is the problem the Scaleup Europe Fund is trying to solve with capital. More money, larger rounds, later stage. But capital deployed into an idea before its ecosystem has reached the decisive inflection point produces a larger, better-funded isolated asset — not a self-sustaining compounding system. The idea grows. It does not compound.

The Fusion Readiness Assessment is the missing instrument. It sits alongside existing EIC criteria — not replacing them — and answers the question that those criteria cannot: has this idea and the ecosystem around it reached the point at which scale capital will compound?

The Fusion Progression in Five Stages

The Fusion Progression describes the natural journey of an idea moving through its ecosystem toward self-sustaining scale. It has five stages. Each stage has its own character, its own observable signals, and its own implication for how the EIC should position its support.

At this stage the idea is still seeking — seeking connections, seeking capital, seeking partners, seeking market entry. But something has shifted. The direction of movement is beginning to reverse. Occasional inbound interest is appearing that was not created by the company. An industry actor has made contact without being approached. A potential partner has reached out. A researcher has cited the work.

These are small signals. They are not yet structural. But they are the first indication that the idea has developed sufficient mass to begin attracting rather than only pushing. Gravitational Pull is the earliest Fusion precursor — the signal that the approach to the decisive inflection point has begun.

At this stage the EIC’s role is to strengthen the idea’s mass: deepen the technology, sharpen the market position, begin building the ecosystem connections that will become the infrastructure of attraction. Node proximity matters here — an idea developing within or adjacent to a high-density node environment develops gravitational pull faster because the structural elements that enable attraction are already present around it.

Attraction is Gravitational Pull becoming structural. The occasional inbound signal has become a pattern. Industry actors are orienting toward the idea across multiple dimensions simultaneously — commercial interest, partnership approaches, talent movement, capital positioning. The idea has become a reference point in its domain.

The decisive test at this stage is whether the attraction is self-generating or EIC-dependent. If the inbound interest disappears when EIC support is withdrawn, it is not yet genuine Attraction — it is reflected light from the EIC’s own authority. Genuine Attraction continues and grows without the EIC’s active promotion. The idea is pulling under its own gravity.

This is where the ecosystem compounding potential signals become readable. Are connections between actors around the idea multiplying rather than adding? Is the intelligence generated by the idea circulating through the ecosystem rather than staying within the company? Are control points in the proximity beginning to orient toward the idea as a domain of interest? These are the Form signals — the evidence that structure is beginning to coalesce around the idea’s gravitational field.

Fusion is the decisive inflection point. It is not a company milestone. It is an ecosystem event — the moment at which the intelligence generated by the idea, the structural form that has coalesced around it, and the governance coherence of the surrounding ecosystem combine to produce something self-sustaining.

Capital is now attracted rather than deployed. Adjacent actors activate without being connected. The policy environment is beginning to reflect and react to the idea as a new field of opportunity. The two hard validators — competitive response from incumbents and entanglement through ecosystem roots — are both becoming visible.

The EIC’s role changes at Fusion. Before Fusion, the EIC is scaffolding — keeping the idea alive, building its connections, strengthening its ecosystem position. At Fusion, the EIC shifts to steering — directing the compounding that is now self-generating toward outcomes that serve European sovereign interests. This is the validated handover point for Scaleup Europe Fund investment.

Post-Fusion, the idea’s ecosystem is in active compounding. New actors are entering without being recruited. Capital is arriving without being summoned. The rate of connection, capability accumulation, and intelligence generation is increasing rather than plateauing. Each new connection multiplies rather than merely adding.

This is where Scaleup Europe Fund capital lands with maximum effect. Not creating momentum — the momentum already exists — but amplifying and directing it. The EIC’s role here is not to generate attraction but to ensure that the compounding is happening within European ecosystem infrastructure, deepening the entanglement that makes the idea unmovable.

The final stage of the Fusion Progression is the clearest evidence that an idea has fully compounded into structural significance. New fields of opportunity are becoming visible — adjacent applications, derivative ideas, new markets, new domains — that were not conceivable at the idea’s outset. These are emerging not from within the original company but from the broader ecosystem that has grown around the idea.

The idea has become infrastructure. It is being built upon. This is the point at which Pioneer-mode policy engagement becomes appropriate — not reacting to the idea but actively shaping the institutional architecture of the new field it has opened. And it is the point at which the EIC’s next investment generation is identified: the new ideas emerging from the field of opportunity this one has created.

The Assessment in Practice

The Fusion Readiness Assessment is designed to be conducted as a structured conversation between an EIC programme manager and the founding team, informed by the programme manager’s own market and ecosystem intelligence. It is not a form to be completed or a box-ticking exercise. By offering a signal grading, this is a discipline for honest observation, not a mechanical scoring system.

The output is a Fusion Readiness Signal Map: a simple visual representation of where the green, amber, and red signals sit across the three clusters and two Hard Validators. The map tells the programme manager, at a glance, where the idea is in its Fusion Progression and what the appropriate EIC response is.

The Scale Delivery End Point

Everything in the Fusion Readiness Assessment is in service of one outcome: the idea reaches self-sustaining scale that delivers the impact it was funded to deliver. Not a larger portfolio company. Not a stronger EIC track record. Not a better-governed ecosystem as an end in itself.

Delivered scale. In Europe. Compounding. The Fusion Progression describes the path.

There is more within the detail of the paper but the assessment stages are outlined for bringing scale and compounding together

Scale attraction and ecosystem compounding potential are the conditions we must strive for. Fusion is the moment they combine. The Scaleup Europe Fund is the instrument. European sovereign advantage — built through entanglement, anchored through node and control point integration, compounding through the intelligence the ecosystem generates — is the end point. This builds the Fusion State we need

We need to build intervention to accelerate the approach to Fusion. To scale, to compound we move towards fusion.

The post Adding Fusion into the European Innovation Scaling Mix first appeared on Building Your Innovation & Ecosystem Intelligence.

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 without an ecosystem architecture:
the missing layer that aligns capabilities, intelligence, and value creation across partners, portfolios, and products.

The Intelligent Integrated Business Ecosystem (IIBE) provides that architecture. It turns ecosystems from fragmented networks into intelligent, adaptive systems that can sense, learn, and coordinate — so strategy, capability, and value creation move together, not apart.

If you’re feeling the limits of the system around you, the IIBE makes those limits visible — and solvable.

The Structural Problem Modern Organisations Can’t See

Across every sector — energy, industry, logistics, healthcare, finance — organisations are trying to accelerate innovation, digital transformation, and new value creation.

We need to recognize organizations are doing so inside systems that were never designed to move with them. Most systems were designed for the single organization, keeping its knowledge and insights inside the organization. Sharing if at all was strictly bilateral.

The world is different today, we seek to share and exchange. We strive for more knowledge and insights. We contribute alongside others to tackle and solve more complex problems, that is the rise of Ecosystems.

If we don’t adapt and change the result are familiar to recognize:

• initiatives that slow at the boundaries
• digital and AI that scale locally but not across the chain
• partners moving at different speeds
• data and intelligence trapped in silos
• value creation that fragments across actors

These are not execution failures.
They are structural symptoms of a deeper issue:

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

Why Ecosystem Architecture Is Missing

Ecosystems emerged faster than the organisational tools built to manage them.
Companies built strategies, operating models, digital platforms, partner programs, and innovation portfolios — but none of these were designed for multi‑actor systems.

Ecosystems became real.
Ecosystem language became common.
Ecosystem ambition became strategic.

But the architecture — the structural layer that aligns actors, capabilities, incentives, and value creation — never emerged.

This is why organisations feel like they are pushing against something they can’t see.
They are trying to accelerate inside a system that cannot absorb the acceleration.

What an Ecosystem Architecture Achieves

An explicit ecosystem architecture transforms an ecosystem from:

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

into an intelligent, adaptive system that can:

• sense what is happening across actors
• learn from distributed intelligence
• coordinate decisions and movement
• compound value rather than fragment it

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

• partners
• portfolios
• products
• and the wider system the organisation depends on

This is the shift from ecosystem as aspiration to ecosystem as advantage.

What Organisations Gain When They Finally See the Architecture

When leaders adopt an ecosystem architecture, three things change immediately:

1. Friction becomes explainable

The delays and breakdowns that looked like execution issues 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 moment when organisations stop fighting the system —
and start architecting it.

The Role of the IIBE

The IIBE is the first architecture designed specifically for modern ecosystems.
It gives leaders a structural view of the system they are trying to change — and a way to evolve it with clarity and confidence.

It is not a methodology.
It is not a framework.
It is an architecture:
a way of seeing, designing, and evolving the ecosystem as an intelligent, adaptive system.

For organisations feeling the limits of the system around them, the IIBE makes those limits visible — and solvable.

We need to recognise what limits our Ecosystem ambitions

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

• We’ve entered a world where value is created across partners, platforms, regulators, suppliers, customers, and data flows that no single organisation controls. In other words: every organisation now operates inside an ecosystem.

• But almost none have an ecosystem architecture — the structural layer that aligns capabilities, intelligence, and value creation across the system.

That missing architecture explains the patterns leaders keep seeing:

• pilots that don’t scale • digital and AI that work locally but not across the chain • partners moving at different speeds • data that doesn’t flow end‑to‑end • initiatives that slow at the boundaries

These aren’t execution problems. They’re symptoms of a system with no architecture.

The IIBE was built to make that architecture explicit.

It turns ecosystems from fragmented networks into intelligent, adaptive systems that can sense, learn, and coordinate — so strategy, capability, and value creation move together, not apart.

The time to recognize the missing architecture is now so you can turn your Ecosystem ambitions into a growing reality of greater growth, impact and value.

We need this scaffolding to be built in a complex world where we can exchange, share and build on combined knowledge and insights

The post Forget the Component Approach think Ecosystem Architecture first appeared on Building Your Innovation & Ecosystem Intelligence.

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 Building Your Innovation & Ecosystem Intelligence.

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 Building Your Innovation & Ecosystem Intelligence.

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..

The narrative that makes them recognize that Ecosystems are unavoidable

“Your next decade of growth depends on actors you don’t own, don’t control, and can’t replace. That’s an ecosystem condition — and it requires an ecosystem architecture.”

This reframes ecosystems as:

• a structural reality, not a strategy choice
• a capability gap, not a marketing theme
• a board-level risk, not a digital initiative
• a source of competitive advantage, not a partnership model

This is the rupture that is or will take place that should make the senior executives responsible (CEO down) lean in and take note

Let me give three reasons ecosystems become a compelling investment

These are universal across Hitachi Energy, ABB, Maersk, Johnson Controls, DHL, Allianz, Siemens Healthineers.

1. Their strategic bets cannot scale without ecosystem coherence

Energy transition, smart buildings, logistics visibility, embedded insurance, connected care — all require multi‑actor alignment.

If the ecosystem doesn’t work, the strategy doesn’t work.

2. Their existing ecosystem attempts have already shown the cracks

TradeLens, ABB Ability resets, OpenBlue repositioning, DHL platform consolidations, Allianz ecosystem pilots, HealthSuite fragmentation.

They’ve already paid the price of missing architecture.

3. Their competitors are moving faster in ecosystem posture

Siemens AG’s Xcelerator is the clearest example — and for example Siemens Healthineers (partly owned by Siemens AG) is visibly behind.

Ecosystem maturity is becoming a competitive differentiator. It is becoming a race that must be joined seriously.

The message that should stand out for ALL of them

“You don’t have an ecosystem strategy problem — you have an ecosystem architecture problem”
Until you solve that, every platform, partnership, and digital initiative will stall.”

“You’re already ecosystem-dependent.
You’ve already tried ecosystem initiatives.
You’ve already felt the pain of incoherence.
The only thing you haven’t done is architect the ecosystem itself.”

So lets look at each of these seven major companies

I am looking through the Intelligent Integated Business Ecosystem (IIBE) lens here

* Hitachi Energy

They are operating at the centre of one of the most complex systems on earth — grid modernisation, DER integration, and regulatory alignment. What I see across the sector is that the technical progress is strong, but the multi actor system around it isn’t keeping pace

How they talk now

• Mission / site: Energy transition, sustainable energy future, “advancing a sustainable energy future for all.”
• Innovation tone: Grid automation, digital, HVDC, “smarter, stronger, greener” grids.
• Ecosystem language: Strong implicit ecosystem: TSOs, DSOs, regulators, OEMs, renewables developers. Often framed as “collaboration,” “partnerships,” “co‑creation,” “integrated energy systems.”

The Issue

“Hitachi Energy is structurally dependent on grid and data ecosystems, has repeatedly reframed its digital platforms, and still treats ‘ecosystem’ as portfolio + partners rather than a designed architecture—exactly where IIBE provides the missing structural grammar.”

The need

Hitachi Energy is already building the infrastructure of the transition. The next step is making the ecosystem itself intelligent and coherent. This needs explicit architecture for multi-actor grid and data ecosystems

* ABB

ABB is in a unique position: Electrification, Motion, Robotics, and partners all contribute to customer outcomes, but the system they operate in is becoming more interconnected and more demanding.

How they talk now

• Mission / site: Electrification, automation, robotics, “transforming industries,” “more sustainable and resource‑efficient future.”
• Innovation tone: Digital solutions, ABB Ability, AI, automation, smart manufacturing.
• Ecosystem language: “Partner ecosystems,” “integrated solutions,” “end‑to‑end,” “across the value chain.”

The Issue

ABB’s future depends on orchestrating automation, electrification, and building ecosystems, yet ABB Ability and related initiatives show narrative resets instead of architectural clarity; IIBE makes their cross-domain ecosystem condition operable

The Need

Needs unifying ecosystem grammar across domains & partners

* Maersk

Maersk has made bold moves toward integrated logistics, and the ambition is clear: end‑to‑end visibility and orchestration across a global network of actors. What I see across logistics ecosystems is that the technology is ready, but the system architecture — the way partners, data, and decisions align — is the real bottleneck.

How they talk now

• Mission / site: “End‑to‑end logistics integrator,” “connecting and simplifying global supply chains.”
• Innovation tone: Digital platforms, visibility, integrated logistics, decarbonisation.
• Ecosystem language: Strong: “integrator,” “end‑to‑end,” “global network,” “partners,” “platforms.”

The Issue

“Maersk has already lived through a flagship ecosystem failure with TradeLens, proving that technology and bilateral partnerships are insufficient; IIBE gives them the architectural lens they were missing when they designed that ecosystem.”

The Need

Knows tech + partnerships aren’t enough; needs structural ecosystem design

* Johnson Controls

Smart buildings are no longer single‑vendor environments — they’re ecosystems of integrators, OEMs, platforms, and operators. The complexity is rising faster than the tools built to manage it.

How they talk now

• Mission / site: Smart, healthy, sustainable buildings.
• Innovation tone: OpenBlue, smart buildings, digital twins, sustainability, decarbonisation.
• Ecosystem language: “Partners,” “integrators,” “open platforms,” “building ecosystems.”

The Issue

Johnson Controls’ OpenBlue vision assumes an open smart-building ecosystem, but the underlying roles, flows, and governance remain implicit; IIBE turns that implicit ecosystem into an explicit, designable architecture.

The Need

Needs architecture for roles, flows, and governance in built-environment ecosystems

* DHL

Global logistics is becoming more interconnected, more digital, and more dependent on partners you don’t control. What I see across the sector is that visibility and optimisation work well inside the organisation, but break down across the wider system.

How they talk now

• Mission / site: “Excellence. Simply delivered.” Global logistics, connecting people and improving lives.
• Innovation tone: Digitalisation, data, AI, sustainability, e‑commerce, last‑mile, supply chain visibility.
• Ecosystem language: “Networks,” “partners,” “collaboration,” “end‑to‑end supply chain.”

The Issue

DHL’s logistics platforms and visibility solutions depend on a dense ecosystem of carriers, shippers, and data partners, yet their initiatives are framed as products and platforms, not as a coherent ecosystem architecture—precisely the gap IIBE fills

The Need

Needs ecosystem architecture beyond “platform + visibility”

* Allianz

Insurance is becoming deeply ecosystem‑driven — health, mobility, financial platforms, embedded services. The challenge isn’t the ambition; it’s the architecture behind risk, identity, and data across actors.

How they talk now

• Mission / site: Protecting futures, resilience, long‑term value.
• Innovation tone: Digital insurance, platforms, ecosystems (health, mobility, financial), data, AI, risk insights.
• Ecosystem language: Explicit: “ecosystems” in health, mobility, financial services; “platforms,” “partners,” “embedded insurance.”

The Issue

Allianz is betting on mobility, health, and embedded insurance ecosystems, but its pilots and platforms remain fragmented; IIBE offers the structural language to redesign these as one coherent ecosystem architecture instead of scattered experiments.

The Need

Needs structural grammar for embedded & cross-sector ecosystems

* Siemens Healthineers

Healthineers is pushing the frontier of diagnostics, AI, and digital health — but the clinical ecosystems these innovations depend on are fragmented and move at different speeds.

How they talk now

• Mission / site: “We pioneer breakthroughs in healthcare. For everyone. Everywhere.”
• Innovation tone: AI, digital health, precision medicine, integrated diagnostics, clinical decision support.
• Ecosystem language: “Care pathways,” “clinical networks,” “partners,” “integrated solutions,” “digital ecosystems” (sometimes explicit).

The Issue

Siemens Healthineers is increasingly ecosystem-dependent in data-driven care and AI, but its ecosystem posture lags behind Siemens AG’s Xcelerator framing; IIBE gives Healthineers the architectural catch-up path to align its ecosystem condition with the group’s ambition. The Health Ecosystem is one of the most important to be connected up.

The Need

Needs to catch up architecturally with Siemens AG’s ecosystem posture but create the distinctive ecosystems for the focus areas they are operating in.

They are all facing the Structural Rupture of how they operate today is starting to fail

Most companies don’t realise they’ve already crossed a line. They’re no longer operating in markets. They’re operating in ecosystems—whether they intended to or not.

And here’s the uncomfortable truth:

Their next decade of growth depends on actors they don’t own, don’t control, and can’t replace.

Energy transition.
Smart buildings.
Logistics visibility.
Embedded insurance.
Connected care.
Industrial automation.

Every strategic bet now relies on multi‑actor coordination.

Yet most organisations are still trying to scale these ambitions with tools built for a different world:

• bilateral partnerships
• product portfolios
• digital platforms
• integration programs
• “ecosystem” slides full of circles and arrows

These aren’t wrong but they are facing rapidly slower growth rates. They’re just not enough in today’s world.

Because the real blocker isn’t technology, or partners, or adoption. It is mostly within the companies themselves It’s the absence of something more fundamental:

An ecosystem architecture and they need to set about and build it – to fit their circumstances but they need to talk a different mission, innovation tone and build their ecosystem language.

Perhaps the IIBE is the missing piece, there is only way way to find out- ask!

• Ecosystems are now your operating environment.
• Architecture is the missing capability.
• IIBE is the only architecture built for multi‑actor value creation.
• Without it, you will continue to stall, consolidate, or retreat.
• With it, you can scale what your strategy already depends on.

This is the shift from “ecosystems are interesting” to “ecosystems are the only way forward.”

It is the time to take stock and each of these companies are caught in the same trap as countless others – there is a time to break out and follow those who are already ahead.

The post Business Ecosystems are more than your Companies thinks they are first appeared on Building Your Innovation & Ecosystem Intelligence.

The Architecture of Ecosystems — Do you recognize what it actually takes?

Many Business Ecosystems are not as well designed as they can be. Often, we are at the problem recognition level. Do we ever go beyond this to recognize the architectural specificity is missing and this is essential.

Do you have a real sense of what that architecture actually consists of or why its categorically different from everything you have tried before?

You now recognize the problem. The system is resisting you. The tools you built were designed for a different world. The structural layer never emerged.

But recognition is not enough.

The question every leader reaches at this point is the same: what would it actually mean to have an ecosystem architecture — and what does one consist of?

That question deserves a precise answer. Not a framework. Not a methodology. An architectural answer.

Ecosystem architecture has three requirements. Most organizations have none of them.

The first requirement is a structural design — an explicit blueprint of how actors, capabilities, and value creation roles relate across the system. Not a partner map. Not an org chart extended outward. A genuine structural design that shows how the system is supposed to move — where value is created, where it transfers, where it compounds, and where the current design is working against itself.

Without this, every initiative is being launched into a system that has no blueprint. Leaders are renovating a building no one has ever drawn plans for. They find walls they didn’t expect, loadbearing structures they didn’t know existed, and spaces that can’t be connected no matter how good the individual rooms are.

The second requirement is a shared ecosystem grammar — a common structural language that every actor in the system can work within. This is the requirement that surprises leaders most, because it explains something they have never been able to account for: why partners who are genuinely aligned at the relationship level still produce fragmented results at the system level.

Alignment at the relationship level is not the same as alignment at the structural level. Two organizations can share strategy documents, sign partnership agreements, attend the same governance meetings — and still be operating with fundamentally different definitions of value, capability, and contribution. They are speaking different structural dialects. They can interact. They cannot compose.

A shared ecosystem grammar gives every actor a common way of defining roles, capabilities, incentives, and value creation. It is not a contract. It is not a standard. It is the architectural language that makes composition possible — the difference between components that coexist and components that fuse.

The third requirement is a distributed intelligence layer — the capacity to sense, learn, and adapt across the whole system, not just within individual actors. Most organizations have invested heavily in data and AI capability. But that capability is concentrated inside the organization, or inside a single platform. It processes what that actor can see.

An intelligence layer built at the ecosystem level sees differently. It detects signals that no single actor can detect alone. It identifies where the system is misaligning before that misalignment becomes a visible failure. It learns from the distributed experience of every actor simultaneously — and converts that learning into coordinated movement across the system.

These three requirements – structural design, shared grammar, distributed intelligence – are what turn an ecosystem from a collection of actors into a system that can compound value. Any they are categorically from anything that strategies, operating models, digital platforms, or partner programs were built to provide.

What these three requirements actually give a leader

When structural design, shared grammar, and distributed intelligence are in place, something shifts in what a leader can actually do.

They can see the system as a whole. They can understand where value is created and where it is lost. They can identify structural friction before it compounds into failure. They can align capabilities across actors rather than within them. They can shape how intelligence flows across the system. They can design how the system learns. And they can create the conditions where progress compounds rather than fragments.

These are not improvements on what leaders currently have. They are capabilities that simply do not exist without explicit ecosystem architecture. The shift is from managing initiatives to designing the system those initiatives must live in.

This is why the investment paradox exists.

Look across the industrial landscape — you name them and recognize most are included – Every organization has invested substantially in ecosystem capability. IoT platforms. Digital Twins. Data architecture. Partner networks. Innovation portfolios. You name them and you can spot clear investment in their individual ways, be that, Siemens AG, ABB, Hitachi, Honeywell, GE Vernova, Schneider Electric, Johnson Controls, Maersk, DHL, Siemens Healthineers, who ever.

Siemens AG with their Xcelerator is the most architecturally advanced of the group. It has moved further than most toward a genuine platform ecosystem. And yet even Xcelerator has not produced the compounding value that Apple’s ecosystem generates, or the structural lock-in that Salesforce’s architecture sustains.

This is not a failure of investment. It is not a failure of ambition or execution. It is a structural diagnosis.

Apple and Salesforce are not successful because they built better products. They are successful because they built architectures — systems where every participant’s contribution makes every other participant’s contribution more valuable. The value does not live in any single component. It lives in the structural relationships between components. It compounds because the architecture was designed to compound it.

Every major industrial organization built the components. None of them built the architecture that makes the components fuse.

The IoT platform that didn’t become Salesforce didn’t fail because the technology was wrong. It failed because technology without ecosystem architecture is a component in search of a system. Excellent in isolation. Unable to compound.

Flow. Form. Fusion.

This is the progression that ecosystem architecture must move through. Not a sequence of projects. A structural development path — and understanding where an organization sits within it explains everything about why their ecosystem is performing the way it is.

Flow is the foundation. Data moves. Systems connect. Platforms integrate. Partners exchange. Most major organizations have achieved significant Flow — the connections exist, the signals travel, the data is gathered. But Flow without structural design is movement without direction. The system is active. It is not intelligent. It is producing information without producing coordinated action.

Form is the structural layer. This is where the blueprint is drawn — where actors are given defined roles, where capabilities are mapped against value creation potential, where incentives are aligned with system outcomes rather than individual outcomes, and where governance is built to serve the ecosystem rather than control it. Form is where structural design and shared grammar come into existence together. It is where the system stops being a network of relationships and starts being an architecture.

Most organizations have fragments of Form. Governance structures. Partner frameworks. Innovation programs. But Form built without ecosystem architecture logic solidifies the wrong things — creating bureaucracy where it should create alignment, locking in bilateral relationships where it should enable multi-actor composition.

Fusion is the destination. This is where individual capabilities stop coexisting and start compounding — where the IoT platform, the digital twin, the partner network, the AI capability, and the customer intelligence stop being parallel assets and become a single intelligent system generating value no single actor could produce alone.

Fusion is the Apple moment. The Salesforce moment. The point at which the architecture produces emergent value that was not present in any of the components individually, and that cannot be replicated by any competitor who hasn’t built the same architectural foundation.

Almost no industrial organization has reached true Fusion. Most are somewhere in Flow. Some have partial Form. The gap between where they are and where the architecture could take them is not a technology gap. It is not a strategy gap. It is an architectural gap.

What changes when the architecture is in place.

When an organization moves from ecosystem activity to ecosystem architecture — through Flow into Form toward Fusion — three things become structurally different, not just operationally better.

The system becomes legible. Leaders have a structural view of the ecosystem they are trying to change. The invisible constraint becomes visible. What can be seen can be addressed.

The system becomes composable. With shared grammar in place, capabilities that were parallel become additive. Initiatives that were isolated become integrated. Partners moving at different speeds begin to move within a shared structural logic. The system can be reconfigured as conditions change without losing the architectural coherence that makes it compound.

The system becomes defensible. An architecture that has reached Fusion generates structural moats that no individual product or platform can generate. The compounding intelligence, the shared grammar, the aligned incentives, the distributed capability — these become harder to replicate the longer the architecture operates. The advantage is not in any single asset. It is in the system itself.

This is what organizations leave on the table when they remain at the aspiration level. Not incremental performance improvement. Not faster execution. Structural advantage that compounds over time and becomes increasingly difficult for any competitor to replicate.

The question is no longer whether ecosystem architecture matters.

The question is whether you build it deliberately — or whether you continue accelerating inside a system that cannot absorb the acceleration, waiting for an architecture that will not emerge on its own.

The architecture exists.

Everything described here — the structural design, the shared grammar, the distributed intelligence layer, the progression through Flow into Form toward Fusion, the conditions for legibility, composability, and defensible advantage — has been built into a single coherent architecture.

The Intelligent Integrated Business Ecosystem (IIBE) is the first named architecture designed specifically for this reality. Not a methodology applied to ecosystems. Not a framework extended from single-actor logic. An architecture — built from the ground up for multi-actor systems where value is created between organizations, not inside them.

For organizations feeling the limits of the system around them, the IIBE makes those limits visible, nameable, and solvable.

This is the moment organizations stop fighting the system — and start architecting it.

The post The Architecture of Ecosystems — What It Actually Takes first appeared on Building Your Innovation & Ecosystem Intelligence.