Business architecture is the discipline that maps what an organization does and how it delivers value, in business terms, independent of the systems and technology underneath. It answers four questions: what is the business able to do, how does value flow to the customer, what information does it run on, and how is it organized. It is the business-facing layer of enterprise architecture, and its main reference is the Business Architecture Guild’s BIZBOK Guide.
Done well, it gives leaders a shared, technology-neutral picture of the business, so a strategy decision can be traced to the capabilities and value streams it touches, before anyone writes a line of code. This guide covers the four core domains, what business architecture is used for, how it differs from enterprise and solution architecture, the tools, and certification.
What is business architecture?
Business architecture is a blueprint of the enterprise as a business, not as a set of IT systems. It describes the organization’s capabilities, value streams, information, and structure, and how they connect to strategy. Because it stays in business language, the same blueprint is readable by an executive and usable by an architect, which is the whole point: it bridges strategy and execution.
The discipline is codified in the BIZBOK Guide (A Guide to the Business Architecture Body of Knowledge), published by the Business Architecture Guild. BIZBOK is where the core concepts below, the domains and the blueprints, are defined and kept current.
The four core domains
BIZBOK builds business architecture on four core domains. They are called “core” because they are the most stable parts of a business: capabilities and value streams change far more slowly than the org chart or the software.
| Core domain | What it maps | Example |
|---|---|---|
| Capabilities | What the business is able to do, independent of how or who does it | Manage Orders, Develop Products, Service Customers |
| Value streams | The end-to-end stages that deliver value to a stakeholder | Acquire to Onboard, Order to Fulfill |
| Information | The core business objects and what they mean | Customer, Product, Order, Contract |
| Organization | The business units, roles, and how they relate | Divisions, teams, and partner roles |
The power is in the links between them. A capability map is a layered list of what the business does: a Level 1 capability such as “Customer Management” breaks into Level 2 capabilities like “Customer Onboarding,” “Customer Support,” and “Customer Retention.” A value stream then shows the stages that deliver value, for example “Order to Fulfill” running Receive Order, Validate, Allocate Inventory, Pick and Pack, Ship, and Invoice, with a capability enabling each stage. Map the two together and you can see exactly which capability a strategic goal depends on.
Around the four core domains sit extended domains: strategy, initiatives, products, stakeholders, and policies. BIZBOK represents all of them, and their relationships, through a set of blueprints, the most common being capability maps, value stream maps, organization maps, information maps, strategy maps, and initiative maps.
A worked example: a capability map for a manufacturer
Abstract definitions only go so far, so here is a partial capability map for a manufacturer that runs on ERP. The left column lists Level 1 capabilities, the middle breaks each into Level 2, and the right shows the value stream the capability mainly serves. Notice that the same capability can feed more than one value stream, which is exactly what the map is meant to reveal.
| Level 1 capability | Level 2 capabilities | Main value stream |
|---|---|---|
| Product Management | Product Design, Bill of Materials, Product Lifecycle | Concept to Product |
| Order Management | Order Capture, Credit Check, Order Fulfillment | Order to Fulfill |
| Procurement | Sourcing, Purchasing, Supplier Management | Procure to Pay |
| Manufacturing | Production Planning, Scheduling, Shop-Floor Execution | Plan to Produce |
| Inventory Management | Warehousing, Stock Control, Replenishment | Order to Fulfill |
| Finance | Accounts Payable, Accounts Receivable, General Ledger | Record to Report |
This is where business architecture pays off for an ERP program. Because the capabilities are defined in business terms and stay stable, they become the checklist for what the ERP must support and the shared language between the business and the implementation team. The inventory management capability, for instance, is one box on this map, but it enables both the Order to Fulfill and Plan to Produce value streams.
What business architecture is used for
- Strategic alignment. A capability map shows leaders what the business does well and where the gaps are, so investment goes to the capabilities that actually move a goal, not to whichever department shouts loudest.
- Mergers and acquisitions. Overlaying two capability maps shows exactly where two businesses duplicate capabilities and where they complement each other, which is the fastest way to plan an integration.
- Digital transformation. New digital initiatives map to the capabilities and value streams they change, so the program targets real business outcomes rather than technology for its own sake.
- Regulatory compliance. Tracing a regulation to the capabilities and value streams it governs shows precisely which processes and controls need to change, which matters in banking, insurance, and healthcare.
- Product and process improvement. Mapping a value stream end to end exposes the redundant steps and bottlenecks that are invisible inside any single department, for example in a manufacturer’s inventory and fulfillment flow.
Business architecture vs enterprise, solution, and IT architecture
These terms overlap, which causes endless confusion. The short version: business architecture is one layer inside enterprise architecture, and the others sit below it.
| Aspect | Business Architecture | Enterprise Architecture | Solution Architecture | IT Architecture | Business Analysis |
| Focus | Aligning business strategy with operating reality | The whole picture: business, data, application, and technology | Designing a specific solution to a business problem | Technology infrastructure and systems | Eliciting business needs and requirements |
| Scope | Capabilities, value streams, information, organization | The strategic context that solutions fit into | One project or problem | IT systems and platforms | Detailed needs on a project |
| Level | Broad, business-wide | Broad, enterprise-wide | Specific project | Technology-centric | Project or initiative |
| Relationship | Sets the business context for the rest | Contains business architecture as its top layer | Works within the context business architecture sets | Supports the goals business architecture defines | Relies on business architecture for alignment |
Where it fits with TOGAF and Zachman
Business architecture is not a rival to the big enterprise frameworks; it is the business content those frameworks organize. TOGAF devotes a whole phase of its Architecture Development Method (Phase B, Business Architecture) to it, and the Zachman Framework classifies its artifacts across the top rows of its grid. In practice, BIZBOK supplies the business-architecture method and blueprints, while TOGAF supplies the surrounding delivery process.
Tools
Business architecture does not need heavy tooling to start; many teams begin with capability and value stream maps in a spreadsheet or a diagramming tool. As the practice matures, dedicated enterprise architecture platforms such as LeanIX, Ardoq, Bizzdesign, MEGA, and Sparx Enterprise Architect add a shared repository, so a capability links to the applications, value streams, and initiatives that touch it, and a change in one place is visible everywhere. The tool matters less than keeping the maps current and connected to strategy.
Certification
The main credential is the Certified Business Architect (CBA), run by the Business Architecture Guild and aligned to the BIZBOK Guide. The Guild, founded in 2010, publishes BIZBOK (currently version 13) and administers the CBA exam, which tests knowledge of the core domains, blueprints, and how they connect to strategy. It is the closest thing the discipline has to a standard qualification. TOGAF certification is a useful complement for architects who work across the wider enterprise architecture process.
FAQs
What is BIZBOK?
BIZBOK is A Guide to the Business Architecture Body of Knowledge, the main reference for the discipline, published and maintained by the Business Architecture Guild (currently version 13). It defines the core concepts, the four core domains, and the blueprints such as capability maps, value stream maps, organization maps, information maps, strategy maps, and initiative maps.
What is the Business Architecture Guild?
The Business Architecture Guild is the professional body for business architecture. Founded in 2010, it publishes the BIZBOK Guide and administers the Certified Business Architect (CBA) certification, and it sets the de facto standards for the discipline.
What are the four core domains of business architecture?
Capabilities (what the business is able to do), value streams (how value is delivered to a stakeholder), information (the core business objects and their meaning), and organization (the business units and roles). BIZBOK calls these the core domains because they are the most stable parts of a business.
How is business architecture different from enterprise architecture?
Business architecture is the business-facing layer of enterprise architecture. Enterprise architecture spans four domains: business, data, application, and technology. Business architecture covers only the first of those, describing capabilities, value streams, information, and organization in business terms, independent of the systems that support them.
Conclusion
Business architecture earns its place by giving an organization one clear, technology-neutral view of what it does and how it creates value. Built on the four core domains and expressed through capability and value stream maps, it lets leaders connect strategy to the parts of the business that deliver it, and it gives every downstream architecture a stable foundation to build on. Start with a capability map, keep it current, and tie it to strategy, and the rest of the discipline follows.
References