Capabilities Inventory and Attributes

The Capabilities Inventory governs every Capability the enterprise performs, intends to perform, or has explicitly decided to exit. A Capability qualifies for an entry when it represents a distinct, named, outcome-oriented area of organizational ability that can be assessed, owned, and invested in independently of adjacent Capabilities. Every entry is a Noun Instance of the Capability Noun Type — a unique Capability with its own Semantic ID, its own position in the hierarchy, its own owner, its own service organization, and its own maturity and investment profile.

A Capability is explicitly not a process, application, technology, organizational unit, or job role. Processes describe how work is done — the sequenced activities that operationalize a Capability. Applications support Capabilities but are not Capabilities themselves. Technologies enable Capabilities but do not define them. Organizational units own and perform Capabilities but are not themselves Capabilities. Job roles are filled by individuals who contribute to Capabilities but are not Capabilities. When in doubt: if it can be assessed for maturity, has an investment direction, and remains stable through organizational restructuring, it is a Capability.

The Capabilities Inventory is organized as a hierarchy rooted at the enterprise itself. The recommended baseline is the three-branch top-level decomposition described in the Overview: Industry-Specific Capabilities, Core Business Capabilities, and Information Technology (IT) Capabilities — each of which is a Level 1 branch beneath the root. Each Level 1 Capability decomposes into Level 2 children, which decompose further into Levels 3 and 4. The framework recommends Level 4 as the typical leaf depth but imposes no hard limit. Enterprises requiring deeper decomposition into function-level or sub-function-level detail are free to extend further. Whether and how deeply to extend is a modeling decision driven by analytical need, not by an external constraint.