EM-STR-03 · Subject model · W2
Business Capabilities
The enterprise's ability to achieve a defined class of outcomes independently of the current structure and means of implementation.
Queued for research
Claude: not-started; Grok: not-started.
Research note, in Russian: Entire research brief pending
Subject boundary and candidate types
- BusinessCapability
- CapabilityLevel
- CapabilityAssessment
- CapabilityRealization
Deep research questions
- Where is the boundary of a capability relative to a process, a function and a product?
- How are levels of detail formed without the org structure acting as the taxonomy?
- Which methodology confirms maturity and coverage?
Verifiable invariants
- A capability survives reorganization
- A maturity assessment is bound to a methodology
- A system supports a capability, it does not automatically realize it in full
End-to-end acceptance scenario
After a process is transferred to another unit, the capability map keeps its IDs and changes only the realizations.
Negative case
A department name is used as the sole definition of a capability.
Approaches to compare
- ArchiMate: motivation, capability and realization relationships
- APQC: coverage of functions and processes
- PMI: benefit/business case; compare with a chosen OKR school and value-stream management
Candidates in the live catalogue
- WM-ACT-001 · Function / Capability · 0.2.0-legacy · not installed automatically
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.