Back to Insights
EAM Frameworks for Small and Medium-Sized Businesses: TOGAF & ArchiMate
TOGAF, Zachman, ArchiMate 4.0, BIZBOK, SAFe, COBIT - which frameworks really work in DACH SMEs, which ones combine, and which ones are deliberately left out.
/Herr_Dreher_500x500.jpg)
TOGAF, Zachman, ArchiMate 4.0, BIZBOK, SAFe, COBIT - which frameworks really work in DACH SMEs, which ones combine, and which ones are deliberately left out. From 1,200+ projects.
AM series - Part 3
Part 1: ERP selection based on architecture - Part 2: EAM in the digital transformation. This article is dedicated to the framework question - which building blocks work and when, and which are deliberately omitted in SMEs.
The most important answer in 60 seconds
Frameworks are a toolbox, not a religion. In the SME sector, it's the combination that counts.
Not a single framework - neither TOGAF 10, ArchiMate 4.0 (April 2026), Zachman, BIZBOK v15, SAFe 6.0, COBIT 2019 nor IT4IT - was written primarily for SMEs. The right answer is therefore almost always a lean combination: ArchiMate for visualization, selected TOGAF modules (ADM cycle, capability model), BIZBOK for the business view if required.
At Dreher Consulting, we see frameworks as a guide, not a dogma - combined with many years of experience in the SME sector and supplemented by AI-supported analyses. 33+ years of consulting, 1,200+ projects, 100% vendor-independent. You speak directly with Dr. Dreher, not with a junior consultant in a third sub-team.
What an architecture framework really does - and doesn't do
An architecture framework is not a result. It is a language, a structure and an approach that makes the complexity of modern enterprise architectures manageable. Complexity is growing - business models are shifting, the cloud, AI and platforms are driving heterogeneous landscapes, and regulations such as the EU AI Act and NIS-2 require verification obligations. Frameworks provide a framework for this complexity.
Specifically, frameworks do four things:
- They structure and document architecture elements - capabilities, data objects, applications, technologies - in a consistent notation.
- They create a common language between business departments and IT so that sales and development talk about the same thing when they say "capability" or "service".
- They provide a process for analysis, planning and transformation - typically an iterative cycle that leads from business strategy to implementation.
- They embed best practices and standards from thousands of projects worldwide - and protect you from having to reinvent every architecture problem from scratch.
What frameworks do not do: they do not make decisions. They do not replace management, negotiations with providers or political clarification between departments. Anyone who introduces a framework as an end in itself has overlooked the most important insight from 30 years of architecture practice: In our experience, the key figure that really counts is not the completeness of the models, but the response time to an architectural question from the steering committee.
The three classics in profile: TOGAF - Zachman - ArchiMate
Anyone who wants to have a say in architectural circles knows these three names. We have used them in hundreds of medium-sized projects - and just as often deliberately not used them. An honest profile per framework, without folklore.
Our rating: TOGAF without ArchiMate feels like an architect without a pencil. ArchiMate without TOGAF (or an equivalent approach) feels like a pencil without an architect. Only the combination delivers reliably in the SME sector.
The comparison matrix: Where which framework really delivers
For a quick overview - based on the criteria that actually count in SMEs, not academic completeness.
Source: Dreher Consulting analysis based on Open Group documentation, Zachman International, Forrester EAM Suites Landscape (Q4 2025) and 1,200+ practical projects - as of May 2026.
Behind the classics: BIZBOK v15, SAFe 6.0, COBIT 2019, IT4IT
The three classics do not cover everything. Four frameworks complement them in specific areas - and are often more valuable for SMEs than an orthodox TOGAF roll-out.
BIZBOK v15 - Business Architecture Body of Knowledge
Published by the Business Architecture Guild in April 2026 in its 15th edition. BIZBOK is on the business side and delivers exactly what TOGAF often leaves too abstract on the business side: a concrete capability map approach, stakeholder models, value stream logic. In the SME sector, we use BIZBOK specifically where the architecture has to dock directly onto the business model - for example, in the transition from strategy to investment planning.
SAFe 6.0 - Scaled Agile Framework
SAFe 6.0 (last updated September 2025, including AI-Empowered Agility additions) is not a classic EAM framework, but a scaling model for agile delivery. Relevant in SMEs as soon as several agile teams need architectural coordination. SAFe provides the "Architecture Runway" and "System Architect" concepts - both of which fit very well with the modular, sprint-capable architecture that we recommend at Dreher Consulting.
COBIT 2019 - IT Governance
From ISACA, still current in the 2019 edition, with 40 governance and management objectives. COBIT is rarely a stand-alone project for SMEs - but it is relevant wherever compliance and audit requirements (NIS-2, GDPR, industry-specific regulation) need to be embedded in the architecture.
IT4IT - Open Group Reference Architecture
A reference architecture specifically for IT value creation itself. IT4IT is useful when the IT organization is thought of as a business in its own right (strategy-to-portfolio, requirement-to-deploy, request-to-fulfill, detect-to-correct). We use IT4IT selectively in SMEs - especially in IT service management discussions.
From our experience: you don't need any of these frameworks in their entirety. You need exactly the building blocks that fit your current question - and the discipline to consciously leave out the rest.
30 minutes of clarity on the framework question - directly with Dr. Dreher
Which building blocks will give your company the greatest leverage today? Not a sales pitch.
The pragmatic SME stack: how we actually combine frameworks
Instead of a monolithic choice of framework, we recommend a stack - four layers that complement each other without duplicating work. This is what it looks like in our SME projects.
Layer 1
Business model & capabilities - BIZBOK v15 capability map + business model canvas. One page. Approved by the board.
Layer 2
Procedure & iteration - TOGAF-ADM cycle, lean tailored. Architecture sprints of 2-4 weeks each instead of a 6-month waterfall.
Layer 3
Visualization - ArchiMate 4.0 as standard notation. Tools such as Sparx EA, Archi, BiZZdesign. Modular, not monolithic.
Layer 4
Governance & Compliance - Selected COBIT targets for audit suitability, IT4IT references for IT service topics, SAFe modules for several agile teams.
Important: this stack is not "introduced" like a corporate program. It is created incrementally, starting with the layer that solves the current problem. In a medium-sized industrial project with around 2,000 employees, we have seen that the combination of ArchiMate visualization and ADM-oriented iteration was sufficient to reduce 40% of redundant interfaces in nine months - without any formal TOGAF roll-out. The benchmark is the problem solved, not the training completed.
Three practical recipes: Which combination solves which problem
The quickest way to choose the right framework is not a textbook - it is a concrete use case. Three patterns that regularly crop up in SME projects.
Recipe 1
Make a heterogeneous IT landscape visible - and consolidate it
Over the years, you have accumulated isolated solutions and parallel cloud and on-premise systems. No one can tell where the data truth lies. You want transparency first, then consolidation.
Recommended combination: ArchiMate 4.0 for rapid as-is visualization - TOGAF capability model for duplicate detection - ADM phase B/C for the step-by-step target architecture. Tool: Archi (open source) or Sparx EA.
Recipe 2
Translate business strategy into architecture
The management has adopted a new strategy - new markets, new service business, new platform. You need a clear path from strategy to capability roadmap.
Recommended combination: Business Model Canvas as strategy anchor - BIZBOK v15 capability map for business translation - ArchiMate 4.0 for visualization of target capabilities - TOGAF-ADM Phase A for strategy connection.
Recipe 3
Anchoring compliance and auditability in the architecture
NIS-2, EU AI Act, industry-specific audits (ISO 27001, MDR, GMP) - you want your architecture to support the verification obligations from day one, not retrospectively.
Recommended combination: Selected COBIT 2019 objectives as a governance layer - ArchiMate 4.0 for audit-capable modeling - IT4IT references for IT service architecture - TOGAF ADM Phase G (Implementation Governance).
Six anti-patterns for framework implementation in SMEs
Frameworks rarely fail because of their content. They fail because of the implementation. From 1,200+ projects, we have distilled six patterns that regularly lead to frictional losses in SME projects - and which are all avoidable with a little discipline.
1
The orthodox TOGAF complete start. Anyone starting out with a full TOGAF implementation in the SME sector has a lot of models, many training vouchers and few decisions to make in the first six months. Frameworks only work when they solve a specific problem - not when they are fully documented.
2
Modeling without an addressee. We see architecture teams drawing elaborate ArchiMate diagrams that nobody opens afterwards. Every model needs a concrete question that it answers and a person who needs this answer. Otherwise it's a piece of art.
3
The "architect in the ivory tower". Architecture that is created separately from the delivery organization is not accepted. Architecture owners belong in the value streams, not in a detached architecture staff. This applies regardless of whether you work in SAFe, classic or hybrid.
4
Tool before method. Procuring an expensive EAM suite before it is clear which questions it should answer is a very direct way of burning money. In our experience, Archi (open source) or Sparx EA are often sufficient for the first nine months - the suite question only arises when the maintenance effort becomes noticeable.
5
The attempt to standardize everything. A frequent reflex after the first models: now please use the same notation, the same procedure, the same templates everywhere. This is almost always counterproductive in SMEs. Standardize precisely the interfaces between value streams - within the value streams, teams can remain independent.
6
Frameworks as an argument against change. The most damaging pattern: a framework becomes a protective shield ("TOGAF says it can't be done that way") instead of a tool. A good framework accepts that reality will change it. We formulate this clearly in every project: if the framework and reality contradict each other, reality is right.
Why Dreher Consulting
Three things make us different when it comes to frameworks.
Firstly
Method toolkit instead of standard method
From over 100 SME projects and more than 20 years of experience with frameworks, tools and tailoring strategies, we have developed a method toolkit that we adapt to your context - not a standard off-the-shelf method.
Secondly
33+ years of experience, 1,200+ projects
We introduced TOGAF in the 2000s before it became fashionable. ArchiMate since version 2.0 in mid-market projects. This experience cannot be abbreviated - and it is the real difference between a dogmatic roll-out and a pragmatic solution in the SME sector.
Thirdly
100% vendor-independent and owner-managed
No commissions, no partner levels, no implementation margin in the background. We recommend the tool that fits your architecture - not the one we earn money from.
+ Advantage for SMEs
You speak directly with Dr. Dreher
Not with a junior consultant in a third sub-team.
"The benchmark is not the completeness of the models. The benchmark is whether a managing director can make a decision at the end of the workshop that would not have been possible without the framework. Trust comes from practical answers - not from the level of training."
Next step: 30 minutes directly with Dr. Dreher
In a 30-minute initial meeting, we clarify with you which framework modules have the greatest leverage in your current situation - and which you can deliberately leave out. You leave the meeting with a concrete recommendation and a clear next step, not a sales pitch.
Frequently asked questions about EAM frameworks in SMEs
Does every medium-sized company need a complete framework like TOGAF?
No. A complete TOGAF roll-out is almost always oversized for SMEs. We recommend a "best-of" approach: only use the building blocks that solve a specific current problem. Typically, ArchiMate 4.0 for visualization plus two to three TOGAF modules (ADM cycle, capability model) are sufficient. Everything else is added as required.
Which framework combination do you recommend as standard for DACH SMEs?
Our most common recommendation: ArchiMate 4.0 as the visualization language, selected TOGAF modules (ADM cycle, capability model) for the process, BIZBOK v15 for the business view, supplemented by SAFe concepts if several agile teams are involved, and selected COBIT 2019 objectives for audit and compliance requirements.
How long does it take to introduce a pragmatic framework combination?
The first visible results - a capability map on one page, an initial ArchiMate visualization of the current architecture, a prioritized backlog - are achieved in four to eight weeks. Complete anchoring in the steering committee and in investment planning is a continuous process over six to 24 months.
What is the difference between TOGAF and ArchiMate, and do you really need both?
TOGAF is a procedure - like a construction manual. ArchiMate is a notation - like the blueprint drawing set. In practice, we recommend both, but not orthodox: the ADM logic from TOGAF, without being formally TOGAF-certified, and ArchiMate as a language, without using any type of diagram.
Which tools do you typically use with ArchiMate?
In SMEs, we often start with Archi (open source) - freely available, sufficient for the first nine months. When maintenance and versioning become more important, many of our customers switch to Sparx Enterprise Architect or BiZZdesign Horizzon.
How does Dreher Consulting deal with frameworks in heterogeneous SME environments?
Lean as-is assessment in two to four weeks, targeted selection of the relevant framework modules, integration into your existing processes - without corporate bureaucracy. In this way, we have reduced architecture documentation by around 70 % in a medium-sized company project and at the same time noticeably increased transparency.
What role does AI play in the use of EAM frameworks?
AI accelerates three things in particular: the automated detection of interface redundancies, the creation of initial ArchiMate models from existing documents and the prioritization of migration roadmaps. We document AI recommendations in a comprehensible way - never as a black box. Our AI-supported SCOReX® model is primarily used for vendor and portfolio issues.
Found this helpful? Let’s explore how these insights could benefit your business.
Click the Contact Us button to connect with me directly.
