Go-live is behind you. Teams log into the ERP every morning. The project is officially “in production”. And yet, six months later, the promised productivity gains are nowhere to be found. Processing times have not decreased. Data quality remains poor. The finance team still runs its reconciliations in a shared spreadsheet.
This is not a technical problem. It is an adoption problem hidden behind the appearance of compliance.
This article gives you the 8 KPIs you must monitor in the post-go-live phase, how to collect them without overloading your teams, and a structured remediation plan if the signals are in the red.
The Post-Go-Live Paradox: The ERP Works, the Benefits Don’t Arrive
Why ERP Benefits Fail to Materialise: The Real Reason
A technically functional ERP is not an adopted ERP. The distinction is critical, and it is often overlooked during the first weeks after go-live, when the project team is still in hypercare mode and technical emergencies absorb all attention.
The reason benefits fail to materialise is almost always the same: users use the ERP for what is mandatory and monitored, but maintain their parallel tools for what actually matters operationally. They enter orders in the ERP because the approval process requires it, but manage priorities and exceptions in a shared Excel file on OneDrive.
This situation is not trivial. It has direct consequences on ERP data quality (real decisions bypass the system), on actual productivity (double entry, manual reconciliation), and on the project’s return on investment.
Silent Rejection: How to Recognise It Before It Becomes Critical
Declared rejection is manageable: a user who says “I can’t use this module” can be trained, supported, and heard. Silent rejection is more dangerous because it is invisible. Login dashboards are green. Support tickets are rare. And yet, value is not building.
The early warning signs of silent rejection are subtle:
- Requests for reports or exports that users “prefer to run themselves” rather than using the ERP’s BI module
- Excel files created as “temporary” workarounds during go-live that become permanent
- Managers who sign off on ERP processes without actually reading them, because real decisions are made elsewhere
- Low support ticket volume accompanied by high informal request volume (questions asked directly to key users or IT, bypassing the ticketing system)
The 8 KPIs below are designed to make visible what is actually happening in the 3 to 18 months following your go-live.
The 8 ERP Adoption KPIs You Must Monitor
KPI 1: Daily Login Rate by Business Profile
Definition: percentage of active users who log into the ERP at least once per working day, segmented by department and role.
How to measure: extract login logs from the ERP administration console (available natively in SAP, Dynamics 365, Odoo, and most SaaS ERPs).
Alert threshold: a rate below 70% in the first 30 days for daily-use profiles (finance, order management, procurement, logistics) is a red flag. Measure by department — never as a global average. An 80% average can mask an entire department sitting at 40%.
Corrective action: identify departments below the threshold, schedule a 30-minute meeting with their manager to understand blockers, and verify that the team’s key tasks are actually configured in the ERP (if the process is not in the ERP, why would anyone log in?).
KPI 2: ERP Entry vs Parallel Entry Ratio
Definition: inventory of parallel tools and files used for operational data that should be managed in the ERP.
How to measure: targeted field audit. Ask department heads to list all shared files (OneDrive, SharePoint, Google Drive, file servers) created or modified in the 90 days following go-live. Every Excel, Google Sheets, or Access file containing operational data is a workaround.
Alert threshold: more than 3 active operational files per department is a strong signal. A “temporary” file that persists beyond 60 days has become a parallel source of truth.
Corrective action: for each identified file, understand why it exists. Either the corresponding process was not configured in the ERP (a scope or configuration issue), or users do not know how to execute it in the ERP (a training issue). The two diagnoses lead to different actions.
KPI 3: Weekly Support Ticket and Request Volume
Definition: number of tickets opened per week in the support tool, segmented by type (technical blockage, functional misunderstanding, change request).
How to measure: extract from your ticketing tool (Jira Service Management, Freshdesk, ServiceNow, or your integrator’s portal).
Alert threshold: high volume in weeks 1–4 is normal (learning phase). Volume that does not decrease after 8 weeks indicates that training was not effective. Conversely, an abnormally low volume from week 3 onwards may signal that users have given up asking for help and are finding workarounds on their own.
Corrective action: analyse the nature of tickets. A majority of “I do not know where to click” tickets points to additional training needs. A majority of “the process does not cover my case” tickets points to a configuration or scope problem.
KPI 4: Data Completeness Rate
Definition: percentage of mandatory and recommended fields actually filled in ERP records, by module and by process.
How to measure: query the ERP database or use a native data quality report. In Odoo, completeness reports are available by model. In SAP, the Data Quality Management module allows configuring completeness rules. In Dynamics 365, Power BI can generate these reports in a few hours.
Alert threshold: a completeness rate below 85% on key business fields (supplier category, cost centre, account manager) degrades the quality of analytics and management reporting. Below 70%, ERP dashboards become unreliable.
Corrective action: identify fields that are systematically left empty. Either users perceive them as irrelevant (explain why they matter), or the form is too long and complex (review UX with your integrator).
KPI 5: Key Process Turnaround Time vs Pre-ERP Benchmark
Definition: average processing time for a key process (customer order, supplier invoice, purchase request) in the ERP, compared to the pre-deployment baseline.
How to measure: extract timestamps for key steps (creation, approval, closure) from ERP logs. Compare with timings measured during the initial diagnostic phase. If you have no pre-ERP baseline, build one now from department manager estimates.
Alert threshold: if the processing time for a customer order or supplier invoice has not decreased compared to pre-go-live after 3 months in production, users are not mastering the ERP workflow or are bypassing validation steps.
Corrective action: map the steps that take the most time. Bottlenecks indicate either a poorly configured workflow, a lack of training on approval steps, or organisational resistance (a manager who refuses to validate electronically what they used to sign on paper).
KPI 6: Deployed Module Utilisation Rate
Definition: for each module activated at go-live, the percentage of actual usage measured by the number of transactions or records created.
How to measure: list of modules activated in the ERP configuration, cross-referenced with transaction volume by module over the last 60 days.
Alert threshold: a module being used at less than 30% of its potential after 6 months in production represents wasted expenditure. It typically signals that the module was not properly trained or does not cover real business needs in its current configuration.
Corrective action: organise a diagnostic session with target users of the module. Three conclusions are possible: the module needs better configuration, users were not adequately trained, or the module does not match the actual need and should be deactivated to reduce licence costs.
KPI 7: User Satisfaction Score
Definition: user satisfaction score for the ERP, measured through a short, regular survey (adapted eNPS format: “On a scale of 1 to 10, would you recommend the ERP to a colleague for your daily tasks?”).
How to measure: monthly survey of 3–5 questions sent by email or directly within the ERP interface (third-party tools such as WalkMe or Whatfix allow distributing these surveys inside the application window). Results must be segmented by department and role, not aggregated into a global average.
Alert threshold: a score below 6/10 in a department signals active resistance. A score between 6 and 7 indicates surface-level adoption. A score above 8 across all departments after 6 months is a realistic and strong indicator of successful adoption.
Corrective action: analyse qualitative verbatims from low-scoring respondents. Recurring themes point to priority workstreams: interface slowness, workflow complexity, lack of training, or functional inadequacy.
KPI 8: Number of Identified Workarounds
Definition: structured inventory of identified workaround practices: shadow IT, double entry, processes executed outside the ERP (by email, phone, or on paper).
How to measure: bi-annual field survey conducted by key users within their department. Each workaround is documented: process concerned, replacement tool used, stated reason, frequency.
Alert threshold: more than 5 active workarounds identified 6 months after go-live signals that the ERP does not cover real needs or training is insufficient. Each workaround represents a data quality loss and a risk of divergence between operational reality and what the ERP sees.
Corrective action: treat each workaround as a backlog ticket: either the ERP must be configured to cover the use case, targeted training is needed, or the process itself needs rethinking.
How to Collect These KPIs Without Overloading Your Teams
Native ERP Analytics
Most modern ERPs offer built-in usage tracking tools. SAP provides UPL (Usage Procedure Logging) within SAP Solution Manager, which traces transactions executed by user and profile. Microsoft Dynamics 365 integrates Power BI natively for building adoption dashboards within hours. Odoo offers activity logs by module accessible from the admin console. Start with these tools before investing in third-party solutions.
Third-Party Usage Measurement Tools
When native analytics are not sufficient, digital adoption platforms allow you to go further. WalkMe, Whatfix, and ClickLearn integrate directly into the ERP interface and enable not only usage measurement (which features are used, how long each task takes), but also the delivery of contextual interactive guides for struggling users. These tools are particularly effective for ERPs with complex interfaces (SAP ECC, Oracle EBS).
The Manual Method: Field Audit
Twice a year, run a 2-day field audit in each impacted department. Objective: observe, not interview. Sit next to a user and watch how they actually work. In two hours you will discover what six months of support tickets would never have revealed.
4-Step Remediation Plan When Adoption Falls Short
Step 1: Diagnostic by Business Profile (Weeks 1–2)
Analyse the 8 KPIs by department. Identify the 2 or 3 departments with the most difficulty. Meet with department heads and their key users to understand the specific blockers. Do not try to fix everything at once: prioritise the processes most critical to the business.
Step 2: Role-Specific Targeted Training (Weeks 3–6)
Abandon generic sessions. Build training blocks of no more than 2 hours, on a single specific process, for a single specific role. The procurement manager does not need training on payroll management. The accountant does not need to understand the CRM module. Training precision is directly correlated with retention.
Step 3: Network of User Champions (Weeks 7–10)
Identify in each department a user who masters the ERP well and commands the respect of colleagues. Train them in depth, free up 20% of their time, and appoint them as their department’s ERP champion. This champion network is more effective than any internal communications campaign.
Step 4: UX Configuration Review with Your Integrator (Weeks 11–13)
If KPIs remain in the red despite training and champions, the root cause is probably functional: a poorly configured process, an overly complex workflow, or an interface that does not match operational reality. Engage your integrator for a targeted configuration review on the struggling processes. Not a full overhaul — but focused adjustments on the friction points identified during the field audit.
Case Study: 90-Day Action Plan for a Mid-Sized Manufacturer with 200 Employees
Consider a mid-sized manufacturer with 200 employees in industrial production. Go-live was 6 months ago with 3 modules deployed: finance, procurement, and production. The project is officially “in production”, but the Operations Director reports that order lead times have not changed.
The 8 KPIs measured and their results:
| KPI | Measured Value | Status |
|---|---|---|
| Daily login rate | Finance 92% / Production 41% | Production alert |
| Active parallel spreadsheets | 7 active files in production | Alert |
| Weekly support ticket volume | Stable at 12/week for 3 months | Alert (not declining) |
| Data completeness | 71% (production orders) | Alert |
| Order lead time vs pre-ERP | Unchanged (−0%) | Alert |
| Module utilisation rate | Finance 88% / Production 34% | Production alert |
| User satisfaction score | Finance 7.8 / Production 4.2 | Critical production alert |
| Identified workarounds | 11 processes running outside ERP in production | Critical alert |
The diagnosis is clear: the production module was not adopted. The following 90 days focused exclusively on the production department.
Actions deployed and results at 90 days:
- Weeks 1–2: 3-day field audit on the shop floor. Finding: team leaders had never received training on entering production orders, and the module had been configured according to an ideal workflow that did not reflect shop floor reality (mid-run material additions not accounted for).
- Weeks 3–6: 4 training sessions of 2 hours each on real-world cases, led by the finance key user who had prior production experience. Module configuration adjusted to include mid-run material additions.
- Weeks 7–10: 2 team leaders appointed as production ERP champions, with 20% of their time freed up.
- Results at 90 days: production login rate up to 76%, active Excel files reduced from 7 to 2, production satisfaction score up to 6.1, production order processing time reduced by 18%.
Go Further
To structure remediation on the human side, our 8-step ERP change management plan provides a complete operational framework from stakeholder mapping through to long-term anchoring.
If the KPI audit reveals a training problem, our ERP user training guide details how to build a programme by profile and by role.
Finally, if your post-go-live is still in the technical stabilisation phase, our 90-day post-go-live checklist helps you secure the production environment before moving on to adoption optimisation.
