A capability map should answer questions, not decorate walls

Many organisations own a capability map: a diagram of everything the business must be able to do. Most were expensive to produce and are rarely used. A map earns its keep only if it can answer real business questions. Built as connected data rather than a picture, it reveals duplicated spending, gaps and ownership conflicts that drive investment decisions.

Most capability maps are pictures, not tools

A capability map lists what the business does, such as managing customers, pricing, fulfilling orders and handling payments, usually as coloured boxes on one large page. It looks impressive in a strategy pack.

Then someone asks a practical question. Which teams own customer data? How many systems do we pay for that do the same job? Which important capability has no investment at all? The diagram cannot answer. Someone spends a week in spreadsheets and interviews, and the answer is out of date by the next quarter.

A printed city map shows the streets. A city planning system can tell you which neighbourhoods lack schools. The difference is not the drawing. It is whether the underlying information is connected.

Four business questions a useful map must answer

A capability map should be judged by whether it answers four questions quickly.

Who owns each capability? When several teams believe they own the same capability, decisions collide and work is duplicated. When nobody owns it, it is neglected.

Where are we paying twice? Several systems supporting the same capability often means duplicated licences, integration cost and inconsistent data.

What capability has no support? An important capability with no system, team or investment behind it is a strategic gap waiting to surface.

Where is investment concentrated? Spending piled onto a few capabilities while strategic ones are underfunded is a sign that budgets follow history rather than strategy.

Each answer feeds directly into decisions on budgets, vendors, organisation design and transformation priorities.

Build the map as connected data

The practical fix is to hold the map as simple, connected information rather than a drawing. Four lists are enough to start: capabilities, teams, systems and investments, with links between them showing which team owns which capability, which systems support it and where money is spent.

Once those links exist, the four questions become quick lookups instead of research projects. The picture can still be drawn from the data when a diagram is needed. But the value is in the answers.

This also makes the map useful for evaluation. Before an acquisition, an expansion or a major technology investment, the same map shows where capabilities overlap, where gaps lie and what an integration would really involve.

What to do

• Take your current capability map and try to answer the four questions with it. Note which ones it cannot answer.
• Start four simple lists, capabilities, teams, systems and investments, for one business area.
• Use the result in your next budget or vendor decision, and judge the map by whether it helped.

If you need a clear view of what your business can do and where money goes, let's discuss it.