Operations Won't Take the Keys: Transition Readiness at the Final Gate
A transit authority's $120M fare-collection program has delivered all five component projects within tolerance. The final program gate is in ten weeks. The projected benefits - $6M per year in reduced fare evasion - depend entirely on the operations division running the new analytics and enforcing the new inspection regime. The operations director has refused to accept handover: the staffing model for the analytics team was never funded, no operations staff have been trained, and the transition plan was authored by the vendor without operations sign-off. The program sponsor wants to close on schedule because "the technology works."
1. What should the program manager assess before the final gate, and against what criteria?
Read the worked answer
The gate is not about whether the technology works; it is about whether the benefits are deliverable after the program team leaves. That requires a transition/operational readiness assessment, evaluated against pre-agreed criteria:
- Capability - is the receiving organization staffed, funded, and trained to operate the new analytics and inspection regime? Today: no on all three.
- Ownership - has a named operations owner accepted accountability for each benefit, in writing?
- Sustainment - is there a funded support model, service levels, and a benefits measurement process that survives demobilization?
- Benefit dependencies - the $6M evasion reduction requires behavior change in the field, not just a system; is the enforcement policy approved?
- Knowledge transfer - vendor-authored plans without receiving-organization sign-off are proposals, not plans.
Readiness criteria should have been defined at program definition. If they weren't, the program manager defines them now and gets them ratified before the gate - not after.
2. The sponsor directs the program manager to close the program and note the transition as an operations risk. What is the appropriate response?
Read the worked answer
The program manager should not silently comply, and should not refuse. The move is to convert the directive into a documented governance decision with consequences attached.
Concretely:
- State the consequence in benefit terms: closing now transfers an unfunded, untrained capability to operations, which puts the $6M annual benefit at risk in year one and probably beyond.
- Put the decision in front of the program's governing body, since accepting residual risk of this size is a board-level call, not a sponsor-level one.
- Offer the middle path: close on schedule with conditions - a time-boxed transition period, a funded staffing commitment, a named operations owner, and a defined trigger if the conditions aren't met.
- Record the sponsor's directive and the program manager's advice in the decision log either way.
If the board accepts the risk, the program manager documents it and proceeds. Governance exists to make risk acceptance explicit and owned - not to give the program manager a veto.
3. Assuming the gate is deferred, what does the program manager do in the next ten weeks?
Read the worked answer
Use the deferral to close the actual gap, not to re-polish deliverables:
- Fund the capability - take the analytics staffing business case to whoever controls the operations budget; without money, everything else is cosmetic.
- Rebuild the transition plan with operations - the vendor draft becomes an input, co-authored and signed by the receiving director, with named roles and dates.
- Train and rehearse - schedule training and run at least one enforcement cycle in a live corridor so readiness is demonstrated, not asserted.
- Re-baseline the benefits curve - if evasion reduction now starts two quarters late, forecast the reduced year-one benefit and adjust the benefits register rather than pretending the original curve holds.
- Re-set gate criteria and date - a new gate date with objective readiness criteria, reviewed by the governing body.
The exam distinction: deferring a gate is a legitimate control action. Closing a program whose benefits have no owner is an abdication dressed as schedule discipline.