Business Capability Analysis: Method, Matrix and Examples
How to assess what an organization can do against what its strategy needs, and turn the result into investment decisions.
By Capstera Business Architecture Staff · Updated
9 min read
Business capability analysis is the assessment of an organization's business capabilities against what its strategy requires: how well each capability performs today, how much it matters, and where the gaps are. It works on the capability map rather than on departments, processes or systems, so the result shows where to invest without being tied to the current org chart. This article covers what capability analysis answers, the six-step method, the importance vs. maturity matrix at the center of it, an illustrative example, and the mistakes that make the results hard to trust.
Most organizations decide where to invest by budget line, department or project proposal. Each of those views is partial. Capability analysis puts every proposal against the same list of things the business must be able to do, which makes it possible to see duplicated investment, gaps nobody owns, and spending on capabilities the strategy no longer depends on.
Key Takeaways
- Business capability analysis assesses each capability on the map for current performance and strategic importance, then compares the two.
- It needs an agreed capability map first. Analysis on a map that mixes capabilities with departments and processes produces results nobody can act on.
- Rate importance and maturity separately, with separate criteria and often separate people, before combining them.
- The output is a short list of priority gaps, not a colored map. Low maturity matters only where importance is high.
- The results feed the heat map leaders read and the capability roadmap that sequences the work.
What Is Business Capability Analysis?
Business capability analysis evaluates what an organization is able to do, capability by capability, against what its strategy needs it to do.
The unit of analysis is the business capability: an ability such as Customer Onboarding, Claims Assessment or Demand Planning, described independently of who performs it, how, or with which systems. Each capability is assessed on a small number of dimensions, most often maturity or performance and strategic importance, sometimes also cost, risk or the health of the applications that support it.
Because capabilities are stable, the analysis can be repeated and compared over time. A reorganization changes who owns a capability, not whether the business needs it, so a gap identified this year can still be tracked next year.
- Where is the organization weak in ways that matter to the strategy?
- Where is it strong, and needs to stay strong?
- Where does spending exceed the value a capability returns?
- Which capabilities are duplicated across business units or regions?
- Which gaps have no initiative, and which initiatives close no gap?
How Do You Perform a Business Capability Analysis?
The six steps below assume a capability map exists. If it does not, building one is step zero.
1. Agree the scope and the decision. Name the decision the analysis supports, such as an annual investment plan, a transformation scope or a merger integration, and the part of the capability map it covers. The decision determines which dimensions are worth assessing.
2. Confirm the capability map. Check that every capability in scope has a name, a one-sentence definition and an owner, and that the map is decomposed to a consistent level, usually Level 2. Ratings attached to vague capabilities cannot be defended later.
3. Define the rating scales. Write criteria for each level before anyone scores anything. A 1 to 5 maturity scale needs a description of what a 2 and a 4 look like in this organization; an importance scale needs to say what makes a capability critical to this strategy.
4. Assess each capability. Collect ratings from the capability owners and from people who depend on the capability, and use operational data where it exists. Rate maturity and importance separately; the people best placed to judge one are often not the people best placed to judge the other.
5. Calibrate and analyze. Review the ratings in a cross-functional session, resolve outliers, and plot the results on the importance vs. maturity matrix. Look for clusters as well as individual scores: a whole domain rated low usually has a structural cause.
6. Turn findings into decisions. Agree the short list of priority gaps, attach existing initiatives to them, and identify gaps with no initiative. Publish the results as a heat map for leaders and hand the prioritized gaps to the capability roadmap.
Step 2, already done
The Sales Management Business Capabilities Map provides 171 defined Level 3 capabilities with KPIs at Level 2, a 40-question readiness assessment and prioritization with your own weights.
Sales Management Business Capabilities Map: AI-Ready Edition · $1,295
The Importance vs. Maturity Matrix
The core of capability analysis is the comparison between how much a capability matters and how well it performs.
Either rating alone misleads. Maturity alone flags weakness everywhere, including in capabilities the strategy does not depend on. Importance alone shows what matters but not whether the organization can deliver it. Plotting each capability on both axes splits the map into four groups that call for different actions.
| Quadrant | Importance | Maturity | Typical action |
|---|---|---|---|
| Invest | High | Low | Fund improvement; these gaps go first on the roadmap |
| Protect | High | High | Maintain, monitor for decline, avoid disruptive change |
| Tolerate or simplify | Low | Low | Accept the gap, standardize, or outsource |
| Review spend | Low | High | Check whether investment exceeds the value returned |
Business Capability Analysis Example
An illustrative example: a regional insurer preparing its annual investment plan.
The insurer's strategy is to grow through brokers while reducing the cost of claims. The business architecture team scopes the analysis to the Level 2 capabilities under Distribution, Underwriting and Claims, writes a five-level maturity scale for each, and asks the strategy office to rate importance against the two strategic goals.
The results put Broker Management and Claims Assessment in the invest quadrant: both are central to the strategy and both rate 2 out of 5. Fraud Detection rates 4 and is important, so it is protected. Direct-to-consumer Marketing rates 2 but matters little to a broker-led strategy, so it is tolerated rather than funded. Document Management rates 4 but is low in importance, and three business lines each run their own version, which makes it a candidate for consolidation.
The investment plan that follows funds two capability improvements, one consolidation and nothing for direct marketing. Two proposed projects that closed no priority gap are deferred. Each decision traces back to a rating and a definition the business agreed to.
Capability Analysis, Assessment and Heat Maps: How They Relate
The three terms are often used interchangeably. They describe different steps of the same work.
A capability assessment is the act of rating capabilities against defined scales. Capability analysis is the wider exercise: choosing the dimensions, running the assessment, comparing the ratings and drawing conclusions. A capability heat map is the usual way of presenting the results, with ratings shown as colors on the capability map. The capability roadmap then sequences the gaps the analysis identified.
Common Mistakes in Business Capability Analysis
Most analyses that leaders do not trust fail for one of a few reasons.
- Analyzing a map that is not a capability map. If the boxes are departments, processes or systems, the ratings describe those, and change with the next reorganization.
- Scoring before defining the scales. Without written criteria, a 3 means different things to different raters, and the calibration session turns into a negotiation.
- Combining importance and maturity too early. A single blended score hides whether a capability is weak, unimportant, or both.
- Treating every red capability as a priority. Low maturity is a problem only where the strategy depends on the capability.
- Stopping at the map. An analysis that does not end in a short list of decisions, with owners, is a report rather than an input to planning.
Frequently Asked Questions
What is business capability analysis?
Business capability analysis is the assessment of an organization's business capabilities against what its strategy requires. Each capability is rated for dimensions such as maturity and strategic importance, and the comparison shows where to invest, what to protect and where spending exceeds value.
What is the difference between capability analysis and capability assessment?
A capability assessment is the rating of capabilities against defined scales. Capability analysis is the whole exercise around it: choosing the dimensions, running the assessment, comparing the results and turning them into decisions.
What dimensions are used in capability analysis?
Maturity or performance and strategic importance are the most common. Cost, risk, the health of supporting applications and the degree of duplication are added when the decision needs them.
How long does a business capability analysis take?
It depends on scope and on whether a capability map already exists. With an agreed map, analyzing one or two domains for a specific decision is a matter of weeks; an enterprise-wide first analysis takes longer.
Who should take part in a capability analysis?
Capability owners and the people who depend on each capability rate maturity. Strategy and executive leaders rate importance. A business architect usually runs the method and the calibration session.
What comes after a capability analysis?
The results are presented as a heat map, and the priority gaps are sequenced on a capability roadmap, with initiatives attached to the gaps they close.
Pro Tips
- Write the maturity scale in the organization's own terms. A level described as "claims are assessed by one team using one set of rules" is easier to rate than "defined and repeatable".
- Keep the raters for importance and maturity separate where possible. Capability owners tend to rate their own capability as important.
- Record the reason behind every rating of 1, 2 or 5. Those are the ratings leaders will challenge.