Capability Architecture

Intro

Capability Architecture describes how a capability is realized by processes, data, applications, and technology. It matters in EA because it connects strategy to executable change.

Key points:

• Blueprint for people, process, data, and systems
• Enables traceability from objectives to solutions
• Used in roadmaps, operating model design, and solution scoping
• Pitfall: jumping to solutions without defining outcomes and constraints

Examples:

• Designing “Customer Onboarding” across KYC, workflow, and data platforms
• Defining “Order Fulfilment” integrations and SLAs
• Mapping “Financial Reporting” controls and data lineage

In practice:

Document current and target states, then stage changes as increments tied to value.

Related terms: Capability; Operating Model; Roadmap

FAQs:

Q: How detailed should a capability architecture be?
A: Enough to guide design decisions and dependency planning.

Q: Who owns it?
A: The capability owner with architects and SMEs.

‍