What this tier actually looks like.
The EA function exists. Some delivery teams invite architects in early; many don’t. The architecture principles document is updated annually; nobody reads it. The capability model is a project artefact, not a living instrument that drives investment.
You probably have:
- A central EA team of 3–8 architects.
- A 30+ page architecture principles document.
- A capability model in LeanIX / Ardoq / Visio.
- ADRs in some projects, inconsistently used.
- A design review board that meets fortnightly.
- Mixed reception across business units — loved in 2–3, ignored in others.
Why most teams get stuck here.
Consultative-tier EA functions stall because the work product is artefacts, not behaviour change. Three patterns that keep teams here:
- Principles in PDFs. If they aren’t encoded as policy-as-code or platform defaults, they’re aspirational.
- Architects-as-reviewers, not enablers. Approval queues breed routing-around; enablement clinics breed adoption.
- Capability model used by EA, not by the business. If the CFO doesn’t consult it in investment decisions, it’s overhead.
The three substrate moves to the next tier.
1. Encode the top 3 principles. Subtract the rest.
Pick the principles most cited and most violated. Encode them as OPA / Kyverno rules, platform module defaults, or paved-path scaffolds. A principle nobody can violate without warning is a principle. Subtract the rest from the principles doc — if they’re not enforced, they don’t exist.
2. Federate. Embed an architect in the top 2 streams.
Stop trying to scale from the centre. Central EA team owns cross-cutting concerns; embedded architects sit in the highest-coupled streams (typically payments, identity, data, AI). Dotted-line to central. Team Topologies calls this stream-aligned EA.
3. Tie capability investment to outcome metrics.
Make the capability model a real instrument. Every major investment decision uses it; every quarter, outcome metrics per capability are reported to the board. The function stops being “EA people work on architecture artefacts” and becomes “EA people make sure the next $5M lands on the highest-leverage capability.”
What changes when you cross.
- Decision velocity doubles. Encoded principles + ADRs + federated architects = no re-litigation.
- EA becomes invisible because it works. The platform enforces what EA decided; engineers don’t feel the function as a gate.
- Capability model survives leadership change. When the CIO changes, the artefacts that survive are the ones the business uses.
- Audit conversations get easier. “Show us your architecture principles” → policies-as-code repository, not PDFs.
This is the Governed tier. ~20% of EA functions reach it. The jump from Governed to Enabling (~8%) is what crosses from “works inside the EA function” to “encoded as a property of the org.” See The encoded enterprise architect essay.
Run the diagnostic.
To find out whether your team scores at this tier or another, run EA Operating Model. It takes 2–4 minutes and surfaces both your overall tier and the capability breakdown that shows you where the move starts.
For the bigger picture: the compound diagnostic takes results from all six diagnostics and shows you the substrate gap that bounds your overall delivery, not the per-discipline symptom.