In the complex world of Enterprise Architecture (EA), the question “Are we doing a good job?” is critical but often difficult to answer. Without clear metrics, architecture practices can drift into bureaucracy or become disconnected from business reality. This tutorial explores the “Measures of Success” framework, a comprehensive method for evaluating a TOGAF-based architecture practice across six key domains.

The Core Philosophy: The Central Hub

At the heart of this framework lies the concept of the TOGAF-Based Architecture Practice. Think of this not just as a department, but as a dynamic engine that drives the organization forward. The infographic illustrates this practice as a central hub, surrounded by six distinct pillars. Each pillar represents a critical dimension of performance that, when measured, provides a holistic view of the organization’s architectural health.

1. Strategic Alignment (The North Star)

The first and perhaps most critical measure is Strategic Alignment. This domain answers the question: “Does our architecture actually support the business strategy?”

• Percentage of initiatives linked to strategic objectives: This is a quantitative measure. If an IT project is launched, can we trace it back to a specific strategic goal? If not, it might be a waste of resources.
• Stakeholder satisfaction: Architecture is a service. Are the business leaders and project managers satisfied with the support they receive? This is often measured through surveys or Net Promoter Scores (NPS).
• Unresolved strategic dependencies: This is a risk metric. Every architecture has dependencies. If dependencies are left unresolved, they become technical debt that hinders strategic progress.

2. Delivery Performance (Speed & Efficiency)

Once strategy is defined, the architecture must enable delivery. This domain focuses on the efficiency of the architecture practice in supporting projects.

• Reduction in project delays: A healthy architecture prevents roadblocks. If projects are consistently delayed due to “architecture issues” (e.g., missing requirements, lack of standards), the practice needs improvement.
• Reuse of approved building blocks: This is a core TOGAF concept. Are projects building the same thing from scratch, or are they reusing existing, approved assets (like a standard login module or payment API)? High reuse leads to faster delivery.
• Time required for architecture decisions: How long does it take to get an answer from the architecture team? Speed is a competitive advantage.
• Number of late design changes: If designs are changing late in the lifecycle, it indicates that the architecture was not thought through early enough (likely missing the “Pre-Project” or “Preliminary” phases).

3. Technology Effectiveness (Modernization)

This pillar evaluates the underlying technology landscape. Is the tech stack modern, efficient, and sustainable?

• Application rationalization: This is the process of reducing the number of applications. Are we running too many tools? Rationalization aims to consolidate.
• Reduction in duplicate capabilities: Similar to rationalization, this looks for redundancy. Do we have three different tools for email marketing? We should have one.
• Infrastructure utilization: How well are we using our hardware and cloud resources? Low utilization means wasted money.
• Platform standardization: Are we using a wide variety of platforms, or have we standardized on a few core ones? Standardization reduces complexity.
• Technology lifecycle risk: This measures the risk of running outdated technology (End-of-Life systems). High risk requires immediate attention.

4. Data Quality (The Foundation)

Data is the lifeblood of the enterprise. This domain ensures that data is accurate, complete, and accessible.

• Completeness of critical data: Do we have all the necessary data fields to run our business processes?
• Number of duplicate records: “Garbage in, garbage out.” High numbers of duplicates (e.g., multiple entries for the same customer) destroy trust in data.
• Data ownership coverage: In TOGAF, every data asset should have an owner. Are there data assets with no owner? If so, they are at risk.
• Data-quality issue resolution time: How fast can we fix a data problem? Speed here reflects the agility of the data management practice.

5. Governance & Risk (Control)

Architecture without governance is anarchy. This domain measures how well we control the architecture.

• Architecture compliance rate: Are projects following the standards defined by the architecture team? A low rate suggests the standards are too difficult to follow.
• Number and age of exceptions: Sometimes projects must deviate from standards. This is tracked via “exceptions.” If exceptions are old, they should be reviewed for permanent inclusion or removal.
• Security and regulatory findings: This is a direct measure of risk. How many security vulnerabilities or compliance breaches are found during architecture reviews?
• Percentage of initiatives reviewed at the appropriate stage: This is the concept of “Shift Left.” Are we reviewing architecture early enough (e.g., at the start of a project) rather than at the end when it’s too late to change?

6. Business Value (The ROI)

Ultimately, all the metrics above must translate into tangible business value. This is the “So What?” section.

• Cost reduction: The most direct benefit. Are we saving money through rationalization and efficiency?
• Faster product delivery: Time-to-market is a competitive metric. Does our architecture help us launch faster?
• Improved customer experience: A well-architected system is usually more stable and faster for the end-user.
• Increased operational resilience: Can the business survive a failure? Architecture plays a huge role in disaster recovery and uptime.
• Revenue or productivity improvement: Does the technology enable new revenue streams or make employees more productive?

Conclusion

Evaluating a TOGAF-based architecture practice requires a balanced approach. You cannot focus solely on cost reduction (Business Value) while ignoring compliance (Governance), nor can you obsess over standards (Strategic Alignment) if you are too slow to deliver (Delivery Performance). This framework provides a dashboard for the CIO and Enterprise Architects to monitor health, identify bottlenecks, and demonstrate value.

To effectively implement this framework, architects need robust tooling that can automate data collection and visualization. The Recommended tooling for this comprehensive evaluation is Visual Paradigm TOGAF ADM & AI Assisted. This platform enables the creation of detailed architecture models, facilitates the definition of business value metrics within the architecture repository, and leverages AI to assist in generating compliance reports and analyzing data quality, ensuring that the “Measures of Success” are not just theoretical concepts but actionable, data-driven realities.