Enterprise Architecture Value Model - Connect architecture's horizontal ownership to your full IT Management strategy
Enterprise Architecture Value Model
Chapter 43. Connect architecture's horizontal ownership to your full IT Management strategy
Your architecture function’s horizontal ownership model does not exist in isolation from your other IT Management disciplines. It is the connective infrastructure through which Application Portfolio Management, Technology Portfolio Management, and every other IT Management domain is made practically real at the enterprise level — and its value compounds as those connections are made explicit.
Your APM governance covers the applications that deliver business capability. Those applications run on infrastructure that your architecture function’s platform engineering capability provisions and manages. They are built with development tooling your architecture team owns and operates. They are deployed through CI/CD pipelines your architecture team maintains. They are monitored through the observability platform your architecture team owns. When your architecture function owns these horizontal foundations, the quality, consistency, and governance compliance of your entire application portfolio improves — not because your architecture team wrote better standards, but because the engineering every application depends on has been elevated by its ownership.
Your TPM governance covers the technology portfolio — the platforms, frameworks, tools, and infrastructure components that applications are built on. When your architecture team owns the development toolchain, the IaC library, and the platform engineering capabilities, the Technology Standards Register is not just a document. It is the engineering reality of what every team uses. Approved technologies are the ones your architecture function’s platforms support well. Deprecated technologies are the ones your architecture function’s platforms are being engineered away from. The standard is the platform — and the platform is the enforcement.
The businesses your IT organization serves are the ultimate consumers of your architecture function’s horizontal ownership. When cross-portfolio automation reduces the time required to process a regulatory filing from weeks to hours, the business notices. When your observability platform detects and surfaces a production issue before it affects customers, the business benefits. When your AI development platform enables delivery teams to ship capabilities faster, the business sees it in the products and services it brings to market. Your architecture function’s connection to the businesses it serves is not through governance presentations. It is through the operational performance of the platforms it owns.
Copyright for the International Foundation for Information Technology (IF4IT): 2008 - Present
Legal Disclaimers