Understand what the Capabilities Inventory governs - Capabilities Inventory and Attributes
Understand what the Capabilities Inventory governs
(Chapter 3 of Capabilities Inventory and Attributes)
Executive Summary: Chapter Overview
IF4ITThe Bottom Line
Core Concepts
| Concept | Definition & Strategic Role |
|---|---|
| Governed Capability | Establishes each capability as a Noun Instance with its own identity, owner, hierarchy position, and governance attributes. |
| Not a Process or Application | Prevents teams from confusing what the enterprise must do with how work is currently performed or automated. |
| Hierarchy Depth | Allows enterprises to model capabilities from broad Level 1 branches down to deeper operational detail where needed. |
Quick Q&A
Question: How does this chapter determine whether something belongs in the inventory?
Read More Below
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.
How to cite this page
When referencing this page in academic work, internal standards, or external publications, include the page title, IF4IT as author and publisher (The International Foundation for Information Technology (IF4IT), LLC), the URL, and your access date.
Example (informal web citation):
The International Foundation for Information Technology (IF4IT), LLC. Understand what the Capabilities Inventory governs | Capabilities Inventory and Attributes. https://if4it.org/best-practices/capabilities-inventory-and-attributes/understand-what-the-capabilities-inventory-governs/ (accessed 2026-09-08).
See About Us for content governance and site-wide citation guidance.
Copyright for The International Foundation for Information Technology (IF4IT), LLC: 2008 - Present
Legal Disclaimers