Core-system replacements are expensive, disruptive, and often underestimated.
Management may blame the system for poor reporting, inconsistent processes, manual work, or delayed decisions. The actual problem may be weak data, unclear ownership, poor configuration, or processes that were never defined.
The company should diagnose the operating issue before selecting new software.
Identify the real problem
Common concerns include:
- reporting is slow;
- data is unreliable;
- systems do not connect;
- manual spreadsheets are widespread;
- inventory is inaccurate;
- customer information is fragmented;
- controls are weak;
- the system is no longer supported;
- growth requires functionality the system cannot provide.
Each concern should be tested.
Determine whether the current system can be improved
Before replacement, assess:
- configuration;
- user training;
- data quality;
- integrations;
- unused functionality;
- reporting tools;
- support;
- process ownership.
A poorly implemented new system may recreate the same problems at greater cost.
Define the business case
The project should state:
- problems being solved;
- expected operating benefit;
- cost;
- implementation time;
- required management capacity;
- data risk;
- customer impact;
- expected return;
- conditions for success.
“Modernization” is not a complete business case.
Fix processes before automating them
Software will not resolve unclear responsibility or uncontrolled exceptions.
The company should define:
- process owner;
- required data;
- approval points;
- decision rights;
- exceptions;
- reporting;
- controls.
Do not automate a process management does not understand.
Establish project governance
The project needs:
- executive sponsor;
- business owner;
- project manager;
- technical lead;
- functional owners;
- implementation partner;
- decision process;
- budget control;
- risk register;
- testing plan.
The project cannot be delegated entirely to IT or the software provider.
Prepare data properly
Data migration should address:
- ownership;
- accuracy;
- duplication;
- retention;
- security;
- mapping;
- testing;
- reconciliation;
- historical access.
Poor data can undermine the new system before launch.
Plan adoption
Employees need:
- role-specific training;
- clear procedures;
- support;
- realistic transition time;
- accountability for use.
Allowing employees to continue operating through old spreadsheets may prevent the new system from becoming the source of truth.
Measure the outcome
After implementation, review whether the system improved:
- reporting speed;
- data quality;
- customer delivery;
- control;
- inventory;
- working capital;
- employee productivity;
- decision-making.
A core system should support the company’s operating model. It should not become the operating model.