Business Capability Map
Definition
Business Capability Map
A business capability map is a single visual view of what an organisation is able to do, drawn independently of who does it or which system supports it. It shows abilities, not activities — which is exactly what makes it stable while processes change.
The distinction from process mapping is the one that matters. A process map shows a sequence of steps in order; a capability map shows a set of abilities with no sequence at all.
That is why capabilities age slowly. An insurer will still need to price risk and settle claims in twenty years, however many times the workflow and the systems behind them are rebuilt.
The map is usually rendered from an underlying capability model and coloured for one conversation — investment, risk or sourcing. The colouring is the point; an uncoloured map is a reference document nobody opens.
It is a communication artefact more than an analytical one. Its value lies in getting a whole leadership team to look at the same page and disagree about the same thing.
Key takeaways
- Capabilities describe what an organisation can do, not how or by whom.
- A capability map is a rendered view; the capability model is the definition behind it.
- Heat colouring against one question is what makes the map a decision tool.
- Capabilities remain stable while processes, systems and org charts change around them.
How it works
Maps are drawn in levels. Level one holds ten to twenty capabilities on a single page. Level two decomposes each into three to eight children — and level three is only built where a decision needs that detail.
Everything must fit on one page at level one. The constraint is deliberate, because a map that requires scrolling stops being usable in the conversations it exists to support.
Attribution is what turns the picture into evidence. Once costs, systems and headcount are tied to capabilities, the colouring stops being an opinion and starts reflecting something measurable.
Two colourings on one page is the practical limit. Importance against maturity works because the eye can read two dimensions at once, while a third turns the map into a puzzle.
| Heat dimension | What is coloured | Decision it supports |
|---|---|---|
| Strategic importance | Contribution to the strategy | Where to invest |
| Current maturity | How well it is performed today | Where to improve |
| Cost | Spend attributed to the capability | Where to reduce |
| Risk | Exposure if it fails | Where to protect |
| Sourcing | Retained or outsourced | What to hand over |
Architecture frameworks supply the conventions. The Open Group’s TOGAF 10th Edition is presented by its publisher as covering “a broad range of use-cases, including agile enterprises and Digital Transformation”, with capability views among its standard products.
Engineering practice reaches the same conclusion by another route. NASA’s systems engineering handbook documents model-based methods adopted “to improve development and delivery of products” across very different programmes.
Examples
Maps earn their keep when a single question is put to the whole organisation at once. The three cases below colour the same map for investment, sourcing and risk respectively.
A retailer colours its map by maturity against strategic importance. The two capabilities that are both critical and weak become the year’s strategic planning priorities.
A bank colours by sourcing position before a programme. Knowing which capabilities are already contracted out shapes the whole digital transformation sequence.
A manufacturer uses the map to scope improvement work. Only once a capability is selected does process mapping begin, which keeps detailed analysis off the areas nobody will fund.
Related terms
The map borders several artefacts that look similar and answer different questions. The entries below separate the visual view from the delivery and analysis around it.
- Architecture outsourcing: the capability that produces and maintains the map.
- Business analyst: the role that decomposes capabilities into workable detail.
- Global capability center (GCC): a delivery location, despite the shared word.
- Workflow outsourcing: handing over the activity, once the map shows it is not core.
FAQ
How does a capability map differ from a capability model?
The model is the defined, levelled taxonomy with descriptions and owners. The map is a visual rendering of that model, usually coloured for one specific question.
How many capabilities belong at level one?
Ten to twenty. Fewer hides real differences between areas, and more turns the page into a list nobody can read at a glance.
Is it the same as a process map?
No. Capabilities have no sequence and no actor. Processes have both, and they change far more often than the capabilities they serve.
Who should build it?
Architecture with business owners, in workshops rather than in isolation. A map built without the business gets corrected rather than used.
How often should it be redrawn?
The structure rarely. The colouring is refreshed for each decision cycle, which is usually annual.
Can it be outsourced?
Facilitation and drafting can be. The judgements about importance and maturity have to come from the people accountable for the work.
Compare architecture and advisory partners in the Outsource Accelerator directory.
Independent
