An enterprise architecture function reports on standards compliance and diagram coverage. Leadership cannot tell whether it is adding value. What should it measure instead?

Why the current metrics fail

They measure the function's activity, not its effect. Standards compliance and documentation coverage describe how much governance has been applied, and a system can be fully compliant and slow, expensive and fragile.

They also invite gaming: coverage rises by producing documents, and compliance rises by relaxing standards.

What to measure instead

• Delivery flow: lead time from decision to production, deployment frequency, change failure rate. If the architecture function is doing its job, these improve — because reducing coupling, providing paved roads and removing coordination is what architecture does.
• Cost per unit of business activity, trended. Architecture decisions determine cost structure more than any other function, and the unit metric shows whether they are compounding.
• Incident rate by contributing factor, particularly the proportion caused by interactions between services rather than by individual failures — which is the class architecture is uniquely responsible for.
• Paved road adoption, voluntary and measured, which is the best available proxy for whether the platform is genuinely useful.
• Time to onboard a new team or launch a new market, which measures whether the architecture supports the business's actual growth mechanism.
• Duplication: how many implementations of the same capability exist. It quantifies a real cost and it moves when rationalisation works.

The metric that is most revealing and least used

How many teams must change for a median feature. It measures whether boundaries match the way work arrives, which is the single largest determinant of delivery speed and the thing an architecture function is most able to influence.

A number above two indicates a boundary problem that no amount of process improvement will fix, because the cost is structural.

The framing that makes it credible

Architecture is accountable for outcomes, not artefacts. A function measured on documents produces documents; one measured on flow, cost and reliability produces changes to the system.

The risk is attribution — these metrics move for many reasons — and the honest response is to use them as direction rather than as a scorecard, paired with specific claims: this decision removed this coordination, this platform reduced this cost.