How-to
How to Assess ERP Change Readiness Step by Step
Quick Summary
An ERP change readiness assessment checks whether your organisation is prepared to adopt a new system before money and time are spent. It measures leadership commitment, culture, people, data, processes and technology, and should be repeated at each stage gate through go-live and beyond.
- Run an assessment before approving the business case, before design sign-off, before testing, before go-live, and after go-live.
- Score leadership on a 1 to 5 scale using observable behaviours rather than opinions.
- Treat a leadership average below 3 as a reason to hold design sign-off until a remediation plan exists.
- Measure awareness, skills and willingness separately, and flag any user group scoring below 3.0 on a dimension.
- Turn your three to five lowest scores into priority actions, each with an owner, a deadline and a measure.
Table of Contents
- What an ERP Change Readiness Assessment Measures and When to Run One
- Step 1: Map Stakeholders and Impacted Users
- Step 2: Score Leadership Commitment, Culture and Change History
- Step 3: Test Data, Technical and Process Readiness
- Step 4: Measure Employee Awareness, Skills and Willingness to Change
- Step 5: Assess the Change Impact on Roles and Sites
- Step 6: Turn Scores into a Plan You Can Act On
- Book a Readiness Review Before Your Next Go-Live Decision
- Frequently Asked Questions
What an ERP Change Readiness Assessment Measures and When to Run One
Last Updated: November 15, 2026
An ERP change readiness assessment tells you whether your organisation is prepared to absorb a new system before money and time are spent. It looks at leadership support, people, processes, data and technology.
Most ERP programmes do not fail on the software. They fail because the organisation was not ready for the change. A readiness assessment is the check that catches this before go-live.
Change readiness is the degree to which people, processes, leaders and systems are prepared to adopt a specific change. For ERP, it covers whether users will actually work in the new system, not just whether the software is installed.
The assessment measures several areas:
- Leadership commitment: whether sponsors are visible and willing to make trade-offs
- Culture and change history: how the organisation has handled past change
- People readiness: awareness, skills and willingness of the users
- Data and technical readiness: whether data is clean and systems are prepared
- Process readiness: whether current processes are documented and understood
- Impact on roles and sites: how much daily work will change, and where
Run an assessment at these points:
- Before you approve the business case or sign a vendor contract
- Before design sign-off, when scope is still flexible
- Before data migration and testing begin
- Before go-live, as a final check
- After go-live, to measure adoption
A common mistake is running one assessment and treating the result as permanent. Readiness shifts as people, priorities and budgets change, so repeat the measurement at each stage.
Step 1: Map Stakeholders and Impacted Users
Start by listing everyone the ERP change will touch. This includes executives, process owners, end users, IT staff, finance, and external partners. Group them by how much their daily work will change.
Impacted users are the people who will feel the change most. They are often the ones with the least say in the project. Find them early.
For each group, record:
- The name of a named contact or owner
- How their work will change
- How much influence they have over adoption
- Their likely concerns
Watch out: a stakeholder list built only from the org chart misses the people who really run processes. Ask process owners who does the work day to day.
Step 2: Score Leadership Commitment, Culture and Change History
Leadership is the strongest predictor of whether an ERP change sticks, but vague questions produce vague answers. Score the executive sponsor and senior leaders on a 1 to 5 scale using observable behaviours, not opinions. A score of 1 means the behaviour is absent; 3 means it is inconsistent; 5 means it is embedded and visible across the programme.
Use these ERP-specific indicators for the leadership dimension:
- Sponsor visibility: Has the sponsor attended the last three steering meetings and spoken at town halls about the ERP change? (1 = no shows; 5 = chairs the forum and presents a consistent narrative)
- Trade-off willingness: Has the sponsor delayed or cancelled a competing project to protect ERP resources? (1 = every project protected; 5 = clear, documented trade-offs)
- Decision latency: How many working days does it take to resolve a scope or design decision escalated to the sponsor? (1 = more than 15 days; 5 = under 3 days)
- Modelling the change: Are leaders using the new system in pilot or sandbox environments before go-live? (1 = never; 5 = routinely and visibly)
- Consequence management: Are managers who bypass the new process held to account? (1 = no consequences; 5 = performance plans reflect adoption)
Next, score culture and change history. Ask what happened the last time the organisation changed a major system. Look for patterns in training completion, data clean-up effort, and adoption curves. A common pattern is that organisations repeat the same failure mode: if the last ERP go-live was delayed by data migration, the current programme is likely to face the same risk unless someone owns data quality explicitly.
Score these culture and history items:
- Past change outcomes: Did the last major system change meet its go-live date and adoption targets? (1 = missed both; 5 = met both)
- Lessons captured: Is there a documented lessons-learned register from the previous change, and is it referenced in the current plan? (1 = none; 5 = actively used)
- Change fatigue: How many major organisational changes have affected the same user groups in the past 24 months? (1 = more than four; 5 = none)
- Data ownership culture: Do business units already treat data as an asset with named owners? (1 = no ownership; 5 = ownership embedded in role descriptions)
- Process discipline: Do sites follow standard processes today, or do local variations dominate? (1 = every site different; 5 = standard with approved exceptions)
Record a score and a short evidence note for each item. A low score is not a failure. It tells you where to act first. Set a decision threshold: if the leadership average falls below 3, do not proceed to design sign-off until the sponsor has a documented remediation plan. If change fatigue scores 1 or 2, sequence the ERP rollout to avoid clashing with other major changes for the most affected groups.
Watch out: scoring leadership from a single workshop with the sponsor in the room produces inflated results. Collect evidence from project managers, process owners, and steering committee minutes before assigning scores.
Step 3: Test Data, Technical and Process Readiness
This is the area most generic assessments skip. ERP-specific readiness depends on the state of your data and processes.
Check these items:
- Data quality: Are customer, supplier and product records accurate and complete?
- Data ownership: Does each data set have a named owner?
- Technical readiness: Are integrations, interfaces and infrastructure planned and tested?
- Process documentation: Are current processes written down and agreed?
- Process standardisation: Do sites run the same process, or many versions?
Score each area from 1 to 5. A low score on data quality is a warning sign. Data migration problems are one of the most common causes of delayed go-lives. Our guide on how to reduce ERP implementation risks sets out five key risks and practical mitigations you can assign today.
Set a decision threshold. For example, if data quality scores below 3, hold the migration plan until it is fixed. Thresholds turn scores into clear decisions. Use this ERP implementation plan guide to write a sequenced plan that defines what must be delivered, by whom, when, and at what cost.
Step 4: Measure Employee Awareness, Skills and Willingness to Change
Awareness, skills and willingness are three separate things. A person can know about the change, lack the skills, and still be willing. Measure each one separately, then combine them into a readiness score for each user group.

Use a short survey with a 1 to 5 agreement scale (1 = strongly disagree; 5 = strongly agree). These ERP-specific questions cover the three dimensions:
Awareness
- I understand why the organisation is replacing its ERP system.
- I can explain what changes in my daily work after go-live.
- I know where to find help when I have a question about the new system.
Skills
- I have completed the training assigned to my role.
- I can perform my main tasks in the new system without step-by-step guidance.
- I know how to handle exceptions and errors in the new process.
Willingness
- I believe the new system will make my work better, not worse.
- I am willing to change how I do my job to fit the new system.
- I would recommend the new system to a colleague in a similar role.
Add two open questions: "What worries you most about the change?" and "What would help you feel ready?" These surface barriers that scaled questions miss.
Score each dimension by averaging responses within each user group. Then apply a simple interpretation rule: a group average below 3.0 on any dimension is a red flag. Awareness below 3.0 means communication has not landed; skills below 3.0 means training is incomplete or mistimed; willingness below 3.0 means resistance is active and needs a targeted response, not a generic email.
Compare scores across groups rather than relying on an organisation-wide average. A common pattern is that head office scores 4.0 while a regional site scores 2.5, and the organisation-wide average of 3.5 hides the real risk. Report scores by department, location, and job role so that high-impact groups receive targeted support.
Repeat the survey at each stage gate and track the trend. A rising score after a communication or training intervention shows the plan is working. A flat or falling score means the intervention missed the mark and needs redesign. Keep the same questions across waves so that comparisons are valid.
Watch out: surveying only volunteers or only people who attend workshops produces a biased sample. Aim for a response rate above 60 per cent in each high-impact group, and follow up with interviews in any group that scores below 3.0.
Step 5: Assess the Change Impact on Roles and Sites
Not every role or site faces the same level of change. A finance team moving to a new ledger may change a lot, while a warehouse team may change very little. Assess readiness role by role and site by site.
Use a simple change impact rating:
| Impact level | What it means | Example |
|---|---|---|
| High | New tools and new daily steps | Order-to-cash team |
| Medium | Changed reports or approvals | Regional managers |
| Low | Minor screen or label changes | Occasional report viewers |
High-impact groups need more training, more support and earlier involvement. Low-impact groups may need only a short briefing.
Step 6: Turn Scores into a Plan You Can Act On
A readiness assessment has no value until it changes what you do. Gather your scores from each step and find the three to five lowest-scoring areas. These become your priority actions.
For each priority, write:
- The action to take
- The owner who will deliver it
- The date it must be finished by
- How you will measure progress
Repeat the assessment at the next stage gate and compare scores. A rising trend shows the plan is working.
Book a Readiness Review Before Your Next Go-Live Decision
If you are about to make a go-live decision, book a conversation to talk through where your readiness gaps sit. Book a readiness review to arrange a 30-minute conversation, or see how we deliver and recover ERP programmes for organisations with stalled or over-budget projects.
For a closer look at turning findings into action, read how to manage complex ERP change with an impact assessment and phased rollout.
Frequently Asked Questions
What is an ERP change readiness assessment?
An ERP change readiness assessment is a structured review of whether an organisation is prepared to adopt a new or changed ERP system. It scores several dimensions, including leadership commitment, employee awareness and willingness, organisational culture and change history, data and technical readiness, process readiness, and the capacity to absorb change alongside competing priorities. The output is a scored baseline with clear gaps, which the project team uses to decide whether to proceed, delay, or put targeted interventions in place before go-live.
When should you conduct an ERP change readiness assessment?
Run the first assessment early, before vendor selection is locked or the business case is approved, so the findings can shape scope and budget. Repeat it at key gates: after design sign-off, before user testing ends, at go-live readiness, and again roughly three months after go-live. Repeat measurement shows whether interventions are working and whether adoption is on track, rather than relying on milestone completion alone.
Who should be involved in an ERP readiness assessment?
Include the executive sponsor, business unit leaders, IT programme managers, process owners, super users, and a representative sample of end users across each role and site. Involving frontline staff matters because they reveal adoption barriers that leaders often miss. Keep the assessment independent of the team delivering the implementation where possible, so the scores are not shaped by the delivery timeline.
How do you identify resistance to ERP change?
Resistance usually shows up as low survey scores on willingness, workarounds in existing spreadsheets, vague answers when asked how daily work will change, and attendance drop-off in training sessions. Combine a short pulse survey with structured interviews in each impacted group. Look for patterns by role and site rather than single comments, and record the specific concern behind each low score so the change plan can address it directly.