Bringing multiple businesses onto one platform—from hire to separation

Bringing different businesses onto a common path

When I joined Alembic Pharmaceuticals in 2025, the HRMS platform and implementation vendor had already been selected. The challenge was turning that decision into a workable enterprise-wide solution for a complex, multi-entity business.

Each entity had developed its own HR policies, rules, preferences, and workflows over time. Bringing them onto a shared platform meant more than deploying an application. It required stakeholders to reconsider established ways of working, agree on common practices, and distinguish essential business requirements from differences that could be standardized.

I conducted requirements-gathering sessions with stakeholders and HR representatives across entities to understand existing workflows, document business needs, and identify commonalities and differences. I maintained project documentation, captured meeting minutes and decisions, and kept relevant documentation accessible to stakeholders.

Working with the implementation vendor, I helped translate business requirements into an implementable solution—evaluating where standard processes could work and where specific business needs required further consideration. The objective was a common operating model without overlooking legitimate business requirements.

The transformation covered the employee lifecycle, from recruitment and onboarding through employee movements, promotions, transfers, confirmations, training-related transitions, probation management, and separation. Delivering this breadth of functionality required a coordinated view of business rules, workflow dependencies, system integrations, and implementation priorities.

Payroll and Time & Attendance introduced further complexity because employee and attendance data can directly affect salary processing. Integration planning required careful consideration of system connections, data flows, downstream impacts, and the sequencing of integration activities.

Governance, delivery, and stakeholder alignment

Alongside requirements and implementation coordination, I managed programme governance and executive communication. I prepared progress reports and presentations for CXO-level stakeholders, tracked risks and dependencies, documented decisions, and maintained visibility into matters requiring leadership attention.

I also led steering committee meetings, bringing programme progress, challenges, outstanding decisions, and stakeholder expectations into a structured forum for alignment and direction.

UAT, training, and business readiness

A successful implementation depends on more than configuring and deploying a system. Business users need to understand new workflows, validate that they work as intended, and feel confident using them in their day-to-day responsibilities.

I coordinated multiple User Acceptance Testing (UAT) and training sessions to help business stakeholders validate workflows, understand system behaviour, identify issues, and prepare for adoption.

As the platform was rolled out to users, I supported the development of training materials and videos that were uploaded to the Learning Management System (LMS), making learning resources accessible beyond live sessions. I also provided go-live support, helping users navigate new processes, address issues, and transition to the platform.

My role and contribution

My contribution centred on connecting business expectations, technology delivery, and organizational readiness. The implementation vendor was responsible for platform implementation; I worked across business and technology stakeholders to keep the programme aligned and moving forward.

• Business requirements and process alignment: Facilitating requirements-gathering sessions, documenting entity-specific workflows, comparing requirements, and helping stakeholders work towards standardized processes.
• Vendor and solution coordination: Working with the implementation partner to evaluate requirements, clarify configuration needs, and coordinate implementation and integration dependencies.
• Programme governance: Maintaining project documentation, meeting minutes, decision records, risks, dependencies, and progress reporting.
• Executive communication: Preparing CXO-level presentations, managing stakeholder expectations, and leading steering committee meetings.
• Testing and readiness: Coordinating UAT and training sessions to validate workflows and prepare business teams for rollout.
• User adoption and go-live support: Supporting training content creation, LMS-hosted training videos, and go-live assistance to help users transition to the new platform.

My focus was not simply to monitor milestones. It was to create clarity across a complex stakeholder environment, ensure decisions were documented and visible, and connect business requirements with implementation, governance, and adoption activities.

What this work represents to me

Enterprise transformation is rarely just a technology problem. The harder work often lies in aligning people who have valid but different needs, creating clarity where requirements conflict, and turning discussions into decisions an organization can implement.

This project reinforced my belief that successful technology delivery depends on four things working together: a shared understanding of the business, disciplined execution, transparent governance, and effective user adoption. The strongest transformation outcomes emerge when technology, operating processes, stakeholder alignment, and the experience of the people using the system are considered together.