Business Capability Modeling
Building a capability map, levels and heat maps, linking capabilities to applications and investment, and avoiding the common mistake of mapping processes or org charts.
What a capability is
A business capability is what the business does (or can do) to achieve its outcomes, independent of how (process), who (organization) or with what (systems). Examples: "Manage Customer Identity", "Price Products", "Fulfil Orders", "Manage Claims". Capabilities are stable over time; processes and systems change.
Building a capability map
- Start from strategy and value streams; use industry reference models (BIAN for banking, TM Forum for telecom, APQC Process Classification Framework as inspiration).
- Level 1: 8–15 top-level capabilities (e.g. Customer Management, Product Management, Sales, Fulfilment, Finance, HR, Risk).
- Level 2/3: decompose to the level where investment decisions are made.
- Validate with business leaders; use their language.
- Assess each capability: strategic importance, current maturity/performance, pain, cost.
flowchart TB
subgraph Customer
C1[Customer onboarding]:::red
C2[Customer service]:::amber
C3[Loyalty management]:::green
end
subgraph Commerce
P1[Product catalog]:::green
P2[Pricing & promotions]:::red
P3[Order management]:::amber
end
subgraph Operations
O1[Inventory management]:::amber
O2[Fulfilment & delivery]:::green
end
classDef red fill:#7f1d1d,color:#fff,stroke:#ef4444;
classDef amber fill:#78350f,color:#fff,stroke:#f59e0b;
classDef green fill:#14532d,color:#fff,stroke:#22c55e;Heat map: red = strategically important and underperforming (invest), amber = improve, green = adequate.
Uses
- Investment prioritization (fund red, important capabilities).
- Application rationalization (which apps support which capability; duplicates).
- M&A integration planning.
- Defining domain boundaries for microservices/DDD (capabilities often map to bounded contexts).
- Organizing product teams around stable business capabilities.
Common mistakes
- Mapping processes ("Receive invoice → Approve invoice") instead of capabilities.
- Mirroring the org chart (reorganizations make the map obsolete).
- Too detailed too early; the map is never finished.
- No link to decisions: a pretty poster that nobody uses.
Interview questions and answers
How would you use a capability map to prioritize a 50-project portfolio?
Map each project to the capabilities it improves, overlay capability importance and maturity, and prioritize projects that improve important, underperforming capabilities; flag projects duplicating investment in the same capability or investing in non-strategic ones.
Capability vs process?
A capability is a stable ability (what); a process is a sequence of activities (how) that uses capabilities. "Manage Claims" is a capability; "first notice of loss to settlement" is a process/value stream using several capabilities.