Harmonising Complex IT Landscapes with Enterprise Architecture

Building Independence at Enterprise Scale

As part of one of the largest corporate carve-outs in German industrial history, a leading global enterprise had to separate from shared corporate IT services and establish full autonomy as a newly independent company, within a compressed regulatory and contractual timeframe.

The scale was considerable. More than 1,000 IT systems, built up over decades, supported critical business capabilities across the company’s core value streams. Many relied on shared services and complex dependencies that had to be disentangled within a limited timeframe. Contractual agreements and regulatory obligations imposed strict migration deadlines, while requirements around data separation, licensing and compliance left little room for delay.

Beyond separation, the company saw an opportunity. Rather than replicating existing structures, it aimed to modernise the landscape and lay a stronger foundation for growth. The underlying difficulty was coordination: technology decisions were made locally, with no shared principles, no common standards and no enterprise-wide view of what was being built or why.

Large-scale carve-outs are ultimate stress tests. Success depends on the ability to maintain architectural integrity and cross-functional alignment while navigating the constant ambiguity of a decoupled business.

Benjamin MalikPrincipal IT Architect

Speed Without Guardrails

Years of decentralised technology decisions had resulted in a fragmented landscape with limited governance and transparency. Responsibilities were not always clearly defined, architectural standards varied across domains and there was no consistent view of ongoing initiatives or technology choices. As the carve-out accelerated, this lack of coordination created growing complexity, duplication of effort and increasing delivery risk.

Different teams chose different stacks, integration patterns and cloud services for similar problems, creating redundancy and inconsistency. There was no enterprise-wide transparency into what was being built, which standards applied or how individual projects fit the broader target landscape. Multiple teams solved the same integration and infrastructure challenges independently, duplicating effort and budget, while point-to-point connections proliferated and made the landscape harder to maintain.

Because data separation deadlines and regulatory obligations were unforgiving, architectural missteps could become non-compliant. The landscape itself reflected decades of organic growth, with domains adopting different technologies and operating models. The challenge was therefore less about modernisation than about creating alignment across hundreds of stakeholders and many domains without becoming a bottleneck.

The hardest part was building trust that governance could actually help teams move faster.

Alexander RengersSenior IT Architect

Structure Without Slowdown

Success was defined by a set of practical outcomes. The organisation needed guiding principles and technology standards adopted across all transformation programmes, alongside review and decision processes that teams would genuinely use rather than work around. It needed reusable reference designs that accelerated delivery instead of constraining it, and full traceability of technology decisions for audit, compliance and future planning.

Four priorities shaped the work. The first was enablement over control, with governance designed to help projects succeed rather than to act as a gatekeeper. The second was standardisation with flexibility, offering common foundations where consistency mattered and autonomy where business context demanded it. The third favoured the practical over the theoretical, testing every standard and blueprint against real project needs before adoption. The fourth was sustainability, building an operating model the organisation could run independently long after the engagement ended. Together with the customer, mmkdigital designed an Enterprise Architecture practice around these priorities, calibrated to provide structure without unnecessary overhead.

Our goal was to build something teams would actually adopt, because it made their work easier.

Clemens MüssenerPrincipal IT Architect

Building and Operationalising an Enterprise Architecture Practice

mmkdigital worked inside the organisation, combining strategic governance design with hands-on delivery across three interconnected workstreams.

The first was governance design and rollout. mmkdigital defined guiding principles and technology standards tailored to the domain structure, established review boards with clear mandates and decision authority, and introduced Architecture Decision Records to capture rationale and ensure traceability. Lightweight relevance assessments let teams self-identify when governance checkpoints applied.

The second was reference designs and reusable blueprints. mmkdigital developed designs for recurring integration, data and infrastructure patterns, publishing them using arc42 and the C4 model so delivery teams could consume them directly, and maintaining them as a living resource updated through project feedback.

The third was embedded project delivery support. mmkdigital architects worked inside transformation projects as solution and domain architects, providing design reviews, technical coaching and hands-on problem-solving. This kept governance grounded in real delivery constraints and turned standards into living tools.

Enterprise Architecture as the Foundation for Growth

Over three years, the practice matured from an initial framework into a self-sustaining function embedded across the organisation.

Decision-making became consistent at scale, as guiding principles and technology standards became the default reference point for teams across all domains. Delivery grew faster and more predictable, because reusable blueprints reduced solution design time and eliminated repeated debates over foundational technology choices. Every significant technology decision was documented and linked to the broader strategy, supporting internal alignment and external audit requirements alike.

The shift from reactive oversight to embedded partnership allows us to build in quality from the start and eliminate the friction of late-stage corrections.

Marc KleinPrincipal IT Architect

Adoption happened without enforcement, as review boards and checkpoints were used voluntarily by the majority of teams because they demonstrably improved outcomes. By 2025, the practice was staffed and operated by the customer’s own people, with mmkdigital transitioning from delivery to advisory. Most importantly, the organisation achieved alignment across a highly heterogeneous landscape without sacrificing the autonomy and speed its teams needed. Governance became a delivery accelerator rather than overhead.

Conclusion

Enterprise Architecture is often reduced to governance, documentation and compliance. At this company, it did far more: it became the central link between the company’s transformation ambitions and the hundreds of delivery decisions required to realise them. As a newly independent DAX company separating from its former parent under hard regulatory and contractual deadlines, our customer needed to make coherent technology decisions across a fragmented, fast-moving landscape of more than 1,000 systems. The answer was an operating model that connected strategy, governance and delivery into a single, practical discipline.

The combination of governance at the enterprise level, blueprints at the domain level and architects on the ground proved decisive. Standards were shaped by and tested in actual delivery, never theoretical documents on a shelf. By embedding governance into the organisation’s transformation programmes rather than placing it above them, mmkdigital helped create a practice that teams trusted and used. The result was a more consistent IT landscape, faster delivery, traceable decisions and a governance function the organisation now owns and continues to evolve.

The engagement reflects a principle mmkdigital applies across its work: effective Enterprise Architecture is an organisational discipline that enables transformation, supports sound decision-making and helps enterprises evolve complex technology landscapes sustainably.

Your challenge,our passion.

Tell us where you are starting from and where you want to go. Together, we design a suitable solution and deliver it.