Why do capability maps go stale so fast?
Because they are often born in a workshop, published as a poster or PDF, and disconnected from changing applications, processes, and evidence. Leaders still point at last year’s grid while the landscape has moved. Search language: how to keep capability maps up to date, why our capability model is ignored, living business capability map.
Should capabilities drive applications — or the reverse?
Both. Capabilities give the strategic frame (top-down). Living application and delivery facts must continuously validate and refine that frame (bottom-up). That is the same hybrid logic as top-down vs bottom-up modelling.
How do living facts update a capability map?
- Capture applications, processes, and evidence via incremental modelling.
- Propose capability links, gaps, and maturity shifts against the metamodel.
- Architects curate — accept, reject, enrich.
- Roadmaps, Ask, and generated docs consume the updated map so decisions track reality.
Where does this sit in the continuum?
Capabilities sit in the strategy/EA quadrant of the IT Knowledge Continuum. If they do not absorb solution and delivery learning, the continuum breaks and every programme rediscovers “what we are capable of.”
How does DecisionPen solve this?
DecisionPen keeps capability maps as living decision infrastructure — continuously refined by facts, not republished once a year.
- Capabilities in the metamodel — first-class entities linked to applications, processes, and technology — not a detached PowerPoint grid.
- Facts in via incremental modelling — documents, meetings, and portfolio changes propose capability links and shifts; architects curate (incremental modelling).
- How/Why retained — evidence stays with capability and application entities so maturity debates are grounded.
- Consumed by Ask and roadmaps — Enterprise Ask and generated docs use the current map, so stale posters stop being the “official” lie.
Trial one capability domain: load the apps and docs you already have, curate the links, and treat the map as operational — not decorative.
When is DecisionPen not the right tool?
When you only need a one-off Visio capability poster with no living link to systems. DecisionPen is for curated, evolving context — not static diagram drawing.