ERP strategy & selection
ERP change management: getting people to actually use the new system
Drive ERP adoption in Philippine companies: leadership sponsorship, communication, key users, role-based training, branch rollout support and adoption metrics.
An ERP can be configured perfectly and still fail if people keep using spreadsheets, approvals still happen by chat, and branches find workarounds. Change management is the work of helping people understand why the change matters, learn new ways of working and stick with them. In Philippine companies, where relationships, hierarchy and branch culture strongly influence behavior, it deserves as much attention as configuration.
Why people resist new systems
- Fear of exposure: errors and delays become visible
- Fear of job loss: automation threatens roles
- Comfort with the old way: spreadsheets feel faster
- Extra work during transition: parallel runs and learning curves
- Lack of involvement: decisions made without them
Address these openly. Resistance is information about what people need.
A change management plan
1. Visible leadership
The sponsor explains why the company is changing, what will improve and what is expected. Leaders use the system themselves, for example approving requests and reviewing reports in it.
2. Stakeholder mapping
List groups affected (cashiers, supervisors, payroll officers, accountants, branch managers, approvers) and how their work changes. Plan communication and training for each.
3. Communication
| When | Message |
|---|---|
| Project start | Why we are changing, what to expect, timeline |
| During design | How processes will change; invite input |
| Before training | What training is coming and when |
| Before go-live | Cutover dates, what stops, where to get help |
| After go-live | Wins, fixes, what's next |
Use channels people actually see: town halls, team huddles, the company wall, branch visits (company announcements).
4. Key users
Select key users in each department and branch: respected people who learn early, help test, train colleagues and provide first-line support. Give them time and recognition.
5. Role-based training
Train people on their tasks, with their data, close to go-live. A cashier needs a different course from an accountant. Provide short guides and videos for reference. Test understanding with practical exercises.
6. Remove the old way
Set dates after which old spreadsheets, paper forms and chat approvals are no longer accepted. Without this, parallel systems persist indefinitely.
7. Support after go-live
Provide on-site or remote support in branches during the first weeks, a clear channel for issues (internal helpdesk), and daily check-ins to resolve problems quickly.
Adoption metrics
- Logins and active users by role and branch
- Transactions entered in the system vs. outside it
- Approval turnaround times
- Helpdesk tickets by topic (shows training gaps)
- Process KPIs: close days, payroll corrections, inventory accuracy
Review weekly in the first months and act on laggards with support, not blame.
Branch rollouts
For multi-branch companies, roll out in waves. Use the first branches to refine training and support, then scale. Pair new branches with key users from branches already live.
Where Cirquolus fits
Cirquolus proposals are scoped around your modules, companies, branches, data migration and training needs, and tools such as the employee portal, company wall and helpdesk support communication and adoption. Related: phased ERP rollout and ERP go-live checklist.
Frequently asked questions
What is ERP change management?
The activities that help people understand, learn and adopt new processes and systems, including leadership communication, training and support.
Why do employees resist new ERP systems?
Common reasons include fear of exposure or job loss, comfort with old methods, extra work during transition and lack of involvement.
Who are key users in an ERP project?
Selected staff from each area who learn early, help test, train colleagues and provide first-line support.
How do you measure ERP adoption?
Track active users, transactions inside vs. outside the system, approval times, support tickets and process KPIs.
Bring this workflow to a Cirquolus demo.
Show us your current process, companies and branches. We will map it to the modules you need and propose a realistic rollout.