If leverage is measurable, the harder question is not whether it exists. It is how you move toward it.
Most architecture functions did not choose artefact production deliberately. They inherited it. Templates existed. Governance boards existed. Documentation satisfied audit. The system rewarded visible activity.
You do not dismantle that overnight. You transition it.
The mistake organisations make is attempting reform through declaration. New framework. New template. New operating model slide. Nothing changes. Because the incentives remain untouched.
Transition Begins with Containment, Not Revolution
Pick one domain where ambiguity is costly. Security. Data residency. Integration standards. Not the entire enterprise.
Take one recurring debate. Convert it into a bounded constraint with a named owner and visible escalation path.
Then measure one thing: decision latency. How long does it take from proposal to bounded answer? Not workshop completion. Not document sign-off. Decision.
If latency compresses without increasing uncontrolled deviation, leverage is forming. If it expands, you have discovered where authority is still symbolic.
The Second Step Is Deviation Visibility
Do not eliminate exceptions. Surface them.
When three projects request the same exemption, the pattern is not indiscipline. It is structural drift. Refine the constraint.
This is how leverage compounds — not through more documentation, but through shorter decision cycles and clearer ownership.
The Role of Artefacts Changes, Not Disappears
In regulated environments, artefacts remain. They do not disappear. But their role changes.
Documentation becomes trace of decision, not substitute for it.
Architecture does not need to produce less. It needs to produce differently.
The Shift Is Operational, Not Philosophical
Measure latency. Name escalation. Track deviation. Refine constraints. Repeat.
That is how an archive becomes an operating system.