Skip to main content

Capability-Led Design

Statement​

Systems and solutions must be designed around stable business capabilities, not transient processes or organisational structures.

Rationale​

Business capabilities change less frequently than processes and org charts. Aligning systems to capabilities reduces the frequency of costly rewrites and enables reuse across the organisation.

Implications​

  • All projects must map their scope to the Business Capability Model before design begins
  • Capability ownership is defined and documented
  • Capability boundaries inform system boundaries