Beyond Canned Metrics: Customizing Enterprise Architecture Toolkits for Real Value
Enterprise Architecture is a field where the true value, in my opinion, has yet to be fully realized. Toolkits like those offered by Forrester and Gartner are useful starting points, but they remain templates—frameworks designed for a generalized enterprise rather than the specific realities within your organization. Every operating model differs, and this variation creates incongruent metrics and discrepancies in how those metrics are applied across different enterprises.
The Purpose of Toolkits
Toolkits exist to provide an explicit way to identify value and articulate strategy in a structured manner. Beyond articulating an operating strategy, having a way to measure progress is essential for validating and steering that strategy within the organization. Without measurement, strategy becomes aspiration without accountability.
There are three categories typically present when describing the value of an EA toolkit:
Operating Metrics
These apply to efficiencies gained and measured within a process context. Operating metrics determine the coverage and scope of the EA practice itself. They answer questions like: How many business capabilities are documented? What percentage of technology decisions flow through architecture review? How quickly can we assess the impact of a proposed change? These metrics demonstrate that the practice is functioning and reaching the parts of the organization it needs to influence.
Cost Metrics
Cost metrics relate to operating expenses, outlining spend and spend reduction within the practice itself. For example, an organization might track the reduction in non-budgeted R&D as a particular innovation matures. Consider microservices adoption: early on, multiple teams may experiment independently, duplicating effort and infrastructure. As the EA practice matures its guidance and reference architectures, that scattered experimentation consolidates into purposeful, coordinated investment. The reduction in redundant spending becomes a measurable cost metric.
ROI Metrics
ROI metrics track the direct income versus expense associated with EA special projects. These are more elusive in the grand scheme, but with the right relationships and baseline data, they can be established and refined over time.
Consider an example: an EA program works to stand up a centralized system to perform a regulatory compliance function. Previously, each line of business maintained its own solution—duplicating technology, licensing, and operational overhead. The new centralized approach reduces duplicity and increases communication across the organization. The outcome saves each line of business an estimated percentage of their previous spend. That measurable savings, attributed to an EA-led initiative, becomes a concrete ROI metric.
Customize for Fit
Toolkits are a good way to present and track a company’s enterprise architecture strategy. However, I would urge customization to achieve fit within your organization rather than forcing a canned toolkit that begets canned metrics. The enterprises that extract real value from EA are those that adapt frameworks to their operating model, define metrics that matter to their stakeholders, and build measurement into the practice from the start.
The goal is not to satisfy a framework’s requirements but to demonstrate genuine business value in terms your organization understands and cares about.
Reference
Rico, D. F. (2006). A Framework for Measuring ROI of Enterprise Architecture. Journal of Organizational and End User Computing, 18(2).
