certificate.tips
All ArticlesScrum & AgileBusiness Analysis
certificate.tips

Elevate your career with expert-curated certification prep. We provide realistic practice exams and study strategies to help you pass professional exams on your first try.

Study Guides

Scrum GuidesAgile ArticlesCBDA Study GuidesCBAP ResourcesAll Articles

Practice Tests

PSM I Mock ExamPSPO I Mock ExamPSM II Mock ExamPSPO II Mock ExamCBDA Mock Exam

Get in Touch

Support Emailcontact@certificate.tips

© 2026 certificate.tips. All rights reserved.

Built for professional certification excellence.

Privacy PolicyTerms of Service
Back to Articles
Business Analysis
8 min

Business Capability Analysis: BABOK 10.6 for CBAP Candidates

BABOK technique 10.6 for CBAP candidates: what a business capability is, how capability maps and heat maps work, a worked example and the traps the exam sets.

Business Capability Analysis: BABOK 10.6 for CBAP Candidates
Aliaksei Khavanski

Contributor

October 10, 2026

Last Updated

Business capability analysis is BABOK technique 10.6: it describes what an enterprise is able to do, independent of who does it or how, and then assesses each capability for value, performance gaps and risk to decide where change should go. On the Certified Business Analysis Professional (CBAP) exam it belongs to Strategy Analysis (15% of the 120 questions), mainly when the current state and future state are defined.

Last verified: October 2026 (exam facts from iiba.org).

What business capability analysis is

Business capability analysis is a scoping and planning technique built on one idea: a capability is what the business does, not how it does it. The International Institute of Business Analysis (IIBA) summarises its purpose in the BABOK Guide as giving stakeholders a shared understanding of the outcomes they want, showing how an initiative aligns with strategy, and filtering what is in scope and what gets priority.

The BABOK Guide v3 describes the technique through these elements:

ElementWhat it covers
Capabilitiesthe abilities of the enterprise, such as "manage customer claims", described without reference to departments, systems or people
Using capabilitieseach capability exists to produce an outcome; capabilities combine to deliver value to customers
Performance expectationswhere a capability performs below what the strategy needs; these gaps are where change adds value
Risk modelthe risks of changing, or not changing, a capability, typically grouped as business, technology, organizational and market risks
Strategic planningcomparing current and future capabilities to plan the change
Capability mapsa visual, layered view of all capabilities, often coloured to show value, performance or investment

A capability is stable: an insurer has needed to "assess risk" for a hundred years, while the processes, systems and teams behind it have changed many times. That stability is what makes capabilities useful for planning.

Why business capability analysis matters on the CBAP exam

Business capability analysis matters because it is a strategy-only technique that many candidates have never used at work. According to IIBA, the CBAP exam has 120 scenario-based questions in 210 minutes, and Strategy Analysis carries 15% of them. In the BABOK Guide v3 the technique supports tasks such as Analyze Current State (6.1), Define Future State (6.2) and Define Change Strategy (6.4). Our map of all 50 BABOK techniques groups it with the other strategy-only techniques, including the balanced scorecard.

Typical question patterns:

  • Capability or process? "Process invoices" written as steps is a process; "invoice management" as an ability is a capability.
  • Where to invest? The answer is usually the capability with high strategic value and a large performance gap, not the one that performs worst overall.
  • Which technique? If a scenario asks for an organisation-wide view of what the business can do and where it underperforms, business capability analysis beats Functional Decomposition (10.22) or Organizational Modelling (10.32).

How business capability analysis works, step by step

The technique moves from a map, to an assessment, to a decision.

  1. Build the capability map. List level 1 capabilities (for a retailer: customer management, product management, supply chain, sales, finance), then break each into level 2 and, if needed, level 3. Name them as nouns or abilities, never as departments.
  2. Define each capability. One sentence on the outcome it produces and the information it uses.
  3. Assess value. Mark which capabilities differentiate the business and which are routine but necessary.
  4. Assess performance. Compare current performance with what the strategy needs, using measures where they exist.
  5. Assess risk. Note what could go wrong if the capability changes or stays as it is.
  6. Draw the heat map. Colour the map by value and gap, and pick the capabilities to change first.
  7. Link to initiatives. Trace each proposed project to the capabilities it improves; projects that touch no priority capability are candidates to stop.

Steps 3 and 4 produce the current state; steps 6 and 7 feed the future state and the change strategy described in our guide to Strategy Analysis.

Example: a capability heat map for a regional bank

A regional bank wants to grow small-business lending. Its project list has 27 initiatives, and the board asks which ones matter. The business analyst builds a capability map with nine level 1 capabilities and 38 at level 2, then runs workshops with business leaders to assess the lending area:

Capability (level 2)Strategic valueCurrent performanceGapKey risk
Credit risk assessmentdifferentiatingslow, manual, 6 dayslargeregulatory (model approval)
Customer onboardingdifferentiatingpartly digitalmediumtechnology (legacy core)
Collateral managementnecessaryadequatesmalllow
Loan servicingnecessaryadequatesmalllow
Regulatory reportingnecessarygoodnonelow

The heat map shows that credit risk assessment, which differentiates the bank and performs worst, is the priority. Of the 27 initiatives, only four touch it; seven others improve capabilities that are already adequate. The board moves funding to the four, which is the gap-to-initiative logic described in our article on Gap Analysis. The analyst also uses benchmarking to set a realistic target of two days for credit decisions.

What practitioners say

Practitioners agree that the map is easy to start and hard to keep clean.

  • William Ulrich, writing for the BPM Institute, defines a capability as what the business does at its core, and warns against confusing capabilities with processes, value streams or roles. His test: a capability exists whether or not it is automated.
  • Juan Cruz of BOC Group lists the most common mapping mistakes in an August 2025 note: mixing capabilities with processes, too much detail too early, copying the org chart, inconsistent levels and no maintenance after the first version.
  • Marc Lankhorst of Bizzdesign suggests assessing capabilities on strategic importance, maturity and adaptability, and writes in September 2025 that capabilities with high importance and low maturity should be investigated first.
  • In an August 2026 article on Adaptive US, CBAP trainer LN Mishra notes that the analysis can miss intangible factors such as culture or brand reputation and depends on accurate data and sound assumptions.

Common misconceptions

Most exam mistakes come from treating capabilities like something else.

  • "A capability map is an org chart." Capabilities are independent of structure. One department can deliver several capabilities, and one capability can span several departments.
  • "Capabilities are processes." A process describes how work flows step by step; a capability describes what the business can do. Processes and value streams, such as those in value stream mapping, realise capabilities.
  • "Fix the worst-performing capability first." Priority comes from value and gap together. A poorly performing capability with little strategic value may be fine as it is.
  • "The map is an IT artefact." It is a business view. Systems can be mapped to capabilities later, but the capabilities exist without them.
  • "Build the map once." Capabilities are stable, but their performance and value change; the assessment needs regular updates.

Practice Questions

These are original questions written for this article.

Question 1

An executive team wants to know which parts of the business most need investment to support a new growth strategy. They ask for a view that does not depend on the current department structure. Which technique should the business analyst use?

A. Organizational Modelling B. Business Capability Analysis C. Process Modelling D. Stakeholder List, Map, or Personas

Answer: B. Business capability analysis describes what the enterprise can do, independent of structure, and assesses value and performance gaps to target investment. Organizational modelling describes structure, which the team explicitly wants to avoid.

Question 2

Which item is correctly expressed as a business capability?

A. "The finance department approves invoices over $10,000" B. "Receive invoice, check purchase order, approve, pay" C. "Supplier payment management" D. "SAP accounts payable module"

Answer: C. A capability names what the business does, without who (A), how in steps (B) or which system (D).

Question 3

A capability heat map shows four capabilities. Which should normally be addressed first?

A. Low strategic value, large performance gap B. High strategic value, large performance gap C. High strategic value, no performance gap D. Low strategic value, no performance gap

Answer: B. Change adds the most value where a capability matters to the strategy and underperforms. A low-value capability with a gap may be accepted or outsourced.

Related techniques

Business capability analysis connects to several other techniques. Functional Decomposition (10.22) breaks capabilities into finer levels; Organizational Modelling (10.32) shows who delivers them; Process Analysis (10.34) improves the processes that realise them; and Business Model Canvas (10.8) and the balanced scorecard describe and measure the strategy they serve. Root Cause Analysis (10.40) explains why a capability underperforms.

The CBAP simulator is not live yet. For scenario practice on another IIBA exam, try our CBDA practice exam.

FAQ

What is business capability analysis in BABOK?

It is technique 10.6 of the BABOK Guide v3. It describes what the enterprise is able to do, independent of structure and processes, and assesses capabilities for value, performance gaps and risk to focus change where it matters.

What is the difference between a capability and a process?

A capability is what the business can do, such as claims management. A process is how that work is carried out, step by step. Processes change often; capabilities stay stable for years.

What is a capability map?

A capability map is a layered diagram of all the enterprise's capabilities, from a few top-level ones down to more detailed levels. When coloured by value, performance or investment, it becomes a heat map that shows where to act.

Which CBAP knowledge area uses business capability analysis?

Strategy Analysis, worth 15% of the CBAP exam. It supports Analyze Current State, Define Future State and Define Change Strategy, where the analyst identifies gaps and decides which capabilities to change.

Is business capability analysis the same as business architecture?

Not quite. Capability maps are a core tool of business architecture, which also covers value streams, information and organisation. In the BABOK Guide, business capability analysis is one technique the analyst can use within strategy work.

Sources

  • IIBA: Certified Business Analysis Professional (CBAP)
  • IIBA Knowledge Hub: BABOK Guide 10.6 Business Capability Analysis
  • BPM Institute: Defining the Business Capability, A Cheat Sheet
  • BOC Group: Most common mistakes when creating business capability maps
  • Bizzdesign: Improving the Use of Capabilities in Business Architecture
  • Adaptive US: The Ultimate Guide to Business Capability Analysis

Trending Guides

Product Management

Story Mapping: The Big Picture Planning

Read Guide
Leadership

Product Vision, Horizons & Strategy

Read Guide
Scrum

How to Pass PSPO I in 30 Days

Read Guide

Recommended for you

Business Analysis

Transition Requirements in BABOK: Migration, Training, Cutover

Transition requirements are the temporary needs of moving from the current state to the future state. How BABOK v3 classifies them, and how CBAP questions test them.

Business Analysis

Data Dictionary BABOK Technique 10.12: Elements, Example, Reality

What the data dictionary BABOK technique 10.12 covers, primitive vs composite elements, a worked example, how practitioners keep dictionaries current, and CBAP questions.