tgroenwals shared this post · Apr 22

Justin Miller

If Enterprise Architecture becomes an approval gate, it slows the business down.

If it becomes a decision partner, it helps the business scale with confidence.

EA should not be where decisions go to wait, it should be where decisions go to get smarter.

The value of EA is not saying “yes” or “no.” It is helping leaders understand:

What risks are being created
What capabilities are being duplicated
What costs will scale over time
What decisions may limit future agility

That is how EA moves from governance theater to business value.

1 / 9

Pavel Kovtun agree with the framing, but I'd add a tension you didn't mention. like even the best EA team can't be a "decision partner" if the business treats architecture as free advice. if the org doesn't trust EA enough to invite them in early, they get invited in late, and late means approval gate by default. so, sometimes, moving from approval to partnership isn't just an EA choice, its an org choice about how decisions get made Apr 20 1 like

Shibaji Sankar Biswas Justin Miller Great point. One practical shift I’ve seen work is turning EA into a “decision service,” not a review gate.
A few things that help operationalize this:
Decision canvases for key choices (platform, vendor, integration) make trade-offs explicit upfront.
Guardrails, not approvals: Reusable patterns + reference architectures teams can apply without waiting
Embedded architecture: Architects sit with product/delivery teams during design, not after
Fast feedback loops: Lightweight checkpoints instead of heavy governance cycles
Metrics: Track decision cycle time, rework, and tech debt avoided
When EA shows up with tools, context, and guardrails, teams move faster and make better decisions. Apr 21 1 like

Public author posts