A Capability in Catalio represents a discrete, named ability that your organization either currently possesses or needs to develop. Capabilities are the stable organizing layer that transcends technology changes, team reorganizations, and platform migrations.
Where Features are Application-specific (“the AP module in Oracle EBS”), Capabilities are business-level (“Accounts Payable processing”). A Capability can remain constant even as the systems that deliver it change completely.
The Difference Between Capabilities and Features
| Concept | Scope | Example |
|---|---|---|
| Capability | Business-level, technology-agnostic | “Invoice Processing” |
| Feature | Application-specific | “AP Invoice Entry Screen in Oracle EBS” |
A single Capability may be delivered by multiple Applications and Features. When you modernize a system, the Capability stays — the Application and Feature implementing it changes.
Key Fields
| Field | Purpose |
|---|---|
| name | Capability name, e.g. “Customer Account Management” |
| description | What this capability enables the organization to do |
| parent_id | Optional parent for hierarchical capability trees |
| status | Whether the capability is active, planned, or deprecated |
| capability_type | Classification of capability domain |
Capabilities can be organized hierarchically:
Financial Management (parent)
├── Accounts Payable
│ ├── Invoice Receipt
│ ├── Invoice Matching
│ └── Payment Processing
└── Accounts Receivable
├── Customer Invoicing
└── Cash Application
Capabilities and Requirements
Requirements describe what a system must do. Capabilities describe what the business must be able to do. In Catalio, you can link Requirements to Capabilities, enabling coverage analysis:
- Which Capabilities have no Requirements yet? (gap)
- Which Capabilities have the most Requirements? (complexity indicator)
- Which Requirements implement a given Capability?
Capabilities and Processes
Processes in Catalio represent ordered workflows that deliver business outcomes. Capabilities and Processes are complementary perspectives:
- Capability: “What can the business do?” (noun)
- Process: “How does the business do it?” (verb, sequence)
A Capability may have multiple Processes. For example, the “Invoice Processing” capability might be delivered by both an “Invoice Approval Process” and an “Emergency Payment Process.”
Capabilities and Policies
Policies — governance rules, compliance requirements, and technical standards — can be linked to Capabilities via the PolicyCapability relationship. This enables you to see all compliance constraints that apply to a given business capability at a glance.
Example:
Capability: "Customer Data Management"
Policies: GDPR Right to Erasure (Mandatory)
PCI-DSS Data Storage Standard (Mandatory)
Internal Data Retention Policy (Recommended)
Sources: Connecting Real-World Data to Capabilities
Each Capability can be connected to one or more Sources — Slack channels, MS Teams channels, GitHub repositories, or other data feeds. Catalio’s AI monitors these Sources and surfaces relevant conversations, code changes, and discussions as potential Requirements or updates to existing ones.
Why this matters for discovery:
Stakeholders rarely write formal requirements documents. Most institutional knowledge lives in Slack threads, meeting recordings, and code comments. By linking a Capability to its relevant communication channels, you enable Catalio to passively harvest this knowledge.
Capability Assessment in Initiatives
Within Initiatives, you can create a Capability Assessment for each Capability in scope — scoring its current (“as-is”) and target (“to-be”) maturity on a 1-5 scale. This heatmap provides a transformation readiness visualization: which capabilities need the most work, and which are already strong?
Maturity scale:
- 1 — Non-existent or completely manual
- 2 — Partial, inconsistent delivery
- 3 — Functional but inefficient or non-standardized
- 4 — Efficient, standardized, and measured
- 5 — Optimized, automated, and continuously improved
Best Practices
Use business language, not technical jargon.
Capabilities are business concepts. “Customer Credit Evaluation” is better than “FICO Score API Integration” — the latter describes an implementation, not a capability.
Start with 10-20 top-level Capabilities.
Don’t try to capture every possible capability before starting discovery. Begin with the major business domains your engagement covers, then expand hierarchically as you learn more.
Map Capabilities to organizational accountability.
The best Capabilities have clear business owners. If nobody in the organization is responsible for a Capability, that’s a discovery finding in itself.
Use Capability Assessments to prioritize.
Low current maturity + high business importance = highest priority for modernization investment. Capability Assessments make this tradeoff visible to stakeholders.
Relationships at a Glance
| Related Concept | Relationship |
|---|---|
| Requirements | Requirements can be linked to Capabilities |
| Processes | Processes deliver Capabilities |
| Policies | Policies constrain Capabilities |
| Sources | Sources feed knowledge into Capabilities |
| Initiative | Initiatives assess Capability maturity |
Next Steps
- Connect Sources — Attach data feeds for automated discovery
- Add Requirements — Specify what systems must do to deliver a Capability
- Link Policies — Apply governance constraints to Capabilities
- Create Initiatives — Assess Capability maturity and plan improvements
Pro Tip: Capabilities are the most durable concept in Catalio. Invest time in getting the Capability tree right — it will outlast any specific technology choice or organizational structure.
Support
- Documentation: Continue reading about Sources and Processes
- Email: support@catalio.ai
- Community: Share capability mapping approaches with other Catalio users