# Change Impact Analysis

A structured assessment of how a proposed change affects value, people, processes, requirements, designs, systems, plans, risks, and obligations.

- Type: method
- Domain: Delivery & agility
- Level: Intermediate
- Last reviewed: 2026-09-24
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/change-impact-analysis/>)

## What it means

Change impact analysis identifies the direct and indirect consequences of a proposed change before a decision is made. It follows relationships across product behavior and its surrounding system to estimate benefits, costs, risks, dependencies, and affected stakeholders; change control is the broader process that authorizes and records the decision.

## Why it matters

Seemingly small product changes can alter operations, data, contracts, training, accessibility, tests, or downstream integrations. Impact analysis makes those consequences visible so decision makers can compare the change with alternatives and opportunity cost.

## When to use it

Use it for changes with cross-team, regulated, contractual, migration, or architectural consequences. Scale the depth to reversibility and risk; a small isolated experiment should not require enterprise-level analysis.

## How it works

1. Describe the proposed change, rationale, desired value, and decision deadline.
2. Use traceability, system maps, process models, and stakeholder knowledge to locate affected areas.
3. Assess effects on customers, staff, requirements, designs, data, interfaces, controls, and operations.
4. Estimate cost, timing, dependencies, risk, and consequences for existing commitments.
5. Compare implementation, deferral, rejection, and alternative approaches.
6. Recommend an action with assumptions and update linked artifacts if the change is authorized.

## A practical example

A subscription team proposes changing account ownership from a person to an organization. Analysis reveals effects on billing, permissions, tax records, audit logs, support scripts, exports, and partner APIs, leading the team to stage the migration rather than treat it as a field rename.

## Where it breaks

Unknown dependencies and stale documentation can hide consequences. Detailed analysis delays low-risk changes, while estimates remain uncertain until implementation. The method can also be biased toward preserving the status quo if only costs, not benefits, are examined.

## Common mistakes

- Assessing only code changes and ignoring people and operations.
- Using an outdated dependency or traceability map as complete evidence.
- Estimating implementation cost without the cost of not changing.
- Performing analysis after a commitment has already been announced.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/change-impact-analysis/#visualization-change-impact-analysis>)

## Sources

1. [Assess Requirements Changes](<https://www.iiba.org/knowledgehub/business-analysis-body-of-knowledge-babok-guide/5-requirements-life-cycle-management/5-4-assess-requirements-changes/>) — International Institute of Business Analysis · Professional standard
2. [I Still Don’t Have Time to Manage Requirements](<https://www.pmi.org/learning/library/poor-requirements-management-source-failed-projects-9341>) — Project Management Institute · Professional conference paper

## Related topics

- [Change Control](<https://wiki.soroush.uk/topic/change-control/>)
- [Requirements Traceability](<https://wiki.soroush.uk/topic/requirements-traceability/>)
- [Dependency Management](<https://wiki.soroush.uk/topic/dependency-management/>)
