The capability map is the anchor artifact of business architecture: a stable, noun-based model of what an enterprise does — not how, not who. It underpins strategy alignment, investment decisions and operating-model design. This is a BIZBOK-aligned Level-1 model across four tiers; toggle the heat-map to see maturity or investment priority, and select any capability to open its sub-capabilities.
A capability answers “what,” not “how” — it is a stable noun (“Customer Management”), so it doesn’t churn when processes, org charts or systems change. That stability is why it’s the backbone of business architecture: strategy maps to capabilities, initiatives are planned against them, value streams are enabled by them, and a heat-map turns them into an investment conversation. The next artifacts — value streams and the operating model — hang off this one.