The capability map is not the strategy

Capability maps are having a moment, and deservedly so — they give organizations a stable, technology-independent view of what they do. But a quiet confusion has followed them into the boardroom: the belief that completing the map completes the strategy.

It does not. A capability map is descriptive. It tells you what the organization can do today, with remarkable clarity. Strategy is prescriptive. It decides which of those capabilities must become excellent, which can remain adequate, and which should be exited entirely. The map cannot make those choices, because they depend on intent, not inventory.

The map earns its keep when it is used as the terrain over which strategy is argued — when leaders point at a capability and say: this one wins us the next five years, and this one we will deliberately underinvest in. Without that argument, the map is wallpaper.

Describe the present with the map. Decide the future with the strategy. Confuse the two, and you will have an excellent picture of an organization that is going nowhere in particular.