Describe capabilities in business language
Capabilities such as order management, customer support or financial close should not be named after current applications. This keeps the discussion useful even when the platform changes.
Connect capabilities to systems and information
Once the business view is clear, map supporting applications, data domains, integrations and ownership. Gaps, duplication and concentration of risk become easier to discuss.
Use the map to make bounded decisions
A capability map is not an architecture diagram for its own sake. Use it to decide where to assess, simplify, integrate or modernize based on a defined business priority.
Practical example
Example: customer support capability
Map the channels, customer data, case-management tools, knowledge sources and escalation process that support customer service. This shows where an Oracle CX or integration discussion may be relevant.
Best practices
Put the fundamentals in place.
- Keep capability names stable and independent of vendor products.
- Validate maps with both business and technology owners.
- Use the map with process and dependency evidence before funding a change.
Frequently asked questions
Is capability mapping only for large transformation programs?
No. It can focus a smaller application, integration or operating-model decision by showing its business context.
How is a capability different from a process?
A capability is what the organization needs to be able to do; a process is one way people and systems perform that work.
Related RSAInfosys expertise