← All insightsTHE MÉTIARCH PERSPECTIVE

Understand the estate. Architect its evolution.

Enterprise architecture is not simply documentation. It is an evolving, connected body of knowledge that helps organisations make deliberate decisions about technology and change.

18 articles · 5 themesRead in order, or start with the theme most relevant to you. Every article also stands on its own.
THEME 01 / 05

Architecture Foundations

Understand what architecture knowledge is for

A modern architecture practice begins with a shared understanding of its estate and the business it serves.

Browse this theme →
  1. 1.1An architecture repository should be more than a diagram library
  2. 1.2Business capabilities are a taxonomy, not an organisation chart
  3. 1.3Names change. Architecture identities should not.
THEME 02 / 05

Modelling & Relationships

Model the real world without confusing its layers

Clear distinctions make models useful for analysis rather than merely plausible-looking.

Browse this theme →
  1. 2.1A logical application is not its hosting platform
  2. 2.2Applications, APIs and services: keeping the model clear
  3. 2.3Composition is not dependency: two relationships, two meanings
  4. 2.4An architecture repository is not an ArchiMate diagram
  5. 2.5Directed Dependencies: Asking the Right Impact Question
  6. 2.6Why Architecture Graphs Need Ports and Orthogonal Routing
THEME 03 / 05

Integration & Contracts

Make the connections trustworthy

Interfaces and integrations are first-class architecture concerns with distinct contracts and ownership.

Browse this theme →
  1. 3.1An API URL is not a complete contract
  2. 3.2Who owns the contract? APIs, events and integration records
THEME 04 / 05

Architecture Evolution

Treat change as part of the model

Understand the current estate while allowing parallel, governed proposals to shape what comes next.

Browse this theme →
  1. 4.1Why AS-IS and TO-BE need more than a status field
  2. 4.2Architecture traceability is not project management
THEME 05 / 05

Governance & Reuse

Govern the decisions that endure

Lightweight, testable governance preserves rationale, supports reuse and keeps architecture actionable.

Browse this theme →
  1. 5.1Governance with a small g: capture the decisions that matter
  2. 5.2An architecture decision is useful only while its context survives
  3. 5.3An architecture standard should tell you how to comply
  4. 5.4Architecture patterns: govern the reference, not another copy
  5. 5.5Architecture Traceability Without the Bureaucracy

Read White Paper 02: Progressive Architecture Traceability →

New white paper: Architecture as a Connected Knowledge Graph

Understand Today. Architect Tomorrow.

That is the thread running through our perspectives: make architecture knowledge trustworthy, then use it to guide change with greater clarity.

Browse the complete Insights library →