Capability maps that people actually use

A capability map describes what an organisation does, independent of who does it and which system supports it. Drawn well, it becomes the common language between strategy, finance and IT. Drawn badly, it becomes wallpaper.

Start from decisions, not from completeness

The most common mistake is aiming for a complete map before anyone uses it. Instead, pick one decision that is coming up anyway: next year's budget, an application retirement, a reorganisation. Build only the part of the map that decision needs, and use it in the meeting.

Keep levels honest

Level one should fit on a single page and be recognisable to any manager. Level two is where most of the useful conversations happen. Go to level three only where a decision demands it; detail everywhere is detail nobody maintains.

Attach something people care about

A map becomes useful when each capability carries information: who owns it, how mature it is, what it costs, which applications support it, which initiatives touch it. Heat-mapping one of those attributes is often the moment a leadership team starts to take the map seriously.

Give it a routine

Review the map at a fixed point in the planning cycle, with a named owner for each top-level area. Fifteen minutes per quarter is enough to keep it current, and far cheaper than redrawing it every three years.