How do you get the board to agree to replacing an HR system?

Most boards don’t turn down a new HR system because they think the current one is good. They turn it down because the proposal in front of them looks like disruption with an unclear payoff, while renewing looks like doing nothing at all. I think that’s the wrong comparison, and the way to get agreement is to change it: show the board what staying put is really costing, how the change could be phased, and how the people side will be handled. Then they’re weighing up a plan rather than a risk.

Why does the board keep choosing to renew?

Mostly for fair reasons. A long-standing HR system usually covers a lot of ground, and removing it touches payroll, rotas, onboarding, reporting and the managers who use it every week. A renewal needs a signature; a replacement needs budget, time and attention from people who are already stretched. Faced with that choice one contract at a time, renewing is the rational answer. And the bigger the business, the harder it gets. More sites and more stakeholders sit on every system, so any change feels enormous.

The board isn’t wrong to be cautious, and the system wasn’t a bad choice when it was made. What’s missing is the context that would let them compare staying put with changing on equal terms.

What does the board need to see that a single-system proposal doesn’t show?

The people side of a multi-site hospitality business rarely runs on one system. HR, rotas and time and attendance, payroll, recruitment and learning often sit with different teams, on different contracts, renewing at different times. Each one, judged alone, looks too embedded to touch.

Put together, the board can see:

  • every system that touches your people, including the ones other teams own

  • what they cost in total, and where they overlap

  • how they connect, and where data is moved by hand between them

  • when each contract ends, which sets the realistic order for any change

  • a transition plan that phases the change so no single step is as disruptive as it looks in isolation

That last point is usually what changes the conversation. A replacement that looks too disruptive on its own can look manageable once it’s one stage in a sequence the business has planned for.

How do you show what staying put really costs?

The cost of staying put is rarely the licence fee. It’s the gap between how the business works now and how it worked when the contract was signed. Multi-function platforms on long contracts tend to drift out of step as the business grows, adds sites or changes how it operates, and the people team quietly absorbs the difference. In my experience, that’s where the real cost sits: in the manual processes teams design purely to work around the quirks of a system that no longer fits the business. Every one of them takes time to run, and every one has to be unpicked before anything can be automated.

There’s a forward-looking cost too. If the business wants to automate more over the next few years, the board needs to know whether its current processes and data can support that. Automating a process that isn’t documented, or that runs differently at every site, only automates the guessing. If the systems are holding that back, the cost of staying put grows every year the business delays.

What will the board ask that the business case doesn’t answer?

Usually: who is going to do this, and will people actually use it? The technical side of an implementation comes with a supplier, a plan and a deadline. The people side, from manager buy-in to how teams are told and who owns the system after launch, has none of that structure, so it’s the part that slips first.

A proposal that answers this before it’s asked carries much more weight. It shows the board that the change has been thought through as something the business will live with, not just something it will buy.

Bringing it together

A board that turns down an HR system change is usually turning down an incomplete picture. Show them the whole stack, an honest view of what staying put costs and a phased plan that covers the people side, and you’re asking for a business decision rather than a leap of faith.

This is the work I do through yellow’s Roadmap. I review every system that touches your people, map the costs, overlaps, connections and contract dates, set out which processes to remove, redesign or automate, and present the plan to your leadership team.

If you’re facing this conversation with your own board, book a 30-minute call with me. We’ll talk through the challenge you’re facing with your people systems, and you’ll come away with a clear sense of how I’d approach it and whether it’s worth taking further.

Next
Next

Hybrid Working in 2026: Why the policy matters less than the consistency behind it