# Enterprise Architecture Maturity Stages

**In short:** Enterprise architecture maturity stages describe how a firm's architecture grows from business silos to standardized technology, optimized core, and business modularity, later extended to a digital ecosystem. Value depends on governance and learning, not stage alone.

## Explanation

A maturity stage model describes the steps a firm passes through as it builds its enterprise architecture. Enterprise architecture is the overall design of a firm's business and IT (see the article Enterprise Architecture).

**The four original stages**

The book names four stages, in this order:

1. Business silos
2. Standardized technology
3. Optimized core
4. Business modularity

Reviewers describe this as a progression where skipping stages is discouraged. In stage 1, firms have only IT solutions and no platforms. A platform is a shared base that many solutions build on. In stage 4, firms reuse their stage 3 platforms to respond quickly to new business opportunities.

**The later five-stage version**

CISR researchers later described a five-stage progression. It does not stop at business modularity. It ends in a digital ecosystem. A 2020 briefing also defines a business component as a unit of accountability for a specified mission. It ties componentization to modular software design.

**How many firms reach each stage**

A 2008 study of about 1,500 firms found that few had reached the later stages. Only 27% had reached stage three, and only 2% were in stage four. The share of firms in stage 3 or 4 rose from 29% in 2007 to 49% in 2011.

**Why maturity alone is not enough**

Business value comes from management practices that spread architectural thinking across the whole enterprise. This is organizational learning. Reaching a later stage does not guarantee value.

Governance also matters. Architecture becomes strategic only when it shapes investment decisions.

**Link to the operating model**

Architecture reflects the integration and standardization needs of the firm's operating model (see the article Operating Model). The journey can be long for large companies.

## Example

A mid-sized retailer runs separate IT solutions for its stores, its web shop, and its warehouse. Nothing is shared. That matches stage 1. The firm then moves to common technology for all three, which is stage 2. Later, it shares platforms across units. When a new sales channel appears, the retailer reuses those platforms instead of building from scratch. That is how stage 4 firms behave.

## Trade-offs

Stage models give a clear picture of progress, but they simplify. Moving up a stage does not guarantee business value. Value also needs organizational learning and governance that links architecture to investment decisions. The path can take long, especially in large companies, and reviewers advise against skipping stages. The two versions of the model differ at the end, so state which one you use.

Stages of enterprise architecture maturity, with the later extension to a digital ecosystem.

```mermaid
flowchart LR
  A[Business silos] --> B[Standardized technology]
  B --> C[Optimized core]
  C --> D[Business modularity]
  D -.later version.-> E[Digital ecosystem]
```

## Checks

- The document states which maturity stage the firm is in today and which model version (four or five stages) it uses.
- The document links the architecture to the operating model's integration and standardization needs.
- The document explains how architecture influences investment decisions.
- The document describes practices that spread architectural thinking across the enterprise.

## Related

- [Enterprise Architecture Maturity Level](https://arc.fuet.ch/concepts/enterprise-architecture/enterprise-architecture-maturity-levels.md)
- [Operating Model](https://arc.fuet.ch/concepts/enterprise-architecture/operating-model.md)
- [Foundation for Execution](https://arc.fuet.ch/concepts/enterprise-architecture/foundation-for-execution.md)
- [Enterprise Architecture](https://arc.fuet.ch/concepts/enterprise-architecture/enterprise-architecture-management.md)
- [Enterprise Architecture (Ross/Weill/Robertson definition)](https://arc.fuet.ch/concepts/enterprise-architecture/enterprise-architecture-ross-weill-robertson-definition.md)
- [Enterprise Architecture Strategy](https://arc.fuet.ch/concepts/enterprise-architecture/enterprise-architecture-strategy.md)
- [Modularity](https://arc.fuet.ch/concepts/principles/modularity.md)
- [Warning Signs of Poor Enterprise Architecture](https://arc.fuet.ch/concepts/enterprise-architecture/warning-signs-of-poor-enterprise-architecture.md)

## Sources

- [MIT expert recaps 30-plus years of enterprise architecture | MIT Sloan](https://mitsloan.mit.edu/ideas-made-to-matter/mit-expert-recaps-30-plus-years-enterprise-architecture) — mitsloan.mit.edu, accessed 2026-11-09
- [Enterprise Architecture Is Not Just for Architects | MIT CISR](https://cisr.mit.edu/publication/2012_0901_ArchitectureLearning_RossQuaadgras) — cisr.mit.edu, accessed 2026-11-09
- [](https://cisr.mit.edu/sites/default/files/2020-02/Enterprise%20Architecture.txt) — cisr.mit.edu, accessed 2026-11-09
- [The Digital Operating Model: Building a Componentized Organization | MIT CISR](https://cisr.mit.edu/publication/2020_0601_BuildingComponentizedOrganization_RossBeathNelson) — cisr.mit.edu, accessed 2026-11-09
- [Notes on Enterprise Architecture as Strategy | Irrational Exuberance](https://lethain.com/notes-on-enterprise-architecture-as-strategy/) — lethain.com, accessed 2026-11-09