Enterprise Architecture · 12 October 2026 · 7 min
Business capability mapping: building a modernisation roadmap the board will fund
How to link applications, data and cost to business capabilities so modernisation investment is prioritised by value, not by noise.
Key takeaways
- Map applications to capabilities before deciding what to migrate or rebuild.
- Score each capability on strategic value and technical health.
- Fund modernisation in value-based waves with clear exit criteria.
Most modernisation programmes stall because they start with technology inventories rather than business outcomes. Capability mapping fixes that by describing what the business does, independent of how it is done today.
Build a level-1 and level-2 capability map with business owners, then link every application, dataset and integration to it. Overlaps and gaps appear quickly: three CRMs, no single customer record, critical capabilities running on unsupported platforms.
Score each capability on two axes: strategic differentiation and technical health. Differentiating capabilities with poor health are modernisation priorities; commodity capabilities are candidates for SaaS or rehosting.
Translate the map into a roadmap of waves, each with a business case, target architecture and measurable exit criteria. This gives the board a portfolio view of risk and return rather than a list of projects.
Keep the map alive. Linked to your CMDB and cloud tagging, it becomes the backbone for FinOps, risk and M&A integration decisions.
Want to apply this in your organisation?
Book a 45-minute discovery call with our architects to discuss your goals, constraints and a practical first step.