Buying leadership development in the public sector
What to put in the scope so the program survives the sponsor who bought it.
Public-sector leadership programs rarely fail during delivery. They fail eighteen months later, when the sponsor has moved, the materials are on a shared drive nobody can name, and the cadence has quietly stopped. The delivery was fine. The design assumed continuity that no agency can promise.
Four clauses worth insisting on
- A named internal owner, agreed at scope rather than at handover, who attends from session one and is not the sponsor.
- Materials delivered unbranded and in an editable format, so a successor can run them without a new procurement.
- A facilitation guide written for somebody who was not in the room, and a train-the-trainer session if the scope allows one.
- A closing debrief addressed to the role, not the person — the file has to make sense to whoever opens it next.
What to ask a vendor before you shortlist
Ask what happens if your sponsor leaves halfway through. A vendor who has thought about it will describe the internal owner and the handover artifacts. A vendor who has not will reassure you about their flexibility, which is not an answer.
Ask, too, what is explicitly excluded. A scope that lists only inclusions is a scope with an argument scheduled in it.
Design for the successor, not the signatory.
None of this makes the program better while it is running. It makes it still exist when the people who bought it have gone, which is the only definition of workforce development that means anything at the scale an agency operates at.
