Enterprise Architecture Organization Structure

This editable chart shows one way a large enterprise can organize its architects by layer, with a governance lead and domain architects who sit inside the business units.

Enterprise Architecture Organization Structure

Use this template

Illustrative, editable reporting structure. Adapt roles and lines to your organization.

About this department template

Architecture teams in large groups spend much of their time between other teams. A project in one division proposes a new system, a second division already has something close, and someone has to notice. The enterprise architecture function exists so that someone does.

This chart is an illustrative, role-based example and not a prescribed structure. It describes no real company, and the layers can be cut differently to match how your group talks about its architecture.

It differs from the data governance page because the architects here design how data fits with applications and infrastructure, while governance decides who owns and may use the data. It differs from the transformation page because the architects set the shape of the estate and a transformation office runs the programs that change it.

How an enterprise architecture function is organized

The Chief Enterprise Architect leads seven groups. Four follow the usual layers: Business Architecture Lead, Data Architecture Lead, Application and Integration Architecture Lead and Infrastructure and Cloud Architecture Lead. The other three work across them: Security Architecture Liaison, Architecture Governance Lead and Business Unit Domain Architects.

The layer leads own models and standards. Business Architecture Lead keeps the map of capabilities that the other layers refer to. Application and Integration Architecture Lead owns the patterns for how systems talk to each other, and Infrastructure and Cloud Architecture Lead owns the platform choices underneath. Security Architecture Liaison is a liaison because the security design belongs to the security function, and the architects need a named person who brings it into their reviews.

Architecture Governance Lead runs the review board and keeps the standards and roadmap library, which gives every project one place to ask whether a design fits. Business Unit Domain Architects are the enterprise addition. They sit inside commercial and operations units, report to the chief architect for method and to the unit for priorities, and take the group view into local decisions. A mid-size company usually has a handful of architects who cover several layers each. The guide on splitting a large org chart by function, at /guides/how-to-split-a-large-org-chart-by-function, shows how to draw such a function on its own sheet.

Lead role

  1. Chief Enterprise Architect

    Example top role — Replace this title with whoever owns the group architecture principles and the review route.

  2. Architecture Governance Lead

    Example function lead — Owns the review board, the standards library and the roadmap that projects check against.

  3. Business Unit Domain Architects

    Example function lead — Carry the group view into the units and bring unit needs back into the models.

How to adapt this structure

Each architecture layer has one lead, so a question about integration patterns or cloud platforms goes to a named person and does not circle between project teams.

Governance is separated from design. The people who build the models are not the same people who run the review, which keeps the board predictable for the project teams that submit to it.

Domain architects close the distance between the center and the units. A division gets a local architect who knows its systems and still follows the group method.

Design tradeoffs

Layers give architects a clear specialty.
A single business change crosses every layer, so the leads have to agree on a shared view before a project starts.
Embedded domain architects know the unit well.
They answer to two lines, so their time can be pulled toward local delivery and away from group standards.
A central review board gives projects one route.
If it is slow or too strict, teams look for ways to avoid it, so its scope needs to be agreed and kept small.

What this chart shows

  • Seven groups sit directly under the Chief Enterprise Architect.
  • Security Architecture Liaison has no team beneath it, because the security design lives in another function.
  • Commercial Domain Architects and Operations Domain Architects are the only roles with an explicit business unit focus.
  • Architecture Governance Lead is the only branch drawn with a librarian role, since a standards library is only useful when someone keeps it current.

Related process templates

Frequently asked questions

Should architects report into IT or the business?

Both arrangements exist. This example places the Chief Enterprise Architect at the head of a function and lets domain architects serve the units. Draw the line you use, and note the second reporting relationship in words on the chart.

Where does data governance fit?

Governance sets ownership and rules for data, and Data Architecture Lead designs the structures. See /org-templates/data-governance-organization-structure for the governance side.

What does a mid-size company combine?

Often two or three architects cover business, data and applications together, with one person looking after infrastructure and standards. The chart can be cut back to a lead and two or three roles.

Is this the structure an enterprise must use?

No. It is an illustrative, role-based example. Rename the roles and redraw the lines to match your own organization.

Use this org chart template

Open and edit this enterprise architecture org chart in QueryChart.

Use this template

More in Company Organizational Charts & Structure Examples

This is an illustrative, role-based organizational chart template. It does not describe any particular company, prescribe a required reporting model or establish approval authority. Adapt roles, hierarchy and cross-functional notes to your organization.