Having sat on multiple sides of HR transformation projects, from inside HR teams, inside a software vendor, and now as an independent consultant, certain problems come up again and again. Almost none of them are really about the technology. They are about planning, people and process.
No clear business case
When a project starts without a properly agreed business case, it becomes very difficult to make good decisions later, because there is no shared understanding of what success actually looks like. Scope changes get approved without anyone checking whether they still serve the original goal, and budget conversations become guesswork.
Scope creep
Almost every implementation faces requests to add extra functionality once the project is underway. A little of this is normal, but without a clear process for evaluating and approving changes, small additions accumulate into a project that looks nothing like what was originally planned, on a timeline nobody agreed to.
Underestimating data migration
Data is consistently the most underestimated part of any implementation. Historic records are incomplete, formats are inconsistent across systems, and ownership of cleaning the data is often unclear. Projects that treat data migration as a late stage technical task, rather than an early and ongoing workstream, tend to run into serious delays.
Insufficient testing
Testing is one of the first things to get compressed when a project falls behind schedule, which is exactly the wrong response. Issues found during proper testing are inconvenient. The same issues found after go live are expensive, and considerably more damaging to trust in the new system.
No real change management
A system can be technically perfect and still fail if the people who need to use it were never properly prepared, trained or brought into the reasoning behind the change. Adoption problems that appear after go live are almost always the result of change management that was treated as an afterthought rather than a core part of the project.
Lack of executive sponsorship
Projects without a visible, engaged sponsor at leadership level tend to lose momentum whenever they hit a difficult decision or competing priority. Sponsorship is not a name on a project charter, it is active involvement when things get hard.
Treating go live as the finish line
Perhaps the most common mistake of all is winding down project support the moment the system goes live. The weeks immediately after launch are exactly when issues surface, questions pile up, and habits are formed, good or bad. Support needs to continue well beyond go live day.
Most of these problems are entirely avoidable with the right planning and governance from the start, which is exactly what the Discover and Define stages of the Pivot Method are designed to catch before they become expensive.
Ready to talk this through
Every organisation is a little different. Book a no pressure discovery call and we can look at how this applies to yours.
Book a Discovery Call