A Capability Landscape is a holistic model for mapping and prioritizing business capabilities across organizational units. It supports strategic decisions, investment prioritization and alignment between product and IT roadmaps. The visualization creates transparency about responsibilities, dependencies and maturity, and informs architecture and governance c…
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.
A capability landscape is a structured overview of an organization’s business capabilities. It places capabilities into a strategic view so products, IT, and investments can be aligned to shared goals.
The term comes from enterprise- and business-architecture practice, where organizations make their business capabilities visible separately from org charts and process maps. It addresses a recurring governance problem: strategy, product planning, and IT investments must be aligned across units against the same set of capabilities. TOGAF and ArchiMate provide the professional framing for that view.
Think of a map rather than a flowchart: each area stands for a capability, grouping shows business domains or product areas, and colors or levels indicate maturity or priority. Links expose dependencies. The map does not describe how work moves step by step; it shows where the organization is strong, where gaps exist, and where effort overlaps.
A capability describes what the organization must be able to do to create value.
Capabilities are arranged by business area, platform, or product line so comparisons become possible.
Capabilities are weighted by strategic importance, risk, or investment need.
Accountability for each capability makes it clear who carries maintenance, development, and decisions.
The view shows which capabilities are mature, where gaps exist, and how areas affect one another.
The landscape is useful for target-state work, portfolio and platform decisions, M&A, target architecture, and roadmap alignment. Its value depends on a stable capability taxonomy, the right level of granularity, and clear ownership; overly detailed models become hard to read. It does not replace process models or org charts, but complements them.
Where this building block is located in the topic model.
No structure path available.
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.