Capability Maturity Model¶
Why This Exists¶
This document defines maturity levels for Business Capabilities.
Maturity helps Algosure evaluate whether a capability is merely named, consistently operated, measurable, executable, or continuously improving.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Each owning Practice is responsible for assessing and improving maturity for its capabilities.
Business Value¶
The maturity model creates business value by giving Algosure a shared way to prioritize improvement, identify capability risk, and connect investment to customer outcomes.
Maturity Levels¶
| Level | Name | Definition |
|---|---|---|
| 1 | Identified | The capability is named and has an initial business purpose. |
| 2 | Defined | The capability has an owner, ID, definition, business outcome, and basic relationships. |
| 3 | Managed | SOPs, Business Rules, data, UX, and KPIs are defined and reviewed. |
| 4 | Executable | The capability is supported by executable workflows, events, APIs, and measurable operation. |
| 5 | Learning | The capability improves through Organizational Memory, performance data, AI reasoning, and continuous learning. |
Maturity Progression¶
flowchart LR
L1[Level 1 Identified]
L2[Level 2 Defined]
L3[Level 3 Managed]
L4[Level 4 Executable]
L5[Level 5 Learning]
L1 --> L2 --> L3 --> L4 --> L5
Level 1: Identified¶
The capability is recognized as a business ability Algosure may need.
Minimum evidence:
- Draft name.
- Draft domain prefix.
- Initial business problem.
- Potential Practice owner.
Level 2: Defined¶
The capability is formally described.
Minimum evidence:
- Capability ID.
- Definition.
- Owning Practice.
- Accountable Digital Professional.
- Business outcome.
- Initial dependencies.
Level 3: Managed¶
The capability has operating controls.
Minimum evidence:
- SOPs documented.
- Business Rules identified.
- Data requirements documented.
- UX surfaces identified.
- KPIs defined.
- Governance review cadence set.
Level 4: Executable¶
The capability can be executed through workflow and system behavior.
Minimum evidence:
- Executable workflows.
- Events produced or consumed.
- APIs documented where relevant.
- Workflow state captured as data.
- Customer experience connected to headquarters areas.
Level 5: Learning¶
The capability improves through use.
Minimum evidence:
- Outcomes update Organizational Memory.
- KPIs are reviewed.
- AI reasoning uses prior context.
- SOPs are improved from operational learning.
- Practice owner reviews performance.
Maturity Assessment Rule¶
Capabilities should not be treated as fully mature because they are implemented. Implementation is not maturity. A capability reaches maturity only when it is owned, governed, measured, executable, and learning.