TOGAF 10 Architecture Board Duties & Huawei's Multi-Level Governance Model
This article outlines the TOGAF 10 Architecture Board's key responsibilities — ensuring sub-architecture consistency, component reuse, compliance, and cross-boundary decision escalation — and details how Huawei operationalizes these principles through a layered governance structure comprising the Enterprise Architecture Committee, Transformation Steering Committee, Project Office, and Requirements & Architecture Management Teams to align local changes with corporate strategy.
TOGAF 10 Architecture Board Responsibilities
In TOGAF 10, the Architecture Board is a cross-organizational body primarily responsible for overseeing the implementation of architecture strategy — i.e., enforcing architecture governance. The board typically pursues the following objectives:
Provide a basis for all architecture-related decisions
Consistency across sub-architectures
Establish component reuse targets
Enterprise architecture flexibility:
Meet changing business needs
Leverage new technology
Enforce architecture compliance
Improve the maturity of the architecture discipline within the organization
Ensure adoption of architecture-based development principles
Support visible escalation capability for cross-boundary decisions
Huawei's Architecture Governance Practice
Both Huawei Data Way and Huawei Digital Transformation Way mention the Enterprise Architecture Committee (EAC), but do not describe its governance mechanics in detail. The following synthesis is based on publicly available materials and represents the author's personal view.
Huawei's architecture governance extends beyond the headquarters EAC to include multiple architecture teams: the Transformation Project Office (PO), Business Transformation and IT Management Teams (3Ts), and Requirements and Architecture Management Teams (RAMTs). Through collaboration among these multi-level teams, Huawei prevents local architecture changes from failing to connect with overall strategy.
In cooperation with the Transformation Steering Committee (ESC) and the Transformation Project Office (PO), the EAC provides architectural support and assurance for business and technology transformations. For example, when introducing new technologies, adjusting business models, or conducting mergers and acquisitions, the EAC ensures these transformations align with the existing architecture strategy while driving architectural adjustments to support the enterprise's new direction.
The Requirements and Architecture Management Teams (RAMTs) are responsible for embedding EAC's architecture decisions and principles into concrete project execution. They act as a bridge between the EAC and project teams, ensuring projects follow the established architecture strategy from initiation to delivery.
Architecture issues or conflicts encountered by project teams during execution can be fed back to the EAC via the RAMTs for resolution, ensuring projects proceed smoothly while remaining compliant with architecture requirements.
Reference: TOGAF Enterprise Architecture Board
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.