Key takeaways
- The Board sponsors the architecture activity and oversees the governance strategy.
- Decision rights over the target, relief, and enforcement remain with stakeholders.
- Monitoring contracts and meeting are operational responsibilities; formally approving the architecture is a governance one.
- Dispensations must remain consistent with the technology strategy.
- A small permanent core, with rotation, keeps the Board effective.
A cross-organization sponsor with limited rights
The Board is a cross-organization body representing the key architecture stakeholders. It sponsors the architecture activity and oversees implementation of the governance strategy. Its name does not matter: an “EA governance committee” plays the same role.
Large enterprises often have several Boards, with global, regional, or business-line scope, and at least two levels: local (domain experts, line responsibility) and global (organization-wide responsibility). Each receives explicit responsibilities, decision-making capabilities, and authority limits.
Classic failure pattern: a Board that believes it owns the target, its changes, relief, and enforcement. Those rights belong to stakeholders. The Board owns the process and issues a recommendation on the completeness and reliability of the work that produced the target.
General responsibilities
At the broadest level, the Board:
- provides the basis for all decisions about the architectures;
- ensures consistency between sub-architectures;
- sets targets for component reuse;
- enforces architecture compliance;
- supports a visible escalation capability for out-of-bounds decisions.
Operational perspective
Day to day, the Board:
- monitors and controls all aspects of Architecture Contracts;
- meets regularly;
- ensures effective and consistent management and implementation of the architectures;
- resolves escalated ambiguities, issues, or conflicts;
- provides advice, guidance, and information;
- ensures compliance and grants dispensations consistent with the technology strategy.
Governance perspective
From a governance standpoint, the Board:
- produces usable governance material and activities;
- provides a mechanism for formal acceptance and approval of the architecture, through consensus and authorized publication;
- acts as a fundamental control mechanism for effective implementation;
- spots divergence and plans realignment through dispensations or policy updates.
Setting up a Board
FURTHER STUDY · APPLICATION DETAILS
Several events often trigger its creation: a new CIO, a merger or acquisition, the launch of an EA program, significant business change. TOGAF recommends a core of about four or five permanent members, ten at most, with rotation to stay representative without becoming unwieldy. The authorized architecture requirements it has agreed are gathered in the Architecture Requirements Repository.
TERMS TO KNOW
The terms, in context.
- Architecture Board
- A cross-organization body that sponsors architecture and oversees the governance strategy.
- Decision rights
- Rights to decide on the target, relief, and enforcement, held by stakeholders.
- Dispensation
- A temporary authorized deviation, granted consistently with the technology strategy.
- Escalation capability
- A visible route to take an out-of-bounds decision to the right level of authority.
- Architecture Requirements Repository
- A view of authorized architecture requirements agreed with the Board.