Rapid deployment, disciplined governance.

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

Nine months, 15,000 operational staff, mining sector constraints.

The client was an Australian mining services group with around 15,000 staff working across mine sites, depots, and corporate functions. The decision had been made to consolidate workforce systems onto SAP using a rapid deployment methodology. The target window was nine months from kick-off to go-live.

Mining sector constraints were not negotiable. Operational shift work meant change windows were narrow and weekends were not necessarily quieter than weekdays. Safety and compliance frameworks meant configuration decisions had to satisfy regulator-grade evidence trails. Workforce demographics were spread across remote sites with limited connectivity and across corporate offices with full digital tooling. The same platform had to land cleanly across all of them.

Rydel was engaged for the Governance and Advisory function. The brief was unusual. Most rapid deployments arrive at this point with the governance brief shaped as "keep up with delivery". This one was shaped as "do not let delivery move faster than the evidence justifies".

Speed and discipline are not opposites.

Rapid deployments fail in a predictable way. Pressure on the timeline turns into pressure on the governance. RAG ratings drift toward green. Decisions get made in the corridor instead of in the steering committee. Evidence gets thinner because there is no time to gather it. Risks get reclassified as issues, then as observations, then disappear from the register entirely.

The pattern that worked here was the opposite. Rapid did not mean less governance. It meant the same governance, applied faster. Decisions stayed inside the framework. The steering committee met more frequently rather than less. Evidence requirements scaled down by precision rather than by absence. The risk register was reviewed every cycle, not when something broke.

The reason this works is that governance is not a bottleneck on speed. It is what protects speed from the cost of having to redo work. A decision made well in the steering committee in fifteen minutes saves the cost of an escalation, a rework, and a recovery later in the programme.

Three commitments held throughout the nine months.

Three commitments were made at the start of the engagement and held without exception until go-live.

1. 01
   Decisions in the steering committee, not the corridor.Every material decision went to the steering committee. The committee moved to a fortnightly cycle to keep up with rapid delivery. Decisions were documented with rationale and an owner inside the meeting cycle. Nothing was deferred to the next meeting unless the deferral itself was documented as a decision.
2. 02
   Evidence scaled by precision, not by absence.Evidence requirements for compliance and safety decisions were not relaxed. They were sharpened. Sample sizes shrank but specificity grew. The audit trail had to be regulator-grade at any week of the programme, not just at go-live. This kept compliance functions inside the room rather than waiting at the end of it.
3. 03
   Phased change despite the rapid timeline.Rapid build did not mean a single big-bang go-live. Operational sites went live in phases shaped by shift patterns and connectivity rather than by build readiness. Sites with stable connectivity and standard shift cycles went first. Remote sites and unusual shift patterns went later, with the lessons of earlier waves built in.

None of these commitments were exotic. The discipline was holding all three at once, under timeline pressure, when the path of least resistance would have been to relax any of them.

On time, in framework, with a reusable model.

The programme landed inside the nine-month window. Operational continuity was protected at every phased site go-live. The risk and controls framework remained intact and was adopted by the organisation as the default for subsequent programmes. The audit trail required no remediation after go-live.

The less visible outcome mattered just as much. The steering committee that ran the programme had become a working governance body, not a status-receiving forum. The same group of people who had run this programme were in a stronger position to run the next one. The discipline did not leave when the programme finished.

Rapid programmes are usually remembered for the timeline. This one is worth remembering for what was held inside the timeline.

Rapid is not the opposite of disciplined. The most expensive rapid deployments are the ones that sacrificed governance for speed and discovered the cost later.

Independent governance and advisory protects speed by holding the framework that prevents the rework. The discipline pays for itself inside the timeline, not after it.

More on the practice behind this case study.