Loading content
Business capabilities are stable, abstract abilities of an organization that describe what the business can do from a functional perspective. They bridge strategy and execution and enable prioritization, roadmapping and portfolio decisions. Capability models are technology-agnostic and provide a basis for target architectures, organizational design and inves…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
Business capabilities describe the stable business-facing abilities of an organization and show what the business can do, independent of processes, systems, or reporting lines.
The concept emerged in enterprise architecture and capability-based planning practice to separate stable business abilities from changing processes, systems, and organizational forms. It responds to a recurring problem: strategy, funding, and delivery are often discussed in different vocabularies. Capability models provide a shared, technology-agnostic view of the business.
Think of a capability model as a map of the organization. Broad regions stand for major business domains, and individual cells stand for specific capabilities. Each cell can carry maturity, bottlenecks, owners, processes, and solutions. The map stays relatively stable; what usually changes is the implementation and emphasis, not the capability itself.
It acts as a stable planning and communication unit at a higher business level.
Capabilities are identified, named, and brought into a shared view.
A model arranges capabilities thematically or hierarchically so they can be compared.
The business view remains separate from applications, teams, and technical solutions.
Capabilities provide a decision frame for investment, sequencing, and standardization.
Business capabilities are useful in strategy workshops, target architecture work, portfolio and investment decisions, and the shaping of product or domain teams. They are especially helpful when many initiatives must be aligned to the same business language. Limits: the model does not show process steps or system architecture in detail; very fine-grained catalogs quickly become maintenance-heavy and can look more precise than they really are.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.