Articles

Reimagine Architecture

Why traditional architecture can look complete while people still have to make the enterprise work, and what Interweaving helps architects see.

Imagine a manufacturer discovering that a component installed in products across several markets may have a safety defect.

The traditional architecture looks prepared.

Applications are connected. Product and supplier data have owners. Processes cover quality, regulatory reporting, field service, customer communication, and recalls. Responsibilities are documented. The architecture repository is current.

Then the recall begins.

Engineering identifies the affected design, but the supplier changed its batch numbering eighteen months earlier. Quality can match the old and new identifiers because an experienced colleague remembers a transition spreadsheet. Field service has an approved replacement procedure, but one region uses an alternative because the specified tooling is unavailable. Product configuration and service history describe installed variants differently.

The recall still works.

It works because people translate, check, remember, and repair.

They know which records can be trusted. They recognise which procedure is actually usable. They know who can resolve a conflict. They explain what a record means before someone in another team acts on it.

One of those people is about to retire. The proposed automation assumes the records are sufficient to identify affected products. Someone would flag an uncertain case for another check. The automated rule could instead classify the product as unaffected.

In this hypothetical recall, the enterprise looks orderly on paper. In practice, people are compensating for gaps that its traditional architecture does not show.

What happens when the people doing that work are no longer there?

The recall exposes a limitation in what traditional architecture recognises. The task appears ready for automation because someone has been making the records usable. Her success conceals the work that the proposed change would remove.

Reimagine Architecture

Integration connects. Participation holds.

A supporting article establishing situated participation as the agent-side condition through which enterprise coherence is produced and sustained.

The order moves.
The promise travels.
The supplier is notified.
The machine produces an event.
The document is available.
The rule is enforced.
The obligation is recorded.
The customer situation is visible.
The manager sees status.

And still, the enterprise action may not hold together.

The connected enterprise still depends on agents who can understand what is happening, coordinate across boundaries, honour obligations, repair mismatches, and adapt when reality moves.

Integration connects parts of enterprise reality. It does not, by itself, make those parts hold together.

Coherence is not imposed by architecture. It is not delivered by integration. It is produced through situated participation.

Reimagine Architecture

Integrated systems can still produce incoherent enterprise action.

A supporting article that separates technical, data, and process integration from enterprise coherence.

The order moves from sales to production. The delivery is visible to logistics. The invoice is triggered. The customer record is shared. The supplier has been notified. The service team sees the case. The manager sees the dashboard. The policy can be retrieved.

The system connections work.

And still, the enterprise action does not hold together.

Sales believes the customer has been promised one thing. Production understands the product variant differently. Logistics works from another delivery assumption. Billing follows the contract structure. Service interprets the situation through open cases and commitments. Legal sees obligations. Risk sees exposure. Management sees status.

Everything is connected.

But the enterprise is not coherent.

Reimagine Architecture

The enterprise does not need one more complete picture of itself. It needs to hold together without one.

Why enterprise coherence does not require one shared representation, one central knower, or leadership to author it

A new white paper from the Business Architecture community, Cohesion by Design: From Fragmentation to Flow by Roger Burlton and Whynde Kuehn, names something real. Enterprises are fragmented. Functions optimise locally, and the customer experiences the seams between them. Strategy does not reach execution while it still matters. Bureaucracy taxes everyone, and the authors put a figure on it that is hard to ignore. They are also right about the part most architecture writing still gets wrong: AI will not rescue a fragmented enterprise. It will amplify whatever is already there.

This is worth saying plainly, because it means the wider architecture community is now describing the same condition this series has been working on. The diagnosis is shared. The disagreement that matters is about the cure.