Capability Landscape
A structured representation of an organization’s business capabilities to align strategy, products, IT and investments.
Classification
- ComplexityMedium
- Impact areaOrganizational
- Decision typeOrganizational
- Organizational maturityIntermediate
Technical context
Principles & goals
Use cases & scenarios
Compromises
- Wrong prioritization leads to misinvestments.
- Too coarse granularity prevents operational usefulness.
- One-sided focus on technology rather than business purpose skews decisions.
- Define clear ownership and metrics for each capability.
- Start with a manageable set of critical capabilities.
- Link capability priorities directly to investment decisions.
I/O & resources
- Strategy and objective documents
- Product and service inventory
- Technology and platform overviews
- Capability map with maturity, ownership and priority
- Recommended investment and roadmap items
- Governance recommendations and role descriptions
Description
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 choices.
✔Benefits
- Improved alignment between strategy, product and IT.
- Better decision basis for investments and roadmaps.
- Increased transparency about dependencies and responsibilities.
✖Limitations
- Requires regular maintenance and alignment, otherwise the representation becomes outdated.
- Can initially create significant coordination effort between business units.
- Not all technical dependencies can be represented purely on a capability basis.
Trade-offs
Metrics
- Number of validated capabilities
Number of capabilities that have been documented and aligned.
- Time-to-value per capability
Time until realized value increase after investing in a capability.
- Ownership coverage
Percentage of capabilities with clearly assigned owner.
Examples & implementations
Telecom provider: product portfolio alignment
A capability landscape was used to identify redundant services and prioritize consolidation projects.
Bank: consolidating compliance capabilities
A bank mapped regulatory capabilities to justify investments in central compliance platforms.
Software vendor: deriving platform strategy
The landscape showed which capabilities could be consolidated on a common platform to shorten time-to-market.
Implementation steps
Kickoff with stakeholders and goal definition
Collect and consolidate existing information
Model the capability map and validate
Integrate into governance and roadmap processes
⚠️ Technical debt & bottlenecks
Technical debt
- Outdated, unmaintained capability definitions
- Incompatible tools hinder automation
- Missing interfaces to CMDB/inventory
Known bottlenecks
Misuse examples
- Using the capability map as a static diagram without governance.
- Defining capabilities too technically and losing strategic relevance.
- Prioritizing solely by short-term cost.
Typical traps
- Confusing capability with process/project.
- Lack of stakeholder commitment leads to incomplete data.
- Excessive detail before the structure is stabilized.
Required skills
Architectural drivers
Constraints
- • Limited resources for collection and maintenance
- • Organizational silos prevent unified view
- • Data protection and compliance constraints