Loading content
Architecture governance defines structures, roles and processes to make architectural decisions consistently, transparently and value-driven. It ties strategic goals to technical standards, ensures compliance and enables aligned choices about longevity and platform selection. Governance increases transparency and risk control.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
Architecture governance steers how an organization makes, reviews, and documents architectural decisions. It connects strategic goals with technical standards, clarifies responsibilities, and sets rules for approvals, exceptions, and traceability.
The term belongs to enterprise architecture practice and became important when organizations needed to coordinate architecture decisions across multiple teams, systems, and change initiatives. TOGAF describes a governance environment with roles, responsibilities, and relationships. Architecture governance makes such decisions visible so that standards, exceptions, and long-term evolution are managed at an organizational level rather than only inside individual projects.
Think of architecture governance as a constitution with a control loop: first, decision rights and binding standards are defined. An architecture board or review process checks initiatives against these guardrails and approves only justified exceptions. Architecture Decision Records capture what was decided, why, and with what consequences. This keeps architecture comparable and traceable across teams.
API design, lifecycle, and operations are aligned with the broader architecture rules.
Rules, metrics, and review steps steer decisions toward desired patterns and limit risky ones.
It is clear who may set standards, approve exceptions, and make binding architecture decisions.
Shared rules create consistency; deviations remain possible but must be justified and documented.
Decisions are documented so that context, rationale, and consequences can be reviewed later.
Architecture governance is especially useful when multiple teams must steer shared platforms, APIs, or target architectures. It supports platform selection, migration paths, and exception handling. Its value depends on clear mandates, lean review processes, and accepted standards; too much control slows delivery, too little leads to drift and inconsistent solutions.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.