Why Impact Assessment Precedes Change
The difference between change that sticks and change that stalls is preparation. Impact assessments identify who and what will be affected by a change before it happens, enabling proactive mitigation rather than reactive firefighting.
Organizations that conduct formal impact assessments before major changes are 6× more likely to meet their objectives on time and on budget (Prosci, 2023). Yet fewer than 40% of organizations conduct rigorous impact assessments, a key contributor to the 70% digital transformation failure rate.
The Four-Dimension Impact Model
Dimension 1: People Impact
Assess how the change affects the humans in the organization: their roles, skills, workload, and wellbeing.
Impact areas to evaluate:
| Impact Area | Assessment Questions | Severity (1-5) | |-------------|---------------------|----------------| | Role changes | Will job descriptions, responsibilities, or reporting lines change? | | | Skills required | Do employees need new skills or certifications? | | | Workload | Will workload increase during transition? By how much? | | | Headcount | Will positions be eliminated, created, or restructured? | | | Career paths | Will career progression paths change? | | | Compensation | Will pay structures, incentives, or benefits be affected? | | | Work location | Will physical work locations or remote policies change? | |
Severity scale:
- •1: Minimal: Minor adjustments within existing capabilities
- •2: Low: Some reskilling or adjustment needed, manageable within BAU
- •3: Moderate: Significant change requiring dedicated training and support
- •4: High: Major disruption to daily work; extensive transition period
- •5: Transformational: Fundamental redefinition of roles or employment terms
Dimension 2: Process Impact
Assess how workflows, procedures, and operational norms will change.
Impact areas to evaluate:
| Impact Area | Assessment Questions | Severity (1-5) | |-------------|---------------------|----------------| | Core workflows | Which key processes will be redesigned or eliminated? | | | Handoffs | Will cross-team handoff points change? | | | Decision rights | Will approval authorities or escalation paths change? | | | Documentation | Will SOPs, policies, or compliance docs need updating? | | | Metrics | Will success metrics or KPIs change? | | | Governance | Will oversight, audit, or review processes change? | | | Dependencies | Will upstream or downstream process dependencies shift? | |
Dimension 3: Technology Impact
Assess how systems, tools, and data flows will be affected.
Impact areas to evaluate:
| Impact Area | Assessment Questions | Severity (1-5) | |-------------|---------------------|----------------| | Systems | Which systems will be replaced, upgraded, or retired? | | | Integrations | Will data flows between systems change? | | | Data | Will data structures, ownership, or governance change? | | | User interfaces | Will the tools employees interact with daily change? | | | Access/security | Will permissions, authentication, or compliance requirements change? | | | Infrastructure | Will hosting, networking, or architecture change? | |
Dimension 4: Culture Impact
Assess how organizational norms, values, and behaviors will be affected. Culture impact is often underestimated and is the most common reason changes fail to sustain.
Impact areas to evaluate:
| Impact Area | Assessment Questions | Severity (1-5) | |-------------|---------------------|----------------| | Power dynamics | Will the change shift influence or authority? | | | Collaboration norms | Will how teams work together change? | | | Communication patterns | Will information flow differently? | | | Performance expectations | Will what "good" looks like change? | | | Values alignment | Does the change reinforce or conflict with stated values? | | | Identity | Will teams' sense of purpose or identity be disrupted? | |
Conducting the Assessment
Step 1: Define the Change
Before assessing impact, clearly articulate what is changing. Use this structure:
- •From (current state) → To (future state)
- •Scope: Which teams, locations, and processes are in scope?
- •Timeline: When will the change begin and when is it expected to stabilize?
- •Driver: Why is this change happening?
Step 2: Identify Affected Groups
Map every stakeholder group that will be affected. For each group, document:
- •Group name and size
- •How directly they're affected (primary, secondary, peripheral)
- •Current relationship with the change topic (supportive, neutral, resistant)
Step 3: Score Each Dimension
Assemble a cross-functional assessment team. Score each impact area independently, then discuss discrepancies. The discussion itself often surfaces hidden impacts.
Step 4: Calculate Aggregate Impact
Dimension Impact Score = Average of all impact areas within that dimension
Overall Impact Score = Average of all four dimension scores
| Overall Score | Impact Level | Implication | |---------------|-------------|-------------| | 1.0 – 1.9 | Low | Standard communication and training sufficient | | 2.0 – 2.9 | Moderate | Dedicated change management support recommended | | 3.0 – 3.9 | High | Comprehensive change program required | | 4.0 – 5.0 | Transformational | Major investment in people, process, and culture needed |
Step 5: Build Mitigation Plans
For every impact area scoring 3 or above, create a mitigation plan:
| Impact Area | Score | Mitigation Action | Owner | Timeline | Status | |-------------|-------|-------------------|-------|----------|--------| | Example: Role changes | 4 | Redesign role descriptions; 1:1 conversations with affected staff | HR Lead | Weeks 1-4 | Not started | | Example: Core workflows | 3 | Map new workflows; pilot with one team before rollout | Process Owner | Weeks 2-6 | Not started |
Using Discovery to Inform Impact Assessment
One of the most valuable inputs to an impact assessment is qualitative discovery data: what employees actually think, feel, and experience about the areas being changed.
Traditional approaches rely on small focus groups or leadership assumptions. AI-powered discovery tools like Horizon enable organizations to gather input from across the organization before the change, providing:
- •Baseline sentiment: How do people feel about the current state?
- •Anticipated concerns: What are employees already worried about?
- •Hidden dependencies: What informal processes or relationships will the change disrupt?
- •Change fatigue indicators: Is the organization already overwhelmed with change?
This data transforms the impact assessment from an educated guess into an evidence-based analysis.
Impact Assessment Anti-Patterns
- •Assessing too late: If you start the assessment after the solution is decided, it becomes a checkbox exercise. Start during solution design.
- •Excluding frontline voices: Leaders often underestimate people and culture impact because they experience change differently than frontline staff.
- •Treating it as static: Impact evolves as implementation progresses. Reassess at each phase gate.
- •Ignoring cumulative impact: A single change may score "moderate," but if it's the fifth change this quarter, the cumulative impact on the same people may be transformational.
- •Separating from change management: The assessment should directly feed the change management plan, communication strategy, and training design.
Connecting Assessment to Action
The impact assessment is not the destination. It's the input to three critical deliverables:
- •Change Management Plan: Detailed activities to manage adoption, organized by the Change Management Framework
- •Communication Plan: Targeted messaging for each affected group using the Stakeholder Communication Plan Template
- •Training Plan: Skill development and support mapped to people impact areas
An assessment that doesn't connect to action is an academic exercise. Use it to drive decisions, allocate resources, and protect the people who make change succeed.