# Setting Up an Enterprise Architecture Practice: From Slideware to Decisions

How to establish an enterprise architecture function that actually influences decisions: operating model, governance, principles, standards, and portfolio views.

Enterprise architecture has a reputation problem, and in many organizations it is earned. The pattern is familiar: a central team produces current-state diagrams, target-state visions, and standards documents that delivery teams never read; governance becomes a review gate that projects route around; and the architects, starved of real decisions, retreat into ever more detailed models. This guide is about building the other kind of practice — one whose output is decisions, not documents.

## Why EA practices fail

Most failed EA practices fail in one of three ways, each with a recognizable signature.

**The ivory tower.** A central team defines the target architecture without deep involvement from the teams that build and run systems. The models are technically elegant and organizationally irrelevant. The signature: architecture documents with no readers and no decisions traceable to them.

**Documentation without decisions.** The practice measures itself by artifacts produced — diagrams completed, standards published, reviews held — rather than by decisions influenced. The signature: a portfolio of models that nobody consults when a real choice is on the table.

**Governance as gatekeeping.** Architecture review becomes a stage-gate that projects must pass, staffed by people with veto power and no delivery accountability. Teams respond rationally: they present late, present selectively, and design around the gate. The signature: review meetings that projects dread, attend minimally, and forget immediately.

All three failures share a root cause: the practice optimized for its own artifacts instead of for the organization's decisions. Define the practice by the decisions it exists to improve — build-vs-buy, platform selection, integration approach, technology standardization, modernization sequencing — and judge every artifact by whether it makes one of those decisions better, faster, or less risky.

## The operating model: federated beats centralized

An EA practice needs a home, but "home" does not mean a large central team. Three operating models dominate, and the choice should match the organization's size and delivery culture.

**Centralized.** One architecture team owns standards, reviews, and portfolio views. Works in organizations with strong central governance and uniform technology — but scales poorly and drifts toward the ivory tower as the central team grows distant from delivery.

**Federated.** A small central practice sets principles, maintains portfolio views, and runs lightweight governance; architects are embedded in delivery teams and carry the architecture context where decisions happen. This is the model that works for most mid-sized and large organizations: central coherence without central bottlenecks.

**Embedded / decentralized.** No central practice; architecture is a capability each team carries. Works in genuinely autonomous product organizations, but usually fails to produce portfolio-level coherence — nobody watches for duplication or diverging technology choices until the bill arrives.

The practical recommendation for most organizations: **federated**. A central practice of two to five people paired with architects embedded in the major delivery areas. The embedded architects do the real work — shaping designs, writing ADRs, escalating genuine conflicts — and the central practice keeps the portfolio view, the principles, and the governance light. Centralized practices should be suspicious of their own size: if the central team grows while its decision influence does not, it is building slideware.

## Governance that helps: principles over bureaucracy

Architecture governance exists to make good decisions easier, not to add a veto. The practices that get this right share a design: **lightweight, early, and advisory by default**.

**A lightweight review board.** A small group — the lead architect, security architecture, data architecture, and rotating representation from delivery — that meets regularly and briefly. Projects engage it early, when options are still open, not at a stage-gate when the design is already committed. The board's output is recorded advice and, rarely, a binding decision on genuinely cross-cutting matters.

**Principles over rules.** Governance works when anchored in a small set of architecture principles — ten at most — that teams can apply themselves. "Prefer managed services over self-hosted infrastructure," "APIs are the integration default; point-to-point data sharing requires an exception," "customer data stays in-region." Principles are decision aids; bureaucracy is decision replacement. The board exists for the cases the principles do not resolve.

**Exception handling, not exception prevention.** Standards will be violated for good reasons. A healthy practice has an explicit exception process: document the deviation, its rationale, its review date, and who accepted the risk. Exceptions recorded and time-boxed are governance working; exceptions hidden from the board are governance failing. A standard that accumulates permanent exceptions is a standard that should be revised.

**Engage upstream.** The highest-leverage governance moment is before the project is funded, when the solution approach is being chosen. Practices that only review designs after funding are reviewing sunk costs. Get architecture input into the intake or business-case stage — even a one-page architecture note on the proposal.

## Architecture principles and standards that get used

Principles and standards are the practice's most portable product — but only if they are written to be used. The failure mode is a 40-page standards document that reads like legislation.

**Principles: few, opinionated, memorable.** Good principles state a preference and its rationale in two sentences. "We standardize on a small set of integration patterns because bespoke integrations are the dominant source of production incidents and modernization cost." Each principle should name what it costs: standardization costs teams some autonomy, managed services cost some control. Principles that pretend there are no trade-offs are not believed. Review the principles annually; retire the ones that no longer describe how the organization actually decides.

**Standards: the paved road, not the fence.** Technology standards should describe the default path — the approved platforms, patterns, and components that come with organizational support. Teams follow standards when the standard path is genuinely easier than going around it: pre-approved infrastructure, reference implementations, security review fast-tracks. If the standard path is harder than the exception path, the standards document is fiction. (Our [platform engineering guide](/guides/platform-engineering-paved-roads/) describes how to make the default path the easy one.)

**Reference architectures for the recurring decisions.** For the choices the organization makes repeatedly — how a new service is built and deployed, how systems integrate, how data products are published — maintain reference architectures: opinionated, current, and short. A reference architecture that is two years out of date is worse than none. Assign ownership and a refresh cadence to each one.

## ADRs as the decision record

The single highest-value artifact an EA practice can maintain is the **Architecture Decision Record (ADR)**: a short document capturing one significant decision — its context, the options considered, the choice made, and the consequences accepted. ADRs are the practice's memory. They answer the question every organization eventually asks: "why did we build it this way?"

The practice's role is to make ADRs a habit, not to write them all. Establish the expectation that significant decisions get recorded — platform commitments, integration approaches, data modeling choices, build-vs-buy calls — keep the format light, and keep the collection searchable and owned. Decisions that affect the portfolio should be visible to the practice; routine team-level decisions stay with the team. Our [ADR guide](/guides/architecture-decision-records-explained/) covers the format, the writing discipline, and the common failure modes — start there before designing your own template.

The governance payoff: when the review board's advice is captured as ADRs, governance produces a durable record instead of unread meeting minutes. When exceptions to standards are captured as ADRs, the exception list maintains itself. The ADR collection becomes the organization's architectural memory — which is what the ivory-tower practice was trying to build with its diagrams, except this version gets read.

## Portfolio and capability views: what the business actually needs

Executives do not need architecture diagrams. They need answers to portfolio questions: where is our technology spend going, where is the risk concentrated, what is duplicated, what should we stop doing, and what must change to support the strategy. The practice earns its budget by answering these.

**The application portfolio view.** Every significant application or system, with its business owner, technology stack, hosting, data classification, lifecycle state (invest, maintain, contain, retire), and known risks. Without it, modernization planning is guesswork. (See our [legacy modernization playbook](/guides/legacy-modernization-playbook/) for how the portfolio view drives sequencing.)

**The capability view.** What the business can do (customer onboarding, billing, fulfillment, reporting), mapped to the systems that enable each capability. Capability mapping reveals what the application list hides: three systems doing fragments of the same capability, critical capabilities supported by a single unmaintained application, strategic capabilities with no investment planned. This is the view the business side actually recognizes itself in.

**The technology lifecycle view.** Which platforms, frameworks, and infrastructure versions are current, aging, or end-of-life across the portfolio — and the remediation timeline. This turns the abstract risk of "technical debt" into a dated, costed list.

**The data view.** The critical data domains, where they live, who owns them, and how they flow between systems. Data architecture is increasingly the binding constraint on AI and analytics ambitions; our [data platform strategy guide](/guides/data-platform-strategy-guide/) covers the domain in depth. If the practice has no data architecture voice, the portfolio's data flows stay invisible and every analytics project rediscovers the same integration mess.

Keep these views current enough to be trusted and simple enough to be maintained. A portfolio view updated annually with discipline beats a real-time dashboard that nobody owns. Present them in business language: "three billing systems supporting one capability, $X in combined run cost, consolidation saves $Y" moves decisions; "application rationalization opportunity" does not.

## EA's relationship with security, data, and platform teams

EA does not own security, data, or platforms — but it cannot do its job without them. The relationship design matters more than the org chart.

**Security architecture.** The closest partnership. Security sets non-negotiable constraints (identity, encryption, network segmentation, incident response); EA sets the patterns within which those constraints are met. The two practices should share the review board and the reference architectures, and never give a delivery team contradictory guidance. Contradictory guidance is how teams learn to ignore both.

**Data architecture.** Often the weakest link in EA practices, and increasingly the most important as AI initiatives demand governed, discoverable data. Ensure data architecture is represented in governance and in the portfolio views.

**Platform engineering.** The platform team builds the paved road; EA defines where the road goes. EA's standards become platform capabilities, and the platform team's adoption metrics become EA's evidence that standards are actually used. When EA specifies a standard the platform team has not built, the standard is a wish; when the platform team builds capabilities EA has not standardized, adoption fragments. Plan them together.

The general rule: EA is a coordinating function, not an owning function. Its authority comes from the quality of its portfolio views and the usefulness of its guidance, not from headcount or veto power. Practices that try to own what the specialist teams own end up owning nothing.

## Measuring EA's value

"You can't measure architecture" is the excuse of practices that do not want to be measured. EA's value shows up in decision quality and organizational leverage, and both leave traces.

**Decision velocity.** How long it takes a team to get an architecture decision made — from question to recorded ADR. A practice with current reference architectures and clear principles should be measurably faster than one that routes everything through a board. Slow decisions are a cost.

**Reuse.** How often teams build on the standard platforms and patterns versus inventing their own. Every integration built on the standard pattern instead of bespoke is avoided future cost. Platform adoption metrics are EA metrics.

**Risk reduction.** Technology risks retired or mitigated through the practice's work: end-of-life platforms replaced on schedule, single points of failure addressed, shadow systems brought into the portfolio. The lifecycle view makes this countable.

**Duplication eliminated.** Capabilities supported by multiple overlapping systems, consolidated or scheduled for consolidation, with the run-cost savings attached. This is the number executives remember.

**Governance load.** Time teams spend in architecture governance per project, trending down as principles and reference architectures do more of the work. Governance that gets lighter over time is succeeding; governance that stays heavy is a tax.

Report these quarterly, in plain language, to whoever funds the practice. An EA practice that cannot show its value in these terms will lose its budget to something that can.

## Staffing the practice

A few principles for building the team.

**Hire for judgment, not for modeling.** The job is making and recording hard trade-offs under uncertainty, usually with incomplete information and real deadlines. Look for people who have built and operated systems, who can say "it depends" and then say what it depends on, and who can disagree with a delivery team without becoming its enemy. Production scars beat framework certifications.

**Keep the central team small.** Two to five people for most organizations: a lead architect with real authority, plus coverage across the domains that matter (applications, data, infrastructure/security). Beyond that, grow through the federated model — embedded architects in the delivery areas — rather than central headcount.

**Give the lead architect a real mandate.** The practice needs executive sponsorship that backs its decisions when they are unpopular — standardizing platforms, retiring beloved systems, saying no to precedent-setting exceptions. A lead architect with a title but no backing is a facilitator of other people's decisions, which is a different job.

**Rotate through delivery.** Architects who have not shipped anything in years lose credibility with the people who ship daily. Central practice members should periodically work inside a delivery team. Architecture practiced at a distance from building is theory.

## Getting started: the first 90 days

**Days 1–30: listen and inventory.** Meet every delivery lead and understand what decisions are actually pending — the practice's first value comes from helping with live decisions, not from publishing a charter. Start the application inventory; even an incomplete list, honestly marked, beats no list. Draft five to seven architecture principles and test them against real past decisions: would they have changed anything?

**Days 31–60: establish the rhythms.** Stand up the lightweight review board and run it on real, early-stage proposals. Start the ADR habit on the decisions the board touches. Publish the principles. Build the first cut of the portfolio view and the technology lifecycle list — dated, costed, honest about gaps.

**Days 61–90: show value.** Use the portfolio view to identify one consolidation or retirement opportunity with a real number attached. Publish one reference architecture for the organization's most repeated decision. Report the first value metrics. By day 90, the practice should be known for three things: it helps teams decide faster, its portfolio view tells the truth, and its governance is light enough that teams engage early.

An EA practice is not a modeling function. It is a decision function with a memory. Build it around the decisions, keep the memory in ADRs and portfolio views, govern lightly and early, and measure whether any of it changed what got built.
