Five-Step Business Architecture Design: From Strategy to Execution
This article outlines a five-step methodology for business architecture design, covering strategic capability decomposition, end-to-end process mapping, control point extraction, business object identification, and metric decomposition to create an executable, monitorable, and optimizable architecture framework.
In enterprise digital transformation, business architecture design serves as the critical link between strategy and execution, supporting process optimization, system development, and metric management. The article presents a complete five-step methodology that forms a closed loop from strategy to implementation.
Step 1: Decompose Core Capabilities Based on Strategy
The starting point is strategy decomposition, converting enterprise strategy into a clear business capability map through four sub-steps:
Business Domain Design : Identify primary business domains aligned with company strategy and organizational responsibilities (e.g., strategic planning, supply chain management, marketing, HR, finance, safety). Output: Business Domain View.
Level-1 Business Classification Design : Subdivide each domain into level-1 classifications (e.g., supply chain includes demand management, procurement management, warehousing and distribution). Output: Level-1 Business Classification View.
Level-2 Business Classification Design : Further refine level-1 into level-2 classifications (e.g., demand management splits into demand forecasting management, demand declaration management). Output: Level-2 Business Classification View.
Business Capability Design : Extract business capabilities from level-2 classifications (e.g., warehousing and distribution management refines into inbound management, outbound management, inventory management, maintenance management). Output: Business Capability List and Business Capability View.
The core deliverable is the Business Capability Map , which forms the foundation for process design, object identification, and system construction. The article references the APQC Process Classification Framework (PCF) with 13 high-level categories and 5 process levels, and a separate article on business capability identification.
Step 2: Connect End-to-End Process System
After capability decomposition, business processes must be connected end-to-end to ground strategy. Five sub-steps:
Operational Business Process Mapping : Identify operational processes for each business capability. Output: Operational Business Process List and Process Diagrams.
Operational Process Relationship Mapping : Define inputs, outputs, and dependencies between processes to form a collaboration network. Output: Operational Process Collaboration List.
Enterprise-Level Business Process Mapping : Build top-level end-to-end process blueprints along main lines such as "asset full lifecycle" or "customer full-service journey." Output: Enterprise-Level Business Process Diagram.
Professional-Level Business Process Mapping and Connection : Link operational processes of each profession into closed loops, categorized into strategy & planning, value creation, enablement, and supervision & control. Output: Professional-Level Business Process Diagram.
Operational Process Step Mapping : Standardize operational processes into detailed steps to support control point design and IT implementation. Output: Operational Process Step List.
The result is a complete, executable process system providing a panoramic view for subsequent digitalization and process optimization.
Step 3: Extract Process Control Points
To ensure processes are controllable, compliant, and secure, control points are extracted in three sub-steps:
Identify Business Activity Risk Points : Analyze risks across eight dimensions (e.g., operational errors, process bypass, unauthorized access, inaccurate information, legal compliance risks). Output: Risk Point List.
Define Business Step Control Measures : Design controls referencing five control types (role-based, permission-based, time-based, step-based, delivery-based) and select IT enforcement methods (operation control, alerts, intelligent monitoring). Output: Business Control Measures List.
Map Process Roles and Permissions : Clarify execution, review, and supervision roles with corresponding permissions to support system permission configuration and responsibility matrices. Output: Business Role List.
This phase ensures processes not only run but run safely, compliantly, and transparently.
Step 4: Identify and Classify Business Objects
Business objects are core elements of enterprise digitalization; clear identification enables data models and systems to land. Two sub-steps:
Business Object Mapping and Classification : Identify objects involved in processes (e.g., contracts, equipment, suppliers) and distinguish ordinary objects from cross-professional shared core objects. Output: Business Object List.
Standard Business Activity Extraction : Using core object lifecycles as the main thread (e.g., contract from signing to archiving), extract standard business activities and link them to processes. Output: Standard Business Activity List.
Object identification achieves seamless business-data alignment, providing input for data architecture and system development. The article cites Huawei's understanding of business objects.
Step 5: Decompose Metrics
The final step translates strategic goals into quantifiable metrics to close the management loop:
Management Metric Mapping : Organize result-oriented management metrics from enterprise strategy and operational goals (e.g., procurement on-time rate, inventory turnover rate). Output: Management Metric List.
Metric Decomposition and Process Linkage : Break result metrics into process metrics and attach them to business capabilities and operational processes, ensuring metrics drive process optimization. Output: Metric Decomposition Table and Process Mapping Table.
Through metric decomposition, business architecture moves beyond design into a monitorable, optimizable, and implementable management system. The methodology references the Huawei Enterprise Architecture Design Method .
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Architecture Practice Methods
Frontline architect. Sharing knowledge and insights in enterprise architecture.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
