Skip to content

Capability-Based Architecture

Definition

Capability-Based Architecture (CBA) is an approach to enterprise design in which distinct business capabilities are identified, offered through well-defined interfaces, and made available as sharable services across multiple business endeavors. Rather than bundling capabilities within functional silos or lines of business, CBA breaks down organizational walls to expose duplicated capabilities for consolidation, achieving economies of scale while maintaining consistency and control.

In the Book

Cummins contrasts two enterprise structures. In the traditional silo model (Figure 1.6), each business division manages all capabilities needed to deliver its end product—creating duplication. The same capabilities (marked with identical letters) appear across multiple divisions, embedded in mainstreamed processes and hidden from view. CBA opens these silos. Figure 1.7 shows the transformed architecture where each capability is a distinct, shareable box. A single "Order processing" or "Receive" capability can now be configured for use by multiple divisions.

The book emphasizes that a capability consists of "knowledge, skills, resources, facilities, and organizational structure to perform certain activities and produce a desired result." A capability unit is the organizational entity managing these capability methods—potentially a parent organization containing multiple sub-units offering different versions of the same capability for different needs. Shared capabilities can be managed for performance, consistency, control, and economies of scale, then reconfigured into new lines of business without reinventing the wheel.

Why It Matters

CBA fundamentally shifts how enterprises think about change. Instead of optimizing within silos and accepting duplication as inevitable, it makes visible what was hidden and enables strategic investment decisions. An improvement to a shared capability can ripple across the entire organization—benefiting all consumers of that service. This is the architectural foundation that allows agile enterprises to reconfigure faster than competitors, because they have mapped and can manipulate their capability assets with precision, not reinvent them repeatedly. It also surfaces where real differentiation should live (in unique capabilities) versus where standardization should be pursued (in commodity capabilities), a distinction silos obscure.