The Business Challenge
The business situation the organisation faced before the project began.
The organization needed to modernize and standardize HR processes across its head office and growing retail store network, involving more than 1,000 employees.
Previously, employee and HR-related data was not centralized in a single platform, making data consolidation and HR process management more difficult.
The new HRM platform was originally developed for another market, creating significant localization challenges. Indonesian HR processes, particularly payroll and tax-related requirements, differed substantially from the system's existing assumptions and required detailed business analysis and functional alignment.
The implementation also involved a transition period in which the legacy system remained in use while selected HRM modules were introduced, creating additional challenges around data consistency and process alignment.
Why AI Was the Right Solution
Why AI was the right approach — and what alternatives were considered.
A phased implementation approach was appropriate because the organization needed to introduce the new HRM platform while maintaining business continuity.
Migrating all HR processes simultaneously would have created significant operational risk, particularly for payroll and other business-critical processes.
Progressively implementing selected modules allowed the organization to begin adopting the new platform while retaining the existing system for processes that were not yet ready for migration.
The approach also allowed business and technical teams to identify localization gaps and refine requirements before broader rollout.
How the Solution Was Delivered
Discovery, design, development, testing and rollout — the journey, not the tooling.
- 1Gathered requirements from HR and business stakeholders.
- 2Mapped existing and target HR processes.
- 3Performed gap analysis between Indonesian requirements and the existing HRM capabilities.
- 4Identified localization requirements for Indonesian HR processes.
- 5Prepared and reviewed Functional Design Documents (FDD).
- 6Translated complex local business requirements into implementation-ready functional requirements.
- 7Coordinated functional discussions with the Vietnam-based technical team.
- 8Coordinated vendor and stakeholder activities throughout the implementation.
- 9Supported system testing and functional validation.
- 10Supported user training and change management activities.
- 11Supported progressive implementation of selected HRM modules.
- 12Maintained alignment between the new HRM platform and legacy processes that had not yet been migrated.
Key Technical & Architecture Decisions
Architecture, model selection, workflow and trade-offs.
The implementation used a phased HRM adoption approach rather than an immediate full-system replacement.
Key decisions included:
Introduce selected HRM modules progressively.
Maintain the legacy system for processes not yet migrated.
Validate Indonesian business requirements before functional implementation.
Separate local business requirements from the platform's existing country-specific assumptions.
Use Functional Design Documents to provide clear implementation requirements to the technical team.
Validate system behavior through functional testing before broader adoption.
Maintain coexistence between the new HRM platform and legacy processes during the transition period.
At the time of the project, payroll remained dependent on the legacy system, resulting in a temporary dual-system environment.
Challenges & How They Were Solved
Obstacles hit along the way and how they were overcome.
Challenge: The HRM platform was originally developed for another market.
The system's existing assumptions did not fully reflect Indonesian HR processes, particularly payroll and tax-related requirements.
Approach: Local requirements were gathered, documented, analyzed, and translated into functional specifications for the technical team.
Challenge: Differences in interpretation between Indonesian business stakeholders and the Vietnam-based technical team.
Some requirements initially appeared straightforward from a system-development perspective but became considerably more complex when applied to Indonesian operational rules.
Approach: Requirements were clarified through business process mapping, gap analysis, functional documentation, and repeated discussions between business and technical stakeholders.
Challenge: New and legacy HR systems had to coexist.
Not all HRM modules were ready for full adoption, while critical processes such as payroll remained dependent on the legacy platform.
Approach: The implementation followed a phased approach, allowing selected modules to be introduced while maintaining existing processes where migration was not yet complete.
User Adoption & Change Management
How users responded — training, change management and feedback loops.
User adoption was supported through business process alignment, functional validation, training, and change management activities.
Users needed to understand not only how to use the new HRM modules, but also how the new workflows differed from existing processes.
The implementation therefore involved:
User requirement discussions.
Functional validation with business stakeholders.
Training support for implemented modules.
Communication of new workflows and system functionality.
Feedback collection during testing and implementation.
Because the implementation was still progressing, adoption was considered an ongoing process rather than a completed transformation.
Business Outcomes & Impact
The measurable outcomes from the underlying AI Deployment — with the story behind them.
Supported HRM implementation and localization for more than 1,000 head-office and retail employees, covering multiple HR processes and establishing a foundation for future HR process consolidation and digitalization.
Business Outcome Categories
The story behind the numbers
The project established the foundation for a more centralized and standardized HRM environment across head-office and retail operations.
Key outcomes during the implementation included:
Selected HR processes were introduced into the new HRM platform.
Indonesian HR requirements were documented and incorporated into functional design.
HR workflows were standardized across multiple process areas.
Localization gaps between the Vietnam-developed platform and Indonesian requirements were identified and addressed.
The implementation created a structured foundation for future HR process consolidation.
The project supported HR digitalization for a workforce of more than 1,000 employees.
The broader operational impact was still developing when the project was ongoing. The legacy system remained in use for processes that had not yet been fully migrated, particularly payroll.
Lessons Learned
What surprised the team, what worked well, and what would be done differently.
- ERP and HRM localization requires business process alignment, not simply system configuration.
- Local regulatory and operational requirements should be identified early in cross-country implementations.
- Clear functional documentation helps reduce communication gaps between business and technical teams.
- Business users should be involved throughout requirements, validation, testing, and adoption.
- Phased implementation can reduce operational risk when replacing a legacy system.
- A technically feasible solution may still fail to meet business needs if local requirements are not fully understood.
- Cross-border implementation requires continuous clarification between local business stakeholders and the technical delivery team.
Future Opportunities
Where this solution could go next.
The implementation created a foundation for further HR digitalization and system consolidation.
Potential next steps included:
Completing migration of remaining HR processes.
Consolidating HR data into a more centralized environment.
Migrating payroll from the legacy platform once Indonesian requirements were fully supported.
Expanding Employee Self-Service adoption.
Increasing automation across HR approval workflows.
Improving HR reporting and analytics.
Reducing dependency on parallel HR systems.
Establishing a more scalable HR platform for continued workforce growth.
Professional Reflections
Guidance for another builder tackling a similar problem.
This project reinforced that enterprise system implementation is rarely just a technical deployment.
A system developed for one country can contain assumptions about processes, regulations, terminology, and business rules that do not translate directly into another market.
The most challenging part was often not identifying what the system could do, but translating the actual business reality into requirements that the technical team could understand and implement.
As a Business Solution Manager, the project strengthened my ability to bridge business stakeholders and cross-border technical teams, particularly when requirements involved complex local processes such as payroll and taxation.
It also reinforced the importance of validating requirements early rather than assuming that a standardized system can be applied directly across different markets.