Introducing EAM and TOGAF successfully, step by step

Introduction

Enterprise Architecture Management (EAM) is a strategic instrument that helps to align corporate IT with business processes and corporate goals. TOGAF (The Open Group Architecture Framework) is one of the best-known and most widely used frameworks for implementing EAM.

In small and medium-sized enterprises (SMEs) in particular, getting started often looks like a huge mountain to climb. But with a smart approach, clear goals and a structured introduction plan, EAM is feasible and valuable for SMEs too. This article shows how you can introduce EAM and TOGAF step by step – pragmatically, with a clear focus and close to the business.

Step 1: Clarify the target vision and the benefits

Before you get started, ask yourself:

• What should EAM improve?
• What transparency is lacking today?
• Which decisions are cumbersome or not based on facts?

Example: "We want to know which IT systems support which business processes and how changes in IT affect the business."

A clear target vision helps you to stay focused and to convince stakeholders.

Step 2: Identify and involve stakeholders

EAM affects many areas: IT, business departments, management. Identify your key people and stakeholders early on, e.g.:

• Head of IT
• Process owners
• Executive management

Communicate the benefits, take concerns seriously and create participation instead of issuing directives.

Step 3: Small steps instead of a big bang

EAM is not a project that you can "finish". It is a long-term management approach. Start, for example, with:

• one business domain (e.g. purchasing or sales)
• one architecture layer (e.g. applications)
• one specific question (e.g. "Which systems use Excel as an interface?")

Step 4: Choose suitable tools and models

Opt for simple, scalable tools. TOGAF provides the methodology, but not the tool. Suitable for getting started:

• Archi (free of charge)
• leanIX, ADOIT (cloud-based commercial solutions)
• Excel-based templates (for initial modelling)

Define a metamodel: Which object types do you need? (Processes, systems, data, interfaces, etc.)

Step 5: Apply the ADM cycle in practice

The TOGAF Architecture Development Method (ADM) consists of 10 phases. The important thing is not to do everything at once – use the cycle in a modular way. Example:

• Phase A (Architecture Vision): develop the target vision with stakeholders
• Phase B (Business Architecture): capture processes
• Phase C/D (Information/Technology Architecture): document systems and technologies

Step 6: Establish architecture governance

No rules, no benefit. Define:

• Who changes architecture models?
• How are decisions made?
• Which roles are there (e.g. EAM lead, business modellers)?

Start with lightweight but binding rules.

Step 7: Make the benefits visible

EAM works in the background. Point out successes in concrete terms:

• "We have identified and consolidated duplicate systems."
• "A planned technology change could be prepared better."
• "IT investments are now traceably linked to the business goal."

Visualise your architecture with simple, easy-to-understand diagrams. Use colours, layers and relationships.

Conclusion

EAM with TOGAF is not a tool reserved for large corporations, but a structured compass for enterprise architecture. SMEs in particular benefit from the resulting transparency, clarity and ability to make decisions. Those who start pragmatically, involve stakeholders and proceed step by step can establish EAM successfully – without overburdening day-to-day operations.