Knowledge center · Architecture
What is business architecture?
Business architecture describes a company from the perspective of executive leadership: which capabilities it needs to reach its goals, which value streams and processes support those capabilities, who is accountable for them, and what information they require. It organizes the company by capabilities rather than by departments or systems. That shows where strategy actually reaches day-to-day work and where investment in data and technology belongs.
Author Thomas Wassum, Managing PartnerLast reviewed
The concept
Capabilities instead of departments
A capability is something a company has to be able to do, regardless of who does it today and with which technology: pricing orders, managing suppliers, or assessing risk. Capabilities rarely change; departments and systems change often. Aligning investment with capabilities therefore gives you a yardstick that survives reorganizations and system changes. The business capability map shows all capabilities on a single page.
In the Business Data Transformation Framework, business architecture belongs to the Understand and Define phases. It describes the current state and supplies the capabilities that the goals and criteria of a decision build on. Every later recommendation on data, infrastructure, or AI can then be traced back to a capability and a business goal.
Building blocks of a business architecture
- Business model, goals, and constraints
- Business capability map
- Value streams and core processes
- Accountability and decision paths
- Dependencies on systems and service providers
Distinction
How it differs from IT and process architecture
Process management improves workflows; IT architecture organizes applications and technology. Business architecture comes first and connects both to the goals of the company. It does not answer which system to introduce, but which capability that system should strengthen and who is accountable for it. In enterprise architecture, it forms the top layer, on which data, application, and technology architecture build.
In BEIA, business context, capabilities, operating model, and governance are four of the eight layers. Data, applications, and technology form the foundation underneath. Security, Risk & Compliance and AI readiness run across the layers.
Four layers from the business perspective
- Business context
- Business model, goals, and constraints that everything else aligns with.
- Capabilities
- What the company must be able to do, such as winning customers or fulfilling orders, regardless of technology.
- Operating model
- How the company works: structure, responsibilities, processes, and management.
- Governance
- Rules, roles, and decision paths the company uses to govern data and IT.
In practice
When business architecture pays off
Business architecture pays off whenever a decision affects several areas and the people involved have different views of the company: before growth, an acquisition, or a succession, before an ERP vendor selection, or when IT projects run without a clear link to the business. It then provides a shared map on which leadership, business units, and IT use the same terms.
A typical scenario: a midsize company with three sites is planning a new ERP system, and each site describes its requirements differently. The capability map shows that most capabilities are the same at every site and only a few genuinely set the business apart. The RFP gets shorter, and the bids become comparable.
The scenario is typical of our engagements, not a single client case.
Questions from leadership
What executives ask about it
Who should own the business architecture?
Executive leadership. Business units and IT can develop it together, but only leadership can decide which capabilities the company will need in the future and where it will deliberately not invest.
Do you need dedicated software for business architecture?
Not at the start. A one-page capability map and a clear assignment of processes, accountability, and systems take you further than a tool nobody maintains. Whether a tool is worth it becomes clear later, from how often things change.
How often does a business architecture need revising?
As often as the decisions that rest on it change. Because capabilities rarely change, it is usually enough to review the map at strategy shifts, acquisitions, or major system projects.
What is an operating model?
The operating model describes how a company works: how it is structured, who is responsible for what, how processes connect, and how it is managed. In business architecture, it connects capabilities to the people and processes that deliver them every day.
Author and sources
Who answers, and what it rests on
Sources and further reading
- The Open Group: The TOGAF Standard, 10th Edition, 2022 (external site)
- Business Architecture Guild: A Guide to the Business Architecture Body of Knowledge (BIZBOK Guide) (external site)
- The Open Group: ArchiMate Specification
- SIMO GmbH: BEIA · Business Enterprise Infrastructure Assessment, Leistungsbeschreibung mit Glossar der Betrachtungsebenen [in German], 2026
Page last reviewed:
Read on
The next question and the path behind it
Related question
How do you evaluate alternative enterprise architectures?
Several feasible options, future scenarios, and ten criteria instead of a premature target architecture.
Related question
How do you create reliable data flows?
One system of record per data set, binding KPIs, and reconciliations that expose discrepancies.
Matching service
Business Architecture
How SIMO handles this topic in an engagement: approach, results, and the questions executives ask.
See how SIMO structures and assesses alternatives.
Your next step
From the answer to the decision
The Decision Readiness Check shows how ready your own decision is. If you’d rather talk directly, book an initial call with a Managing Partner.
45 minutes, and you will know whether SIMO fits your decision.
How ready is your decision? Check it in 3 minutes.
Or call us: +49 6021 625 63 40