Common Business Capabilities: A Guide to Enterprise Capability Modeling

Is there a generic list of business capabilities that can serve as a starting point for capability‑mapping work? Yes! Capstera provides several customizable generic capability lists, focused on industry/sector but also usable for cross‑functional domains.

Business capabilities act as a crucial glue that links execution to strategy and provides a blueprint for orchestrating a target operating model; their value in aligning business vision with IT support is evident.

Large, complex organizations can spend months or even years building enterprise‑wide capability models—akin to boiling the ocean or reinventing the wheel—so starting from scratch is often impractical.

Instead, by selectively adding, modifying, and improving a generic model, a comprehensive capability list can accelerate time‑to‑value.

For example, let’s look at the list—Level 1 enterprise business capabilities.

Of course you can argue for a special capability or point to one that is not at Level 1. You might say customer management is part of Operations, making “Operations” the correct Level 1 capability with customer management as a sub‑capability. Shared enterprise functions (e.g., finance, accounting, HR, procurement) could be listed as a Level 1 capability, with all functions placed under a broader scope. If you’re lucky, your industry may lack major legal, risk, and compliance concerns. The key is there is no single path; the approach varies with the relative importance of each function. Using a generic capability list as input or reference allows enterprise architecture teams to design a set of Level 1 capabilities that resonate internally.

Now let’s review the next level of capabilities. Assuming your team has agreed on a set of Level 1 capabilities, the next task is to dive into Level 2.

Level 2 capabilities are foundational because they often reflect specific domains and break them into logical business capabilities. Unlike Level 1, Level 2 goes deeper into domains, and subject‑matter expertise is more dispersed. Therefore, having a customizable generic capability list helps reduce reliance on domain experts while remaining comprehensive and deep.

Human Capital Management Capability Decomposition Example:

Now comes the deep‑dive work: breaking Level 2 capabilities into logical, fundamental building blocks. Whether you need depth to Level 3, 4, or 5 depends on the context, purpose, and use case of the capability model.

Detailed Decomposition of Recruiting and Hiring Capabilities:

What are the pros and cons of using a generic business capability list as input to build an enterprise‑wide capability model?

Using Pre‑Built Customizable Business Capability Models:

Pros:

Value‑realization time: a customizable generic list accelerates and completes capabilities without starting from scratch.

Reference point: a pre‑built list provides a concrete reference, avoiding endless brainstorming.

Opportunity cost: it reduces the time subject‑matter experts spend on capability conceptualization, freeing them for daily work.

Cons:

Not fit for purpose: any generic list differs from a tailor‑made model and may introduce burdens.

Potential lack of consistency and buy‑in: building a capability model collaboratively fosters consistency and stakeholder buy‑in, which a purchased list may lack.

For further resources and community discussion, see the table below (contains promotional links and QR codes).

Source: https://architect.pub/list-common-business-capabilities

Discussion: Knowledge Circle 【Chief Architect Circle】 or WeChat ID 【ca_cto】 or QQ group 【792862318】

Additional rows with community links omitted for brevity

Thank you for following, sharing, liking, and viewing.