In most companies, the ERP investment decision starts with software selection: demos are watched, proposals are collected, licence prices are compared. Yet the real variables that determine project outcomes are set before the very first demo is watched: what state is your data in, how do your processes actually work, is your goal measurable? According to Gartner’s prediction, more than 70% of new ERP initiatives do not fully meet their business goals — and most of these failures are lost not in the software but in the preparation. The checklist below gathers on a single page the seven areas that need to be answered before you start collecting proposals.
How to Use the Checklist
Mark each item with "yes / partly / no". If there are more than two "no"s, it means the next step is not yet software selection but measurement: first take an X-ray of the current state, then make the diagnosis, and leave the treatment (the software and the scope) until last.
ERP Readiness Checklist: 7 Items
1. Management ownership and clarity of goals
Does the project have an owner on the board, and is the answer to the question "why ERP?" measurable? "We want to digitalise" is not a goal; "increasing inventory accuracy" or "shortening the month-end close" are measurable goals. A project without an owner is orphaned at the first difficulty.
2. Is the real state of the processes known?
In most companies, the flow in the procedure document and the flow that actually runs on the ground are different: orders taken by phone, approvals circulating in Excel, person-dependent exceptions. If ERP is set up according to the process on paper, it clashes with the real process on day one. Before you start, the real flow of the 3-5 most critical processes should have been put in writing.
3. Data quality and master data ownership
Do you know the rate of duplicate records in your customer accounts? Do your stock codes have a single standard? Does each master data area (customers, products, suppliers) have an owner? An ERP that goes live with dirty data produces faulty reports faster — a cleansing plan before migration is essential.
4. Scope and prioritisation
"Everything in phase one" is the most expensive sentence. Which processes are in the first phase, which units in later phases? Is the scope prioritised by business impact and written down? A project with unclear scope exceeds its budget through change requests.
5. Are internal resources and the schedule realistic?
An ERP project is not only the consultant’s job: part of your key users’ time must be allocated to the project, and this share must increase during the testing and training periods. A project run "when there is spare time" alongside day-to-day work gets stuck at go-live.
6. Success metrics and a measurement plan
"We went live" is not a definition of success. Which business metric will improve, by how much, and who will measure it? Baseline values should be recorded starting today — you cannot prove that something you did not measure has improved.
7. Change management and training readiness
It is habits, not systems, that resist. Do users know why things are changing, has time and budget been set aside for training, is there a support plan for the first week? An ERP nobody uses is the most expensive report printer there is.
Conclusion: Measure First, Then Choose
The seven items share a single common denominator: ERP success is determined not in the software you buy but in the ground it is built on. And the way to see that ground runs through measurement — X-ray first, then diagnosis, treatment last. If you are curious about your level of readiness, there are two free starting points: the 2-minute ERP Risk Score shows your project’s risk profile, and the Free Digital Maturity Scan your company’s overall level of readiness.
Related articles: Is Consulting That Sells Man-Days Coming to an End? · The X-Ray of AI Promises
To make sure you do not miss new analyses, subscribe to the MindDX-Digital Excellence newsletter.
