Services Strategic PMO Governance & Advisory Project Health Check Client-Side Delivery How We Work Industries Government Mining & Resources Navigate Why Us Articles Case Studies Assessment About Get in Touch
Case Study

Closing a three-year HRIS programme was the win.

A Victorian not-for-profit health and community services provider engaged Rydel Group for independent governance and advisory across a three-year Dayforce and RPA programme. The decision the engagement reached was that the Dayforce stream should not go live. That decision protected the investment.

Case study, anonymised. The client is described by sector, state, and scale. The platforms and dates are accurate. The decisions are real. Some sequencing has been simplified for readability.

01. The situation

A three-year programme, two streams, one quiet doubt.

The client was a Victorian not-for-profit operating in health and community services. The programme had been running for over two years when Rydel was engaged. It had two parallel streams.

The first stream was a robotic process automation deployment to remove manual effort from a high-volume back-office function. That stream was tracking close to plan.

The second stream was a Dayforce HRIS implementation intended to consolidate workforce management across the organisation. The platform vendor had been selected. The system integrator had been engaged. Configuration was in flight. The programme was on track to go live within twelve months. There was a quiet doubt, surfacing from inside the organisation, about whether the platform would actually deliver what the business case required.

02. The pattern that emerged

Product fit gaps that SI reporting was not surfacing.

Independent advisory has a structural advantage in moments like this. It can ask questions without commercial consequence. It can test the answers without diplomacy. It can hold the answers up to the business case without softening them.

The pattern that emerged was familiar. Configuration workshops were producing answers, but the answers were forcing the client to change its operating model to fit the platform rather than the other way round. Each individual configuration decision looked reasonable on paper. The accumulation of those decisions was a different operating model from the one the business case had paid for.

SI reporting was not surfacing this. SI reporting is, by design, a delivery instrument. It tracks whether configuration is complete, whether testing is on schedule, whether milestones are being met. It does not test whether the thing being built will deliver the benefit the business case promised. That test belongs to the client. In this engagement, the client did not have the in-house experience to run that test. The independent advisory function was engaged to fill the gap.

03. The decision

Three tests before recommending closure.

Recommending the closure of a programme that has already absorbed years of investment is not a decision to make on suspicion. The recommendation went to the steering committee only after three tests had been run.

  1. 01
    Could the gap be configured around?Detailed product fit assessment with the platform vendor and the SI. The conclusion was that the gap was structural to the platform, not a configuration choice. Customisation paths were available but at a scale that would compromise vendor support and upgrade roadmap.
  2. 02
    What would the operating model look like at go-live?A walk-through of the as-configured operating model with the affected business owners. The walk-through made the cumulative impact visible in a way that workshop-by-workshop reviews had not. The business owners did not recognise the operating model they were being asked to adopt.
  3. 03
    What is the cost of going live versus closing?A side-by-side commercial assessment. Going live would require multi-year customisation, ongoing remediation, and a high probability of revisiting the platform decision within five years. Closing the Dayforce stream would crystallise sunk cost but stop further outflow and free the organisation to reset the platform decision with the lessons of three years of work.

The recommendation went to the steering committee with the three tests documented, the evidence underneath each one, and a clear ask. The steering committee made the decision in one cycle. The Dayforce stream was closed. The RPA stream continued to go-live.

04. The outcome

The closure protected the investment.

The RPA stream went live and delivered the back-office benefits the business case had promised for that scope. The Dayforce stream was closed before the costliest phase of the build. Sunk cost was real but bounded. The downstream costs the closure prevented were larger than the costs the closure crystallised.

The board signed off the closure as a governance outcome, not a programme failure. That distinction matters. A programme that goes live with a platform that does not fit the business case is the failure mode. A programme that closes before that point, on the basis of evidence and a structured decision, is the governance mode working as intended.

Three years later, the organisation has reset its platform thinking with a clearer view of what it actually needs and what the market actually offers. The investment that would have been spent on a misfit go-live is available to fund a better one.

The principle

The most expensive programmes are the ones that should have been stopped earlier.

Independent governance is not about preventing programmes from going live. It is about protecting the investment that justifies the programme. Sometimes that means delivering on time and on budget. Sometimes it means stopping. Both decisions require the same thing. Evidence, applied through a structured decision-making framework, by people whose commercial interest is aligned with the client outcome rather than the platform.

Related reading

More on the practice behind this case study.

Service
Governance and Advisory.
Hub
Programme governance consultant Australia.
Article
Why technology implementations fail.
Article
Do you need an independent advisor for a technology programme?
Article
What should a steering committee actually do?
Reference
Glossary: programme assurance.

Sitting with a programme that needs an independent read?

If the question is whether your programme will deliver the benefit the business case promised, that is the question independent advisory exists to answer. We are happy to talk.

Get in Touch