Skip to content

Anonymised · Enterprise transformation

Everybody owned the outcome. Nobody owned the boundary.

Every team optimised its own platform successfully — yet customer issues kept appearing at the seams between them. The architecture looked coherent on slides; the ownership model between the boxes did not exist.

An anonymised account of a real engagement: a large enterprise transformation involving multiple platforms, vendors, product teams and system owners operating across a shared customer journey.

The real problem

Everyone was accountable for delivering the customer experience. Nobody was accountable for the seams between systems. Each team optimised its own platform successfully — CRM, commerce, identity, registration, ERP, payments — yet customer issues consistently appeared at the boundaries. The architecture looked coherent on slides. The ownership model did not exist between the boxes.

What we did

Rather than modelling systems, we modelled decisions, events and ownership transitions. We focused on lifecycle ownership, event contracts, system-of-record boundaries and escalation paths. The architecture discussions moved away from integration technology and toward accountability.

The outcome

The organisation gained a shared understanding of where ownership started and stopped. Several recurring integration debates disappeared because teams now understood not only what they owned but also what they explicitly did not own.

What we’d do differently

We would map ownership boundaries before platform selection. Technology decisions were repeatedly revisited because ownership decisions had never been made.

What this proves

Most enterprise failures happen between systems, not inside them. The seam is often more important than the platform.