Change Impact Analysis
Part of the Business Analyst Roadmap
In short
New software can work perfectly and still fail because people weren't ready for it. Change impact analysis finds out who gets hit by a change, and how hard, before go-live.
Assessing how a proposed change will affect people, processes, and systems across an organization — surfacing resistance and disruption risks before they derail an implementation.
Think of it like this
Moving hostel breakfast to 7 am
The warden moves breakfast an hour earlier. Cooks need a new shift, the milk van must come sooner, students with 8 am labs are happy, night owls skip meals and food gets wasted. One small change, five groups affected.
Watch it happen
Asking each group: what changes for you?
New e-invoice app?
1/7The BA explains the change: paper invoices are being replaced by an app, and asks what it means for them.
The big ideas
What you need to know
People, process, systems, data
Check all four for every affected group. Most surprises hide in a process or a report nobody mentioned.
Rate the impact
Mark each group high, medium or low. High impact groups get early involvement, training and extra support.
Plan readiness actions
Each impact needs an action: training, updated SOPs, a new report, a helpdesk plan, or a phased rollout.
Ask, don't assume
The people doing the work know the side effects. Talk to them instead of guessing from the org chart.
Save yourself the pain
Common mistakes
Oops
Looking only at the teams that will use the new system.
Do this instead
Also check downstream teams: those who receive its reports, data or decisions.
Oops
Doing the analysis a week before go-live.
Do this instead
Start once the solution is roughly clear, so training and process changes have time to happen.
Your mission
Map one change
Quick check
A new billing system works well in testing, but after launch the accounts team can't produce their monthly tax report. What was likely missed?
Go deeper
- 1Run a change impact analysis for a hypothetical process change, covering people, process, and systems.
- 2Learn why underestimating people-side impact is a common cause of implementation failure.
- 3Practice identifying which stakeholder group would resist a specific change most, and why.
More topics at this stop
SWOT Analysis
Business Model Canvas
PESTLE Analysis
Cost-Benefit Analysis
Business Case Development
ROI & Feasibility Analysis
Competitive Analysis for BAs
Strategic Planning Basics
Stuck on this topic? Ask an Insider
Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.
