You have a capability map and four possible overlays. Which do you use, and how do you choose?
Show the full answer Hide the answer
The overlay is chosen by the question being asked
A capability map alone is a taxonomy. It becomes a decision tool only when something is coloured onto it, and the wrong overlay answers a question nobody asked.
Duplication — applications per capability. Use when the question is consolidation or post-merger rationalisation. Produces the most immediate conversation.
Cost — annual run spend per capability. Use when the question is where the money goes. Uncomfortable and effective, particularly combined with duplication.
Maturity — current versus required capability level. Use when the question is strategic investment, and only when the required level has been agreed with the business rather than assumed.
Risk — end-of-life technology, single points of knowledge, compliance exposure. Use when the question is what could hurt us.
Use one at a time
A map with four overlays is unreadable. Prepare several, present one, and have the second ready for the question the first provokes — which is usually cost, following duplication.
The precondition
Every overlay depends on the application-to-capability mapping being right. If a system supports three capabilities and is mapped to one, every overlay is wrong in the same direction. Mark confidence rather than implying precision you do not have.