Why governance makes the difference in implementing your HR system

On paper, your plan looks solid

Governance doesn’t have the most exciting reputation. People often picture steering committees, extra documents, and more meetings. But that’s not what it’s really about. The real question is: how do you keep the project on track once things start to rub and shift?

And things almost always start to rub. A prerequisite project runs late. A key decision doesn’t get made. Someone wants to change direction halfway through. Or a “small” extra wish pops up.

That’s when you discover how solidly your project was set up.With a house, you see it immediately. Everything looks perfect on paper, until the client decides during construction that they want an extra room or a bigger bathroom. Suddenly the schedule for that part shifts, and so does everything scheduled later in the project. The impact on budget, risks, and responsibilities can be huge. It works exactly the same with an HR system.

Governance in an implementation simply means setting clear rules for collaboration, decision-making, and adjustments. Who decides what? How much freedom does the project team have? When do you escalate? And when should you adjust the original plan?

Where things often go wrong

A lot of trouble starts with an understandable thought: “We’re paying, so we decide.” The reality is you can’t make changes at any moment without consequences. Adding new wishes during the build phase reopens that stage. The schedule comes under pressure, risks change, and the project approach needs to be reviewed again. That makes the project plan a living document with multiple versions over time.

Another common issue is unclear roles. In most implementations, three parties sit at the table: the client, the software supplier, and the implementation partner. If it isn’t crystal clear upfront who is responsible for what, finger-pointing starts as soon as something deviates from the plan. That greatly increases the chance the project stalls.

That’s why governance isn’t a side issue when realizing an HR system. It’s how you prevent the project from getting stuck when reality pushes back. And that steering looks different in every phase.

Phase 1: Getting clear on what you’re building

The first phase is about gathering requirements. What do you actually want to achieve? In the house analogy, this is when you decide how many rooms you want, how big the house should be, what your budget is, and which wishes you have. Plenty can still be on the table here, including wishes that may drop later.

During an HR system implementation, you ask the same kinds of questions. What do you want to accomplish? What’s in scope and what’s out? What’s your target timeline? Are there hard deadlines? What other projects are running at the same time? What does your current and future IT landscape look like? And at least as important: what do you want to spend, and where is the absolute limit if things get tough?

That last point often stays undiscussed. Many organizations know what they want to invest but not how much flexibility they have. Yet that’s exactly the information you need when changes arise along the way.

The answers from this phase also determine what kind of governance fits. Not every project is the same, and not every organization works the same way. Some want everything fully thought out upfront and then executed at speed. Others want to keep influence during execution and stay able to adjust choices. Both are possible, they just require a different project setup.

Phase 2: This is where you set the ground rules

In the preparation phase, governance for your implementation becomes concrete. You’re not just making a plan for the HR system—you’re also planning what happens when reality deviates from it.

How will you handle setbacks? What do you do when wishes change? Which decisions can the project manager make themselves? When does something need to go back to the steering group? And what does scope expansion actually mean in practice?

That last one often sounds harmless. “Just add it quickly,” you think. But just like in a house renovation, a change rarely affects only one part. What seems like little work for the plasterer can mean the carpenter can’t start on time. That’s why you need to agree upfront when a change fits within the existing framework and when you need to go back to the preparation phase to recalculate the impact.

The same applies to the project plan. It’s not a document you create once and then let gather dust. In a well-governed project, it moves with you. If something essential changes along the way, you should be willing to revise it, not because the project is failing, but because you want to stay in control.

Phase 3: Now you find out if your agreements hold up

During the realization phase, governance comes under pressure. What happens if a milestone isn’t met? What if the client doesn’t deliver something on time? What if a supplier is delayed? What if a decision is missing while other activities depend on it?

In the house analogy, this is when construction is underway and you discover whether the preparations actually work in practice. What do you do if the contractor is waiting for a decision on the bathroom? Or if a part isn’t delivered on time? Does everyone just wait, or is it clear upfront who decides and how you move forward?

In this phase, governance needs to deliver two things: clarity on responsibilities and room to intervene in time. You want to know exactly where something is stuck, and you want to be able to act before the whole project grinds to a halt.

Take the test plan as an example. If the client is supposed to deliver it but doesn’t do so on time: what then? Do you wait? Escalate? Or did you already agree that another party can temporarily take over to protect the schedule? If you didn’t arrange this in advance, you’re too late when it actually matters.

Good governance doesn’t prevent problems from arising. It ensures you know exactly what to do when they do.

Phase 4: Go-live needs short lines of communication

The go-live of an HR system requires yet another form of steering. In the house analogy, the house is built but not yet livable. Everything has to happen in the right order. You don’t turn on the water until the faucet is connected.

The same applies to an HR system. Data needs to be migrated, checks need to be performed, and steps must follow the right sequence. This is when you need short lines, sharp direction, and people who are allowed to make decisions when something deviates from the plan.

This is no time for long meetings. Sometimes a choice needs to be made immediately. That’s why you want to have agreed in advance who can make that call, within what boundaries, and how accountability will be handled afterward.

And then there’s the toughest question: when is it good enough to go live? Especially with processes like payroll, this isn’t a casual discussion. If you need to go live on January 1, you can’t start negotiating acceptance criteria and risks at the end of December. Those frameworks need to be on the table earlier. To set the right go-live criteria, it’s smart to define KPIs, such as deciding upfront that 90% is good enough for go-live. That way, a test score of 85% before go-live still gives peace of mind, knowing you’ll likely be at 95% three months after going live. Then you know you’re staying on schedule.

Phase 5: Done? Then something new begins

With a house, this is the moment the keys are handed over. The contractor walks out and the house is yours. But new ideas often come quickly: let’s add solar panels, install a hybrid heat pump, or put a water connection in the shed. It works the same with an HR system. Why not add that module, include that extra wish, or redesign that piece of functionality?

In both cases, one thing is true: you’re no longer finishing the original project. You’re starting something new, with new considerations, new risks, and therefore a new approach.

No governance? Then you’re building on hope

As long as everything runs smoothly, governance can feel like extra work. But the moment something rubs, you don’t want to be figuring out who decides, who adjusts course, and what that means for everything else.

That’s the core message. Good governance doesn’t slow down an HR system implementation. It prevents you from having to improvise at the wrong moments. Without clear ground rules, you don’t build faster—you mainly increase the chance of losing control along the way.

Want to keep a firm grip on building your HR system? At worldofwork™ we’re happy to think along with you about governance, within your resources and budget. With our golden rules for HR system implementations, we help you make the right agreements upfront so your project stays on course, even under pressure.