Your organisation has an architecture standard that most teams ignore. Leadership asks you to enforce it. How do you approach this?

Find out why it is ignored before enforcing anything

The reasons are few and they demand different responses:

Nobody knows it exists. A communication problem, and the cheapest to fix.

It is unclear or contradictory, so teams cannot tell what compliance means. Fix the standard.

Following it is harder than not. No supported implementation, no template, no tooling — so compliance is a research project each team repeats. This is the most common reason and enforcement will not change it, only add friction to something already expensive.

It is wrong. The standard was written for an estate that no longer exists, or by someone without the context. Twenty teams deviating is evidence about the standard, not about the teams.

The response that works

Make compliance the easy path before making it mandatory. A supported implementation, a service template that produces a compliant service by default, and automated checks that tell a team immediately rather than at a review.

A standard that is automatically checked and automatically satisfied by the golden path stops being a standard anyone thinks about, which is the goal.

Then enforce the outcome, not the mechanism

Mandate what must be true — signed artifacts, no long-lived credentials, evidence of change control — rather than how it is achieved. Teams meeting it another way are complying, and their approach is worth studying rather than correcting.

Give it an exception route

There will be a legitimate case the standard did not anticipate. A time-boxed waiver with an owner, a compensating control and an expiry keeps the deviation visible and bounded. A standard with no exception path gets ignored rather than debated, which is where you started.

And review the waivers in aggregate: twenty waivers against one standard means the standard is wrong.

What to tell leadership

Enforcement without making compliance easy produces compliance theatre — teams meeting the letter while routing around the intent, and the architecture function losing the signal that tells it what to fix. Propose the sequence instead: fix the top reason for non-compliance, make the compliant path the easy one, automate the check, then enforce. That is slower to start and it is the version that holds.