Business capabilities and aligning IT with the business
In short: A business capability is something an organisation must be able to do, such as "take payments" or "enrol students", described independently of who or what does it. Capability maps give business and IT a shared language and show where investment, risk and duplicate systems are concentrated.
What a capability is
A business capability describes what an organisation does, not how. "Manage customer accounts" is a capability. The team that does it, the CRM software and the process steps may all change, but the capability stays. That stability makes capabilities a good anchor for planning, because org charts and systems change far more often than what the business fundamentally does.
Capabilities differ from processes. A process is a sequence of steps with a start and end (for example, onboarding a new employee). A capability is the ability itself, which may be used by many processes.
Building a capability map
- Start with 6 to 10 top-level (level 1) capabilities that cover everything the organisation does.
- Break each one into level 2 capabilities, and level 3 only where you need detail.
- Name them as noun-verb phrases ("Payment processing", "Recruit staff"), not as departments or systems.
- Check with business leaders that nothing is missing and nothing overlaps.
- Map applications, data and teams onto each capability.
Industry reference maps exist for sectors such as banking, telecoms and government, and can save time as a starting point.
Heat maps: where to invest
Once applications are mapped, you can colour capabilities by a measure. This is a heat map, and it turns a long list into a clear picture for decision-makers.
| Lens | Question | What it reveals |
|---|---|---|
| Strategic importance | Does this capability set us apart? | Where to invest and innovate |
| Performance | How well does it work today? | Weak areas needing improvement |
| Technology health | Are the supporting systems current and supported? | End-of-life risk |
| Security risk | How exposed is the data and how strong are controls? | Where to focus security spend |
| Duplication | How many systems do the same job? | Chances to consolidate and save |
A capability that is strategically important, performing poorly and running on unsupported technology is a clear candidate for the next round of funding.
Aligning IT with the business
Business-IT alignment means technology work is clearly linked to business outcomes. Practical habits help:
- Describe IT projects in business terms: "keeps payments running during peak enrolment", not "upgrade cluster to version X".
- Rank systems by the capabilities they support, and use that to set backup, recovery and patching priorities.
- Ask which capability a new tool supports before buying it; this exposes duplicate purchases.
- Agree measures that both sides understand, such as service availability, time to enrol a student or cost per transaction.
Tip: for a security or network proposal, show which capabilities are at risk and what the business impact would be. Leaders fund risks to things they care about far more readily than technical upgrades.
Practice
Is "Finance department" a good capability name? Why or why not?
What is the difference between a capability and a process?
How can a capability heat map help reduce costs?
Key takeaways
- A capability is what an organisation does, independent of who or what does it.
- Capability maps are hierarchical and use stable, noun-verb names.
- Heat maps highlight investment, risk and duplication.
- Trace goals to capabilities, applications and technology.
- Explain IT and security work in terms of the capabilities it protects.
Original content written by Mohamed Fayas for FM TecHub. © 2026 FM TecHub. You're welcome to share a link to this page; please don't copy the text elsewhere without permission.