Catalog
concept#Architecture#Product#Delivery#Governance

Business Capabilities

A concept for describing stable, business-facing capabilities of an organization to support strategy, prioritization and architecture.

Business capabilities are stable, abstract abilities of an organization that describe what the business can do from a functional perspective.
Established
Medium

Classification

  • Medium
  • Organizational
  • Organizational
  • Intermediate

Technical context

Enterprise architecture tools (e.g. Archi)Product and portfolio management systemsProcess management and BPM platforms

Principles & goals

Capabilities are stable and independent of implementations.Business capabilities connect strategy with architecture and execution.Capability models should provide governance- and investment-ready artifacts.
Discovery
Enterprise, Domain

Use cases & scenarios

Compromises

  • Capabilities are modeled with political bias and not evaluated objectively.
  • Lack of linkage to metrics leads to non-committal roadmaps.
  • Tight coupling to existing org units prevents organizational change.
  • Start at a coarse level and refine iteratively (avoid bottom-up explosion).
  • Establish clear ownership per capability.
  • Ensure linkage to metrics and financial figures.

I/O & resources

  • Strategy documents and objectives
  • Existing process and system landscape
  • Stakeholder interviews and business requirements
  • Capability map with structure and categorization
  • Prioritized roadmap and governance model
  • Derivations for architecture, product and organizational decisions

Description

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 investment choices.

✔

  • Clear prioritization of investments along business capabilities.
  • Better alignment of product, technology and organizational decisions.
  • A reusable view of capabilities increases transparency and governability.

✖

  • Creating and maintaining capability maps is effort-intensive.
  • Over-abstraction can obscure concrete implementation decisions.
  • Success depends on discipline and governance within the organization.

  • Capability score

    Assessment of a capability regarding maturity, value contribution and cost.

  • Investment share per capability

    Percentage of budget allocated to a capability.

  • Time-to-value for capability initiatives

    Time until measurable business value after implementing a capability initiative.

Capability map of an insurer

Detailed mapping of core capabilities to prioritize digitalization initiatives.

E-commerce transformation program

Use of capability models to align product, technology and organizational activities.

M&A integration in the financial sector

Capability-based consolidation to reduce redundancies and harmonize processes.

1

Stakeholder workshop to capture strategic goals and expectations.

2

Create initial capability model and validate with business units.

3

Define governance and metrics, assign responsibilities.

4

Integrate capability map into tools and establish regular maintenance processes.

⚠️ Technical debt & bottlenecks

  • Insufficient documentation of capability-to-system mappings.
  • Stale capability definitions remain in use.
  • Lack of automation for maintaining large capability models.
Lack of data to assess capabilitiesUnclear governance and responsibilitiesTechnical dependencies between legacy systems
  • Reworking capabilities to justify existing budgets.
  • Creating capability map once and never updating it.
  • Mapping capabilities exclusively to team structures.
  • Confusing capability with process or system.
  • Lack of alignment between product and architecture owners.
  • Defining non-measurable goals for capability initiatives.
Experience in enterprise architecture and modelingBusiness analysis and facilitation skillsKnowledge of strategy methods and portfolio management
Strategic objectivesReuse and modularityOrganizational and product structure
  • • Limited resources for analysis and maintenance
  • • Organizational silos hinder consolidation
  • • Regulatory requirements in certain industries