VOL. IX · CH. 9.1 · ENTERPRISE ARCHITECTURE

Business Architecture

The layer that describes an organization's actual structure — before any technology decision is made.

DivisionEnterprise Architecture

DifficultyAdvanced

Prerequisites8.1

1 min read · 315 words

9.1.1Definition

Business architecture is a formal description of an organization's strategy, capabilities, processes, and organizational structure — independent of any specific technology or system. It answers "what does this business actually do and how is it organized to do it" as a foundation the other enterprise architecture domains (9.2–9.4) build upon.

9.1.2Why It Exists

Technology decisions made without a clear model of the business they serve tend to solve local problems while creating organizational misalignment — a system built perfectly for one department's process while ignoring how it connects to five others. Business architecture exists to establish that organizational understanding first, so downstream technology architecture decisions (9.2, 9.3) are grounded in real business capability and process rather than assumption.

9.1.3Core Artifacts

Capability maps — a structured inventory of what the business can do, independent of how (9.5).
Value streams — the end-to-end sequence of activities that deliver value to a customer or stakeholder.
Organizational structure — how teams, roles, and reporting lines are arranged relative to those capabilities and value streams.

9.1.4Common Mistakes

Jumping straight to technology architecture (9.2, 9.3) with no business architecture foundation, producing systems well-suited to an assumed structure that doesn't match how the business actually operates.
A business architecture that's purely academic, produced once and never referenced in actual technology or process decisions.
Confusing organizational chart with capability map — describing who reports to whom rather than what the business can actually do.

9.1.5Best Practices

Establish business architecture before major technology architecture decisions, not retroactively to justify them.
Keep capability maps and value streams as living references, actively used in prioritization and architecture decisions.
Distinguish organizational structure from business capability — the two evolve independently.

Real-World ExampleTOGAF, the most widely-adopted enterprise architecture framework, explicitly places business architecture as the foundational layer beneath application, data, and technology architecture — the same sequencing this chapter describes.

← Back to Part IX — Enterprise Architecture