I work with complex systems moving into their next stage, when added complexity starts costing them in coordination, governance and funding. I turn that complexity into a transversal system capability, so the whole becomes easier to operate, govern, compare and fund as it evolves.

The core question is simple: How does a distributed system change form without losing its ability to operate as one?

I design the Operating Architecture that makes the recurring logic between programme, governance and funding explicit and reusable across actors, partners and geographies.

Whether programme, governance and funding structures are already mature, still emerging or evolving unevenly, complexity creates drift when the interfaces between them do not evolve at the same pace as the system.

I step in at those interfaces, where programmes, decisions, actors and funding must connect across organisational boundaries, to prevent or resolve the recurring coordination, governance and funding friction that makes the system harder to operate and its collective value harder to compare and fund.

<aside>

SYSTEM IN TRANSITION next stage creates complexity ↓

INSTITUTIONAL COST coordination + governance + funding friction ↓

WHAT YOU BUY transversal system capability ↓

HOW I BUILD IT Operating Architecture across programme + governance + funding ↓

WHAT CHANGES less reconstruction + more cumulative capability ↓

BUSINESS / INSTITUTIONAL VALUE easier to operate + govern + compare + fund

</aside>

For funders, operators and multi-actor platforms coordinating portfolios, programmes, partners and geographies

The challenge is no longer growth. It is preserving coherence as systems decentralise, adapt and scale.

Systems can continue delivering successfully while gradually losing coherence as complexity, variation and coordination increase. They become harder to operate, compare, govern and fund, while requiring more coordination to produce less visible collective value across contexts.

When architecture no longer absorbs the complexity, people compensate. Eventually, compensation becomes part of the operating model.

That is where I work.

<aside>

💡 Why strong systems still drift

Think of it like a body

A system can have a strong programme architecture, clear governance and sophisticated funding mechanisms, and still fail to operate as one.

Like a body, it does not hold because every part works well independently, but because the parts remain connected:

programme defines the system’s core operating logic
governance connects decisions across distributed actors
funding connects capital to the system as a whole

As complexity grows, those connections come under pressure.

The programme still runs. Governance still functions. Funding still exists.

But more human effort is required to keep them aligned.

That is where the hidden cost appears: coordination grows, decisions slow, local realities drift apart and collective value becomes harder to explain, compare and fund.

The issue is not necessarily the capabilities themselves. It sits in the interfaces between them.

What the system must preserve → programme invariants, cross-system decision principles, system-level funding logic

Where variation can remain unconstrained → local delivery, partner configurations, funding instruments and contextual choices

Operating Architecture makes that distinction explicit and turns the critical interfaces into reusable operating logic.

Variation is not the problem. Undefined invariants are.

The aim is not to add more structure. It is to transfer the burden of coherence from people to architecture so capability can accumulate without coordination growing at the same rate.

The architectural gap can appear at different levels of system maturity:

Emerging structures → some core operating structures are still implicit.

Established structures → programme, governance and funding exist, but their interfaces may need to become explicit.

Highly mature structures → those interfaces may already be sophisticated, while recurring operating logic across multiple configurations still needs to become reusable system capability.

The level changes. The architectural question remains the same: what must become explicit for the whole to continue operating as one?

</aside>

<aside>

The Pain Check

Is your system still coherent across its organisational boundaries?

You may recognise these patterns:

Funding Pressure → capital becomes fragmented or harder to mobilise and deploy strategically
Coordination Tax → growing human effort is required to keep the system aligned
Impact Readability → collective value becomes harder to aggregate, compare and defend
Distributed Governance → decision rights, accountability and ownership become less clear across actors
Replication Drift → local adaptation progressively creates divergent versions of the model
Capability Accumulation → each new programme, partner or geography rebuilds coordination, decision and funding logic instead of inheriting reusable operating capability

The verdict: The system may still deliver, but increasing effort is being absorbed by coordination, reconciliation and explanation rather than additional impact.

The hidden cost is that an increasing share of institutional capacity is consumed by keeping the system together instead of extending its impact.

You are scaling complexity faster than structural capacity.

At that point, the issue is no longer execution. The architectural question is whether distributed programmes, decisions and funding can continue operating as one coherent system as its form changes.

</aside>

<aside>

When Operating Architecture becomes critical

These are the moments when structural complexity usually starts compounding across programme, governance and funding, and when Operating Architecture becomes increasingly valuable.

I typically step in during five structural transitions:

From pilot / one configuration to scale / multiple configurations — replication and growth begin creating structural variation across programmes, partners or geographies.
From one organisation to a multi-actor system or ecosystem — value is increasingly created across partners, networks, coalitions or platforms rather than by one organisation alone.
From organisation-bound operation to a distributed system — programmes, decisions, delivery and accountability increasingly cross organisational, partner and geographic boundaries.
From one funding model to plural or hybrid capital — grants, philanthropy, public funding, commercial revenue or blended finance must support the same wider system without fragmenting it.
From project-supported delivery to durable operating capability — what was previously carried through a programme, grant or project must become transferable, governable and sustainable beyond the original funding or implementation cycle.

These are the moments when "we can still manage" starts becoming "this is becoming hard to hold."

</aside>

<aside>

Why this is becoming critical now

Systems are being asked to hold more complexity with less tolerance for the coordination that used to absorb it.

Funding is becoming more selective. Delivery is more distributed. Partnerships and reporting requirements are multiplying. At the same time, funders expect clearer governance, comparative advantage and system-level value.

The result is a structural squeeze:

complexity grows faster than the human coordination available to hold it.

That is why coherence is becoming a funding, governance and operating issue, not simply a management one.

</aside>

<aside>

What changes after an architecture intervention

Capital efficiency: less operational capacity absorbed by coordination, reporting and repeated alignment.
Decision clarity: explicit rights, accountabilities and escalation paths across distributed actors.
Comparable impact: a shared logic through which results can be aggregated and defended without erasing local variation.
System fundability: a coherent system-level proposition that funders can understand, compare and support as a whole.
Cumulative capability: new partners, programmes and geographies can build on existing operating logic instead of rebuilding it.
Institutional reliability: the system depends less on individual memory and more on transferable operating capability. </aside>

<aside> WHAT I ACTUALLY DO

I work at the critical interfaces that must continue functioning as one system across actors, contexts and organisational boundaries.

I make explicit:

what the system must preserve for coherence
where variation can remain local or unconstrained
which recurring interfaces need shared operating logic
what should become reusable so each new configuration inherits more and rebuilds less

I then turn that logic into clear rules, shared reference points and operating assets that teams can use without depending on constant coordination or on the architect.

One Operating Architecture. Multiple realities.

</aside>

<aside>

</aside>

How I work

I work through one architectural method: