Skip to content

Capability Governance

Why This Exists

Business Capabilities are primary design units. They affect product structure, Practices, Digital Professionals, SOPs, Business Rules, APIs, Events, Data, UX, KPIs, and customer outcomes.

This document defines governance controls so capabilities remain stable, owned, and aligned to the Algosure Blueprint.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

The owning Practice governs individual capabilities within the standards defined here.

Business Value

Capability governance creates business value by protecting the integrity of the Digital Procurement Company. It prevents duplicate capabilities, unclear ownership, ungoverned automation, and architecture drift.

Governance Principles

Principle Meaning
One Concept, One Owner Each capability has one owning Practice and one accountable Digital Professional.
Architecture Mirror Principle Capability structure must mirror the Digital Procurement Company operating model.
Business first, technology second Capability purpose must be clear before implementation.
Evidence before approval Capability decisions must be supported by customer value and operating need.
Implementation is not ownership A team may implement a capability without owning the business concept.

Governance Events

Governance is required when:

  • A new capability is proposed.
  • A capability ID is assigned.
  • Ownership changes.
  • Maturity level changes.
  • A capability becomes executable.
  • A capability affects APIs, Events, Data, or UX.
  • A capability is deprecated or retired.
  • A capability changes customer-facing behavior.

Governance Workflow

flowchart LR
    Proposal[Capability Proposal]
    Review[Practice Review]
    Architecture[Architecture Review]
    Decision[Approval or Rejection]
    Catalogue[Catalogue Update]
    Measure[Ongoing Measurement]

    Proposal --> Review
    Review --> Architecture
    Architecture --> Decision
    Decision --> Catalogue
    Catalogue --> Measure
    Measure --> Review

Required Review Questions

  1. What business outcome does the capability create?
  2. Which Practice owns it?
  3. Which Digital Professional is accountable?
  4. Which SOPs and Business Rules govern it?
  5. What APIs, Events, Data, and UX are affected?
  6. Which KPIs measure it?
  7. What maturity level applies now?
  8. Does this duplicate an existing capability?
  9. Does it require a decision record?

Decision Records

A capability change requires a decision record when it introduces or changes durable architecture, ownership, governance, or operating model.

Governance Output

Approved capabilities must be added to Capability Catalogue and documented using Capability Template.