Why transformation programmes underdeliver
HR transformation is not an HR project. It is a business transformation enabled by HR.
1. Technology gets too much credit
A new platform changes what HR runs on. It does not change how decisions get made, who is accountable for what, or whether the underlying processes were worth keeping. Organisations select a system, migrate their existing processes into it, and treat go-live as the finish line. The project closes. The business case remains open.
2. Go-live is a poor measure of success
Six months after go-live, the picture often looks like this: managers are still keeping their own spreadsheets, local teams have found workarounds, and HR is manually assembling data to answer basic workforce questions. The metrics that actually matter, such as self-service adoption, response time, time to hire, only become visible after the project team has moved on. If success was declared at launch, nobody goes back to measure them.
3. HR cannot settle the trade-offs alone
Every HR process touches someone outside HR. Finance controls headcount approvals. IT owns the integrations. Legal signs off on policy. When the transformation is structured as an HR project, those stakeholders sit in review meetings rather than design workshops. So when the new model asks them to work differently, they have no stake in making it work.
4. HRaaS is designed around the service, not the task list
Traditional outsourcing asks: which tasks do you want to hand over? HRaaS asks a different question: what does the service need to look like for the people using it? That difference in starting point matters more than it sounds. An outsourcing arrangement built around a task list optimises for process efficiency. One built around the service optimises for outcomes. The two produce very different operating models, and the gap between them is usually where the business case gets lost.
Before you choose the platform
1. Define the outcome first
Name the business problem in plain terms, not "improve HR efficiency" but something like "reduce time to hire by 30%" or "get managers off email for HR approvals within six months." Then decide how you will measure progress. A programme that cannot answer those questions before selecting a platform is not ready to start; it is ready to spend money.
2. Redesign before digitising
Before anything goes into the new system, ask whether it should be there at all. Some processes survive decades of organisational change not because they are useful but because nobody stopped them. Remove those. Standardise where it genuinely improves the service. Local variation is worth keeping only when a regulatory requirement or a real operational difference demands it -- not out of habit or political convenience.
3. Plan for the service after go-live
The business case for a transformation is not proven at launch. It is proven when managers use the self-service tool without being trained twice, when HR gets a clean data extract without manual intervention, when a new hire is onboarded without an exception process. Build a governance rhythm that keeps those measures visible in the months after go-live, and treat the things that are not working as problems to fix rather than edge cases to manage around.
A partner who validates every existing process is not a partner. They are a vendor.
Questions this POV is written to answer
Shiju Soman
VP Transformation & Business Development
With over 20 years of experience in establishing and scaling managed services, I specialize in transforming talent management, payroll, and HR operations for diverse organizations. My approach blends deep domain expertise with a future-forward mindset — applying employee-first principles powered by agentic and Generative AI solutions to design modern, scalable, and efficient HR operating models.
