ERP transformation readiness is about far more than a configured system and a tested cutover plan. Go-live holds when people understand what changes in their daily work, managers are equipped to support their teams through the transition, processes and roles are genuinely ready, and the programme has evidence that adoption will survive after the implementation team steps back.
This hub brings together ERP-specific readiness guidance, adoption evidence practice and the diagnostic tools ReadinessCompass uses on implementation programmes. Use it to work out what to measure before go-live, understand how manager support and training transfer shape adoption, and see where people risk usually hides in large ERP rollouts.
Featured ERP readiness assessment
Assessment guide
ERP Change Readiness Assessment
Assess ERP change readiness before go-live across user confidence, leadership alignment, manager support, process and role readiness, data and cutover preparedness, and Day-1 capability.
Explore the ERP Change Readiness Assessment→ERP readiness foundations
Article
Change Readiness Is Not a Mood
Why ERP and digital transformation leaders cannot reduce readiness to sentiment, and which practical signals reveal fragile adoption conditions early enough to act.
Read why readiness is not a mood→Article
The Readiness Gap Between Executives and Frontline Users
Executives and frontline users routinely report very different levels of preparedness. Understand why the gap forms and what it means for ERP go-live decisions.
Read about the readiness gap→Article
The Hidden Cost of Expert Overload
ERP programmes often lean on a small group of key users until they become a delivery bottleneck. See how expert overload builds and what it costs at go-live.
Read about expert overload→
Managers, capability and adoption
Article
The Manager as Adoption Multiplier
Middle managers decide whether new ERP ways of working are reinforced or quietly abandoned. Understand what managers need in order to carry adoption.
Read about manager-led adoption→Article
Training Is Not Adoption
Completed training is not evidence that people can work in the new system. See why ERP and AI programmes need practice, not just learning.
Read why training is not adoption→Practical guide
The Manager Toolkit for ERP and AI Adoption
A practical set of actions managers can use to support their teams through ERP and AI adoption, from early communication to reinforcement after go-live.
Open the manager toolkit→Practical guide
Cutover Rehearsals That Test People
A technical rehearsal proves the migration completes in the window. Designing the exercise that proves the organisation can work on Monday.
Read the rehearsal design guide→Practical guide
Training Needs Analysis for ERP
Nobody has a job called Order to Cash. Build the curriculum from a role and task matrix, and name the conditions training depends on.
Read the TNA guide→Practical guide
Super Users: Select, Train and Keep
Selected on availability rather than influence. Who the team already asks, training them to teach, and writing the release down.
Read the super user guide→Practical guide
Training Environments and Real Data
A sanitised practice system teaches a simplified job. A small amount of deliberately awkward data delivers most of the benefit.
Read the environment guide→Practical guide
Evaluating Whether Training Worked
Completion measures the first two Kirkpatrick levels. Behaviour is the one that matters, and unaided completion makes it measurable.
Read the evaluation guide→Practical guide
Onboarding New Joiners After Go-Live
Informal onboarding transmits what a colleague does, not the process. How workarounds become hereditary.
Read the onboarding guide→Practical guide
Data Migration Is a People Problem
Reconciliation proves nothing was lost. Ownership, cleansing judgement and trust decide whether anyone uses the result.
Read the data migration guide→Practical guide
Work Instructions Nobody Reads
Reference documentation and job aids are different artefacts with one name. Write for the moment of need.
Read the documentation guide→Article
Local Process Owners vs Communication Cascades
Cascaded messages rarely survive the journey to a specific team. Why a named local process owner moves adoption further than another communication layer.
Read about local ownership→
Adoption evidence before go-live
Article
Why ERP Programs Need Adoption Evidence Before Go-Live
Milestone completion is not adoption evidence. See which signals show whether an ERP programme is genuinely ready for Day 1.
Read about adoption evidence→Article
From Readiness Survey to Leadership Action
How to turn readiness survey results into decisions leaders will actually make, rather than dashboards nobody acts on.
Read how surveys become action→Article
From Resistance to Signal
Employee pushback during an ERP rollout usually carries specific information about capability, capacity or trust. Learn how to read it.
Read what pushback tells you→Practical guide
Why Users Go Back to Excel After ERP Go-Live
A spreadsheet workaround is adoption evidence, not misbehaviour. Nine causes behind ERP reversion, how to confirm each one and what fixes it.
Read the spreadsheet diagnosis→Practical guide
How UAT Reveals Adoption Risk Before ERP Go-Live
UAT is the richest people-readiness evidence a programme gets. Nine adoption signals to read from user acceptance testing before cutover.
Read the UAT readiness signals→Practical guide
Business Readiness vs Technical Readiness
Technical sign-off says the system works. Business readiness says the organisation can produce its output using it. Who signs which claim, and on what evidence.
Read the go-live sign-off guide→Practical guide
What Transaction Logs Reveal
Surveys measure belief, logs record behaviour. Six signals worth extracting, and the monitoring constraint to plan for.
Read the telemetry guide→
Related assessments and tools
Assessment
Change Readiness Assessment and the ReadinessCompass Score
The broader staged readiness assessment behind the ERP view, tracking people readiness as a measurable KPI across transformation waves.
Explore the ReadinessCompass Score→Assessment
Business Readiness Assessment
What to measure to establish that the business can produce its normal output from Day 1, and why readiness criteria are so often met while the go-live still fails.
See what to measure→Tool guide
Change Complexity Assessment Tool
Estimate the people-side complexity of an ERP programme and identify where adoption effort will concentrate.
Open the Change Complexity guide→Tool guide
Change Impact and Mitigation Register
Map how ERP changes affect roles, processes and data, then connect each impact to an owned mitigation before go-live.
Open the impact register guide→
Need a focused ERP readiness review?
Structured review
Readiness Diagnostic Sprint
Bring fragmented ERP readiness evidence into one focused review with prioritised adoption risks, named owners and an executive-ready action plan.
Request an ERP readiness review→