Business Architecture vs. Business Process: Bridging Strategy and Execution

What Is Business Architecture?

Business architecture is a structured, holistic description of an organization from the perspectives of "what it does," "why it does it," "who does it," "where it is done," and "how it is done." Two authoritative definitions are commonly referenced:

Business Architecture Guild: Business architecture represents a holistic expression of multi‑dimensional business perspectives — capabilities, end‑to‑end value delivery, information, and organizational structure — and the relationships among these perspectives and strategy, products, policies, initiatives, and stakeholders.

Object Management Group (OMG): Business architecture is a blueprint of the enterprise in terms of governance structure, business processes, and business information.

In practice, business architecture acts as a bridge between strategic intent and operational reality. LeanIX describes it as a blueprint that depicts how an organization aligns strategic goals with operational reality.

Based on these definitions and practical experience, business architecture typically encompasses the following key dimensions:

Value Stream: How the organization delivers value from the stakeholder perspective.

Business Capability: The "ability to do" things the organization must possess to achieve strategy and deliver value.

Organization: Which organizational units are responsible for capabilities, value streams, or processes.

Information / Business Information: The information resources that support capabilities and processes.

Process / Operationalization: Although processes belong to the operational layer, they are mapped and associated within business architecture.

What Is Business Process?

Business process refers to a series of ordered, well‑defined activities or tasks — performed within or across organizations — that transform inputs into outputs to create value for customers or stakeholders. Wikipedia defines it as:

"A collection of structured, related activities or tasks performed by people or equipment in a specific sequence to produce a service or product (to satisfy a customer or an organizational goal)."

Key characteristics of business processes include:

Defined start and end: Clear inputs, outputs, and boundaries.

Cross‑organizational / cross‑functional: Often span departments and roles, requiring collaboration.

Value‑creation oriented: Ultimate purpose is to deliver value to customers, the organization, or stakeholders.

Modelable, measurable, optimizable: Can be described with flowcharts, swimlane diagrams, BPMN, and continuously improved.

To manage processes systematically, organizations often establish a process architecture (or process classification framework) — a layered, categorized model that defines process boundaries and relationships. For example, the APQC Process Classification Framework (PCF) provides 13 high‑level categories and five process levels. This helps answer governance questions such as "Are processes fully covered?", "Who owns each process?", and "How do processes relate to each other?"

Relationship Between Business Architecture and Business Process

The relationship can be analyzed from two dimensions: layer positioning and purpose.

(1) Layer Comparison

Business architecture resides at the conceptual / strategic layer : it describes the structure of "what the organization wants to become," "what it must do," and "why it does it."

Business process resides at the logical / operational layer : it embodies "how to do it," "who does it," and "in what sequence" within the business architecture.

In other words, processes are the operational realization of capabilities, value streams, and other architectural elements.

For example, the business capability "Customer Onboarding" in the architecture states that the organization possesses the ability to onboard customers. The concrete "Customer Onboarding Process" then specifies the steps: collect customer information, approve, activate account, notify customer.

(2) Mapping and Support Relationship

In business architecture, value streams, business capabilities, organization, and information need to be operationalized through processes . For instance, value streams and capabilities are "realized" by processes at the execution layer.

Processes also depend on business architecture for direction, boundaries, and semantics: a process must belong to a value‑stream stage, support a specific capability, and be owned by an organizational unit.

The flow can be visualized as: Business Architecture → Process (and Process Architecture) → Concrete Process Models / Tasks .

(3) Governance and Usage Differences

When an organization adopts business architecture, the goal is often "to clarify business structure, capabilities, and value streams from a strategic view"; processes are secondary, serving as mappings of capabilities and value streams.

When an organization adopts process management, the goal is often "end‑to‑end process optimization, bottleneck elimination, efficiency improvement"; processes become the primary focus, while business architecture provides supporting context.

In practice, the two are frequently built collaboratively : business architecture supplies the "why" and "what" perspective, while processes supply the "how" and "who" perspective.

Reference: LeanIX Business Capability .