Multi-SOW programme coordination, at scale.

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

Eighteen months, 100,000 staff, multiple SOWs.

The client was a major Australian state government department. The transformation was a multi-tranche SAP SuccessFactors HCM implementation. The workforce was around 100,000 teachers, principals, and support staff distributed across an entire state. The programme had been commissioned with an 18-month delivery horizon and funded across multiple SOWs.

Multi-SOW funding is the standard model in Australian government. It exists for sound reasons. It allows incremental commitment, manages financial year boundaries, and lets each tranche be re-scoped against actual progress. The trade-off is governance complexity.

Each SOW has its own deliverables, its own success measures, its own commercial reporting cadence. The programme as a whole has a coherent outcome it is trying to achieve. The two views do not always agree. When they diverge, the SOW view tends to win, because the SOW is what gets reported and what gets funded. The programme view quietly recedes.

Multi-SOW programmes drift at the boundaries.

Each SOW reports green inside its own definition. The integrated outcome the business case described is no one SOW's responsibility. Scope accumulates at the boundaries. Decisions that need to span SOWs get deferred to the boundary, then deferred again past it, then absorbed into the scope of the next SOW where they were not budgeted.

By the time anyone notices, the programme has drifted. Not because any single SOW failed. Because the boundaries between them were never governed.

Public-sector multi-SOW programmes are particularly exposed because the SOW reporting cycles are formal and visible. The integrated programme view rarely has the same formality. Sponsors trust the SOW reports because they are what they are given. The integrated view is left to the programme team, who are themselves shaped by the SOW cycle.

Three coordination disciplines, held across all 18 months.

Three coordination disciplines were established at the start of the engagement and held consistently across the 18-month horizon.

1. 01
   A single integrated programme view, separate from any SOW.A programme-level view of scope, milestones, risks, and benefits maintained continuously, independent of which SOW was active. Reviewed at every steering committee. The SOW reports were treated as inputs to it, not as substitutes for it.
2. 02
   Boundary-conscious decision-making.Every decision was tested for cross-SOW impact before it was made. Decisions that affected the next SOW were documented and the impact made explicit before the boundary, not absorbed into the next tranche silently. The discipline is small. The accumulated effect is significant.
3. 03
   Stable governance forums across SOW boundaries.The steering committee did not change shape between SOWs. The membership stayed consistent. The agenda format stayed consistent. The meeting cadence stayed consistent. SOWs are commercial constructs. The governance forum belongs to the programme, not to the SOW.

None of the three disciplines required additional resourcing. They required the discipline to operate them every cycle, including during the periods between SOWs when it was easiest to relax.

A coherent programme across an entire state workforce.

The programme delivered against its 18-month horizon. SAP SuccessFactors landed across more than 100,000 staff. Each SOW closed against its own deliverables and against the integrated outcome the business case had described. Operations across the state workforce continued without disruption.

The less visible outcome was as important. The departmental governance forum that ran this programme was a working governance body by the end of it. The same group of people who had run this transformation were better positioned to run the next one. The SOW model had not eroded the governance. The governance had absorbed the SOW model and used it.

Multi-SOW programmes are remembered for what they delivered. The disciplined ones are also remembered for what they did not lose at the boundaries.

Multi-SOW programmes do not fail at the SOWs. They fail at the boundaries between them.

Independent governance owns the programme view that no individual SOW is responsible for. That ownership is what keeps an 18-month, 100,000-staff transformation coherent across a funding model that was designed for control rather than coherence.

More on the practice behind this case study.