EAM for Digital Transformation in Small and Medium-Sized Businesses

Maturity model, KPIs, consolidation of heterogeneous IT landscapes and agile EAM - how enterprise architecture management is carrying SMEs through the ongoing task of transformation. From 1,200+ projects in the DACH region.

AM series - Part 2
Part 1 is dedicated to ERP selection based on architecture → EAM and ERP selection in SMEs. This article takes a broader look at continuous transformation - and at what happens between selection decisions.

The most important answer in 60 seconds

Digital transformation is not an initiative - it is an ongoing task. EAM is the management tool.

Medium-sized companies rarely fail in their digital transformation because of strategy and almost never because of courage. They fail because of the invisible layer between strategy and operational implementation - the architecture. Without it, ERP implementation, cloud migration, AI pilot and platform development run parallel and uncoordinated into one another.

At Dreher Consulting, we anchor EAM as a pragmatic control mechanism for the ongoing task of transformation - not as a corporate bureaucracy. Coupled with the Business Model Canvas and our AI-supported SCOReX® model, we create an architecture that grows with the organization instead of slowing it down. 33+ years of consulting experience, 1,200+ projects, 100% vendor-independent.

Three fallacies about digital transformation that will slow down SMEs in 2026

In workshops with managing directors, we always hear the same three sentences. They sound plausible - and yet they cost millions every year.

Fallacy 1: "We're doing digitalization projects. Architecture will come later."

Exactly the opposite. Anyone who launches parallel digitalization initiatives without an architectural logic - new CRM, AI pilot, cloud migration, portal - will produce exactly what we found at the kitchen manufacturer within 18 months at the latest: 15 systems, four data truths, no owner. Architecture is the lever that decides whether initiatives become a portfolio or a patchwork quilt. From our experience: an architecture decision costs days, an architecture decision that is not made costs years.

Fallacy 2: "Digital transformation has a beginning and an end."

It doesn't - and that is the most unpleasant truth. Business models are shifting, cloud providers are consolidating, AI tools are replacing their predecessors every 18 months, regulatory requirements such as NIS-2 and the EU AI Act are coming into force in stages. Anyone planning transformation as a project with an end date is planning for the obsolescence of their architecture. EAM understands transformation as a continuous management process - with a maturity level, roadmap and governance.

Fallacy 3: "AI tools will control our architecture themselves in future."

We rely heavily on AI ourselves - SCOReX® analyses patterns from 1,200+ projects, identifies redundancies and prioritizes initiatives. But: AI recognizes patterns, it has no responsibility. An architectural decision with double-digit leverage belongs in hands that are accountable, that ask questions, that disagree. This is precisely why AI complements our experienced consultants - it does not replace them.

The four maturity levels of architecture development - where do you actually stand?

Most SMEs systematically overestimate their level of maturity. In our experience, managing directors usually place their company one level higher than the architecture audit shows at the end. This gap is not embarrassing - it is the most valuable insight of the first two weeks of consulting.

Our classification: Over 70% of the medium-sized companies we start with are at level 1 or 2. This is not a failure - it is normality. The decisive factor is not where you are today, but that the next level is consciously approached in the next 12 months, rather than arising by chance.

EAM in practice: How architecture orchestrates specific digitalization initiatives

The most frequently asked question in our initial meeting is: "What does EAM actually do in an ongoing project?" The most honest answer: EAM ensures that parallel initiatives do not run against each other. It sets priorities, recognizes dependencies and prevents redundancies before they burn into the budget.

The logic behind this is always the same: which system bears the truth, which consumes it and who has the mandate to change it? If you can't answer that, you automate chaos.

Heterogeneous IT landscapes: From architectural debt to consolidation

Practically every medium-sized company we work with has a historically evolved IT landscape. Legacy systems from the 1990s run alongside cloud services from 2024. Isolated solutions were introduced because they helped quickly - and have never been dismantled. This is precisely where EAM acts as an orchestrator, not a bureaucrat.

What EAM actually does in heterogeneous landscapes

We regularly see three effects in the first nine months:

• A common language between business and IT. Capabilities and data objects are described in terms that are understood by both Sales and Development. Workshops are measurably shorter.
• A business-IT alignment roadmap as an artifact. Not a PowerPoint vision, but a well-maintained document anchored in the steering committee that draws every new initiative to the plan - or deliberately rejects it.
• Systematic reduction of technical debt. Redundancies become visible, interface risks are prioritized, legacy replacement planning is linked to business priorities.

Architecture Capability Building - how we empower your organization

We don't come to document architecture for you and leave again. Responsibility for architecture must remain within the company - otherwise all documentation becomes obsolete within the first six months after the end of the project. From over 100 SME projects and more than 20 years of experience, we have developed a method toolkit that we adapt to your context - not a standard off-the-shelf method. It works in three stages:

Our classification: Architecture that is not supported by your own organization becomes the most expensive shelf product for IT management. EAM success is not measured by the model, but by the question of whether the specialist departments use it voluntarily.

EAM in agile settings: architecture owner instead of ivory tower

One of the most persistent prejudices about EAM is: "Architecture is rigid and doesn't suit agile teams." The opposite is true - if EAM is thought of as modular. In our projects, we anchor three concepts that do not slow down agile teams, but relieve them.

Architecture owner per value stream

Each critical value stream - sales, production, after-sales - is assigned an architectural contact person. They are part of the agile delivery organization, not outside it. Decisions are made where they are implemented, not in a decoupled architecture board.

Architecture sprints

Instead of six-month target architecture workshops, we work in two- to four-week sprints, each of which closes a specific architecture problem - an interface, a capability clarification, a migration path. The architecture is created incrementally, with the business, not in front of it.

Modular target architecture

The target architecture is not written as a 200-page document, but as a set of linked modules. Each building block can be updated individually without turning the overall model upside down. This is the only form in which architecture survives a 24-month transformation program.

From our experience: medium-sized teams with 30 to 80 developers achieve a measurably higher delivery speed after three to four architecture sprints - because fewer rework is required, fewer interfaces collide and fewer escalations move to C-level.

The KPIs that really count - how to measure EAM success

EAM without measurement is faith. EAM with the wrong KPIs is reporting theater. In our projects, we rely on a lean KPI logic that appeals to management and IT management alike.

Our classification: If you want to optimize all six KPIs at the same time, you won't optimize any of them. We recommend: two leading KPIs for the first twelve months, the rest as a follow-up.

Why Dreher Consulting - and not the next AI tool or the next major consultancy

Three things specifically distinguish us from both alternatives.

Next step: 30 minutes directly with Dr. Dreher

In a 30-minute initial meeting, we clarify with you what maturity level your company is actually at - and which levers will make the biggest difference in the next 12 months. You leave the meeting with an honest maturity assessment and specific recommendations for action, not a sales pitch.

Frequently asked questions about EAM in the digital transformation

What measurable benefits does EAM bring to a medium-sized company?

In our projects, typically: 20 to 35% cost savings through consolidation of redundant systems, 30 to 40% faster implementation of new digitalization initiatives, significant reduction in technical debt. The first benefits - transparency and quick wins - are usually achieved within six to twelve weeks.

How does Dreher Consulting deal with historically grown, heterogeneous IT landscapes?

We start with a lean as-is analysis - not a six-month documentation orgy. In two to four weeks, an architecture map is created that makes quick wins visible and at the same time lays the foundation for a target architecture. We use ArchiMate, lean architecture approaches and AI-supported analyses via SCOReX®.

Isn't EAM really only for large corporations?

No - and that is precisely the most common misconception. Corporate EAM with hundreds of pages of modeling is not suitable for SMEs. SME EAM fits onto a few pages and delivers the first reliable results in five to ten man-days.

How long does a typical EAM implementation in SMEs take?

Initial results - architecture map, capabilities list, identified quick wins - are produced in six to twelve weeks. A complete maturity level development from level 1 to level 3 typically takes twelve to 24 months, depending on size and complexity.

What role does AI play in modern EAM - and where are the humans?

AI supports automated interface analysis, the detection of redundancies and the creation of migration roadmaps. At Dreher Consulting, AI recommendations are documented in a comprehensible manner, categorized by experienced consultants and never passed on to management as a black box.

How do you measure the success of an EAM project in concrete terms?

Using clear KPIs: reduction of technical debt, time-to-initiative, architecture conformity of new projects, redundancy rate in the system landscape, business-IT alignment score and project duration reduction. Recommendation: two leading KPIs in the first twelve months, the rest as a follow-up.

What is the difference between this approach and traditional large-scale consulting?

We deliver the minimum that enables your management to make architecture decisions with confidence. You speak directly with Dr. Dreher, not with a junior sub-team. And our recommendations are vendor-independent - no commission, no partner level, no hidden implementation margin.

Dr. Harald Dreher Managing Director, Dreher Consulting · 33+ years of consulting experience in the DACH midmarket · 1,200+ successfully supported EAM, ERP and digitalization projects · 100% vendor-independent · Directly available for management and supervisory board in the first meeting. Book an appointment directly with Dr. Dreher →