Change Management
BC-910
Level 1
Cross-Industry
1 providers
6 API surfaces
Organisational change planning and execution.
Change Management (BC-910) is a level-1 business capability in the Cross-Industry model. The catalog holds 6 API surface(s) from 1 provider(s) that can perform some part of it. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.
Where this capability definition comes from.
This capability is part of a published business-architecture model that API Evangelist
did not author. It is redistributed here under
CC-BY-4.0.
Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented.
Source repository · NOTICE and third-party framework attributions
Sub-capabilities
Change Strategy Management BC-910.10
Change vision, narrative, strategy.
no catalog coverage
Change Stakeholder Engagement Management BC-910.20
Stakeholder identification, engagement, alignment.
1 provider,
1 API surface
Change Communications & Training Management BC-910.30
Communications and training as part of change.
no catalog coverage
Change Adoption & Reinforcement Management BC-910.40
Adoption tracking, reinforcement, sustainment.
1 provider,
1 API surface
Providers that reach this capability
Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.
- Prosci thin 35.2
This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature.
This page shows which providers and tags reach Change Management. The underlying
tag → capability edges — each with the quoted fragment of the provider's own
OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate
it passed — are available through the API, along with company-level capability maps.
Only edges at confidence ≥ 0.7 with evidence found verbatim in
the source contract are published at all.