Business Capability — IT definition
What an organization is able to do — independently of how it does it. The foundational pivot of modern enterprise mapping.
A business capability is what an organization is able to do to achieve its goals, independently of how, by whom, or with which tools. A capability describes the what — for example "manage customer relationships", "invoice a service", "hire an employee" — while a process describes the how.
It is one of the most fundamental and widely used concepts in modern enterprise architecture. Capabilities form the pivot between strategy and IT: they are stable over time (the capability "sell" doesn't change even if channels evolve) while processes, applications, and infrastructure constantly evolve.
Capability vs process vs function
Three concepts often confused:
- •Capability: what — what the organization can do. Stable. e.g. "order management".
- •Process: how — the sequence of activities. Evolving. e.g. "omnichannel order intake process".
- •Function: who — an organizational unit. e.g. "sales department".
A capability can be realized by several processes, supported by several applications, and owned by several functions.
Business capability map
A business capability map is a hierarchical view of all the capabilities of an organization, typically over 3 to 4 levels:
- •Level 1: 8 to 15 macro capabilities (e.g. Sell, Deliver, Manage HR, Steer, Innovate).
- •Level 2: sub-capabilities by domain (e.g. under Sell: Manage leads, Manage opportunities, Manage contracts).
- •Level 3-4: precise operational capabilities.
The map is then enriched by cross-referencing:
- •[Application portfolio](/en/glossary/application-portfolio): which applications support which capabilities?
- •Costs: what does each capability cost, IT and business combined?
- •Criticality: which capabilities are strategic, which are commodity?
- •Maturity: which capabilities are under-invested, which to optimize?
Capability-Based Planning
Capability-Based Planning (CBP) is the practice of steering IT strategy from capabilities rather than projects:
- Identify strategic capabilities where the company wants to differentiate.
- Assess the gap between current and target maturity.
- Prioritize investments based on business impact.
- Align the application portfolio with the capabilities.
It is the opposite of historic project-driven logic, which started from business requests with no overall view.
Standards and frameworks
- •APQC Process Classification Framework (PCF): industry-specific capability reference (banking, retail, healthcare, etc.); a classic starting point.
- •BIZBOK: Business Architecture Body of Knowledge (Business Architecture Guild).
- •[TOGAF](/en/glossary/togaf): integrates capabilities in the Business Architecture (TOGAF 9.2 and 10).
- •[ArchiMate](/en/glossary/archimate): Capability element in the Strategy Layer.
Why capabilities are strategic
- •Time stability: capabilities evolve slowly, unlike applications. A map holds for 3 to 5 years.
- •C-suite-IT shared language: an executive understands a capability; they don't always understand an application architecture.
- •Rationalization pivot: "which applications support the same capability?" is the key question of application rationalization.
- •Investment steering: prioritize by capability rather than by project.
Business capability and application mapping
A capability map without application mapping is a beautiful abstract drawing. An application map without capabilities is an unreadable list. The two feed each other: Kabeen automatically cross-references applications, usage, and cost with the business capabilities of the company to enable strategic arbitration.
Frequently asked questions
What is a business capability?
+
A business capability is what an organization is able to do to achieve its goals, independently of how it does it. For example: "manage customer relationships", "invoice a service", "hire an employee". The capability describes the what; the process describes the how; the function describes the who.
What is the difference between capability, process, and function?
+
A capability is the what (manage orders). A process is the how (the activity sequence to process an omnichannel order). A function is the who (the sales department). Capabilities are stable over time; processes and functions evolve. A capability can be realized by several processes, supported by several applications, and owned by several functions.
What is a business capability map used for?
+
A capability map provides a hierarchical view (3 to 4 levels) of everything the organization is able to do. Cross-referenced with the application portfolio, costs, criticality, and maturity, it enables arbitration of IT investments by capability rather than by project, detection of redundancies (several apps for the same capability), and alignment of strategy with the IT estate.
How do you get started with a capability map?
+
Four steps: (1) start from an existing industry reference (APQC PCF, BIZBOK) rather than reinventing everything, (2) build level 1 (8 to 15 macro capabilities) in half a day with the executive committee, (3) drill down to levels 2-3 with business directions, (4) cross-reference with the application portfolio to quickly spot over-instrumented and under-instrumented capabilities. The classic mistake is aiming for level 4 from the start.
All terms
5R Method
A strategy used during application rationalization to determine the best approach for managing applications.
8R Method
An extended version of the 5R method used in application portfolio management and migration strategies.
Application
A computer program or set of programs designed to automate a business process or deliver value to end users.
Architecture
Refers to the structure and behavior of IT systems, processes, and infrastructure within an organization.
Need help mapping your IT landscape?
Kabeen helps you inventory, analyze and optimize your application portfolio.