Enterprise Architecture as a discipline was built for a world that no longer exists. Monolithic systems. Waterfall projects. Centralized technology decisions that flowed through Architecture Review Boards before anyone could write a line of code.
That world produced governance models that made sense at the time — approval gates, target-state diagrams, comprehensive standards documents. And those models are now the single greatest source of friction between architecture functions and the product teams that create value.
If your EA function is primarily controlling technology decisions through centralized review boards, it is not doing enterprise architecture. It is doing governance theater.
The Symptoms Are Everywhere
Product teams bypass governance through shadow IT — not because they are reckless, but because the sanctioned path is slower than the problem demands. Innovation stalls behind review boards that meet monthly to evaluate decisions that needed to be made last week. Architecture documentation becomes performative — created to satisfy a checkbox, read by no one, influencing nothing.
The result is the worst of both worlds: the overhead of governance with none of its benefits. The architecture function loses credibility with the teams it is meant to serve, and fragmentation accelerates precisely because the people closest to the problems have no effective architectural guidance.
What Changed
The business environment that traditional EA was designed for has been replaced by one that operates on fundamentally different principles. Product teams work in short iterations with significant autonomy. Platform teams provide standardized services that enable consistency without requiring central approval. Architecture decisions are continuous and emergent, not episodic and prescribed.
In this environment, the Architecture Review Board is not a quality gate. It is a bottleneck that slows organizational decision cycles at exactly the moment when speed matters most.
John Boyd’s OODA loop — Observe, Orient, Decide, Act — provides the clearest framework for understanding why this matters. Organizations that iterate through decision cycles faster than their competitors gain decisive advantages. Traditional EA governance, by inserting approval delays into every cycle, systematically degrades the very capability that determines competitive position.
What Must Die
Static target-state diagrams that describe a future no one will build. Architecture standards documents in PDF format that no one reads. Review boards that function as gatekeepers rather than enablers. The entire concept of architecture as a separate function that approves or denies the work of delivery teams.
These artifacts and structures served a legitimate purpose when technology decisions were infrequent, high-cost, and difficult to reverse. In an environment where decisions are continuous, incremental, and increasingly reversible, they create overhead without proportionate value.
What Replaces It
Architecture does not disappear. It becomes an embedded discipline rather than a centralized function.
Platform teams own architecture decisions within their domains. They have the context, the delivery cadence, and the accountability. Enterprise architects curate patterns, identify systemic gaps, influence roadmaps, and coach — but they do not approve. The metaphor is a permaculture gardener shaping the overall environment, not a building inspector who can halt construction.
Patterns replace review boards. Product teams consume enterprise-approved patterns and platforms by default. When they need to deviate, a lightweight, timeboxed exception review replaces the traditional ARB process. The review is outcome-oriented — does the deviation create unacceptable risk or fragmentation? — not compliance-oriented.
Living architecture products replace static documents. Tech radars that teams actually consult. Architecture Decision Records with change history. Telemetry that makes architectural health observable and measurable. These tools influence decisions at the moment they are made, not weeks after the fact in a review meeting.
Enterprise architects operate like a platform team — with service-level agreements, measurable impact, embedded collaborators, and a product mindset. They provide shared architectural capabilities, reusable services, and coaching. Context, not condescension.
The AI Test Case
Artificial intelligence is the most consequential test of whether an architecture function has made this transition. In regulated industries, AI adoption creates genuinely competing demands — the need for speed and experimentation alongside compliance, ethical governance, and data privacy requirements.
Traditional EA responds predictably: establish a governance committee, develop comprehensive guidelines, require approval before teams proceed. By the time the guidelines are published, the teams that needed them have already built something — either by going around the process or by waiting and losing competitive position.
Modern architectural thinking takes a different approach. Partner with platform teams to build golden paved pathways for AI adoption. Embed guardrails into platforms rather than processes. Replace approval gates with feedback loops and telemetry. Create clear standards for responsible use while enabling experimentation within safe boundaries.
The principle is consistent: teams only resort to shadow IT when the sanctioned path delivers less value than going around the system. The architecture function’s job is to make the right path the easy path.
The Architect’s Real Calling
None of this means abandoning rigor. The established frameworks — TOGAF, SAFe, Gartner’s guidance — all support this evolution when read carefully rather than applied bureaucratically. TOGAF’s architecture contracts and delegated building blocks. SAFe’s embedded system architects. Gartner’s explicit guidance against ARBs as gatekeeping bodies.
The frameworks already know this. The organizations using them have not caught up.
The architect’s highest calling has never been to create perfect diagrams or enforce rigid standards. It is to shape systems that deliver value and adapt to change — to architect the conditions for teams to succeed, not prescribe the solutions they must build.
Enterprise Architecture as a control function is dead. What replaces it — embedded, federated, focused on enablement — is more powerful and more essential than what came before. The question is not whether your organization needs architectural thinking. It is whether your architecture function has evolved to deliver it in a form that the business can actually use.
