Business Capability Analysis · Business Analysis Notes

What it is#

A business capability is something the business can do to achieve its goals, such as “manage customer bookings” or “procure spare parts”. Capabilities describe the what, not the how: one capability may be delivered by several processes, teams and systems, and those can change while the capability stays the same. That stability is what makes capabilities a useful frame for strategy.

According to the BABOK® Guide, as summarized in the Watermark study tables, the technique works with these elements:

Capabilities themselves, and how they are used to create value.
Performance expectations: how well each capability needs to perform to support the strategy, compared with how well it performs today.
A risk model: the risks to the business if a capability is weak or fails.
Strategic planning: linking capabilities to the goals and objectives of the enterprise.
Capability maps: visual, usually hierarchical, maps of all capabilities, often colored to show gaps.

The output gives stakeholders a shared understanding of the enterprise, aligns initiatives with strategy, and acts as a filter for scoping and prioritizing projects.

When to use it#

When analyzing the current state and defining the future state, to find and prioritize capability gaps by value and risk.
When defining a change strategy and choosing which initiatives to fund.
When specifying requirements at a high level, to represent what the enterprise must be able to do.
When assessing whether the enterprise can offer a new product or service.

When not to use it, or what to add: the technique needs organizational agreement to collaborate, input from many stakeholders and broad cross-functional work to set its scope; it cannot be built in isolation by one analyst. For a single team’s workflow, Process Modelling is more direct. To break one function into parts without a strategic assessment, use Functional Decomposition.

How to do it#

Set the scope. Decide whether you are mapping the whole enterprise, one business unit, or one value stream.
List capabilities. Name each as a noun phrase or verb-plus-noun that describes an outcome (“Parts Procurement”, “Customer Communication”). Avoid names of departments, systems or process steps.
Organize them into a map. Group top-level capabilities and break each into a second level, rarely more than three levels. Check that each capability appears once.
Assess each capability. For each, rate: strategic value (how much it matters to the strategy), current performance against expectations, and risk if it underperforms. Use a simple scale agreed with stakeholders.
Show the gaps. Color the map (a “heat map”) to highlight capabilities with high value and low performance, or high risk.
Link to strategy and initiatives. Trace objectives to the capabilities they depend on, and initiatives to the capabilities they improve. Capabilities with gaps but no initiative, or initiatives touching no important capability, are both warning signs.
Use the map to scope. Agree which capability gaps the current change will address, and record the rest for later.
Maintain it. Update assessments as the strategy changes; keep the capability list itself stable.

Example#

A simple two-level capability map for The Workshop (a fictional chain of 12 bike-repair shops), assessed against its strategy of “reliable and transparent repairs”:

Capability	Sub-capability	Strategic value	Current performance	Gap
Customer Management	Booking	High	Low (phone only)	Large
Customer Management	Customer Communication	High	Low (status by phone on request)	Large
Repair Service	Diagnosis	High	High	None
Repair Service	Repair Execution	High	High	None
Repair Service	Repair Status Tracking	High	Low (paper job cards)	Large
Parts Management	Parts Procurement	Medium	Low (each shop emails the supplier)	Medium
Parts Management	Inventory Management	Medium	Medium	Small
Workforce Management	Scheduling	Medium	Medium	Small
Finance	Invoicing and Payments	Medium	High	None

The map makes the focus obvious: the first initiative should address Booking, Customer Communication and Repair Status Tracking; Parts Procurement follows. Diagnosis and repair work, the core of the business, do not need system change now, which helps keep the scope tight.

Common mistakes#

Capabilities named after departments or systems → name what the business does, so the map survives reorganizations and system changes.
Mixing capabilities and process steps → “Check bike in” is a step; “Customer Intake” is a capability.
Too much detail → two or three levels are enough for strategic decisions.
A map without assessment → a capability list alone is a picture; value, performance and risk ratings make it a decision tool.
Built by the analyst alone → involve stakeholders from across the business; the map needs their agreement to be used.
Redrawing the map for every initiative → keep one shared map and update the assessments.

Checklist#

The scope of the map is agreed.
Capabilities describe outcomes, not departments, systems or steps.
Each capability appears once in a hierarchy of two or three levels.
Value, performance and risk are rated on an agreed scale.
Gaps are visible at a glance.
Objectives and initiatives are linked to capabilities.
The map was reviewed with stakeholders from several functions.
An owner and an update rhythm are set.

Sources and further reading#

IIBA. A Guide to the Business Analysis Body of Knowledge (BABOK® Guide), version 3. International Institute of Business Analysis, 2015. Technique 10.6 “Business Capability Analysis”.
Watermark Learning. BABOK v3 Study Tables. 2016. (study aid for the BABOK Guide): summary of technique 10.6, its elements, strengths, limitations and usage.