Model what the enterprise can do

A capability describes an ability, independently of which team performs it or which application happens to support it today. Names, definitions and scope should be stable enough to survive a reorganisation while still being useful for business conversations.

Hierarchy has governance consequences

Parent–child relationships should be explicit, validated and acyclic. Levels can be derived from the hierarchy rather than manually entered, preventing contradictory classifications. A capability without a parent is a root by definition, not because someone typed “Level 1”.

Avoid artificial ownership of business value

A value stream tells a different story from a capability map. Its stages describe the progression of value, while capabilities contribute to those stages. One capability can support several stages without becoming a child of each stage.

Integrate without prescribing the implementation

Capabilities can relate to applications and services that enable them. These links are useful for impact assessments and investment decisions, but they should not confuse capability ownership with technical implementation responsibility.

Practical lesson

Clear taxonomy rules improve consistency and searchability. The model becomes particularly powerful when capability relationships can be explored alongside application dependencies, programme change and supporting technology.

The MétiArch perspective

This article explains design principles and lessons from developing architecture tooling. Examples are illustrative. A described design approach does not, by itself, indicate that a feature is enabled or generally available in a deployed product.

← Explore all insights