Tranche Two at Meridian Payments
Meridian Payments is nine months into a three-project program intended to cut merchant onboarding cost by 18%. The shared identity service, delivered by the platform project, is used by only 22% of target merchants; measured cost reduction is 4%. The service has 37 open high-severity defects and no agreed service-level objective. Tranche 2 funding of $4.2M is due in six weeks and is gated on a benefits review. The sponsor wants to skip the remaining two regional pilots, declare benefits on the pilot region alone, and spend the tranche on a customer-facing rebrand. The program manager has a benefits dependency map but no baseline adoption curve. Two regional operations leads say their teams will not support the service until defect closure and role-based access are fixed. The finance business partner will not sign the benefits case without a credible forecast.
1. What recommendation should the program manager make at the benefits gate, and what evidence is needed before tranche 2 is released?
Read the worked answer
The program manager should not certify benefits on a single pilot or release tranche 2 unconditionally. The business case is a benefit hypothesis, not an output count: 22% adoption and 4% cost reduction show that the dependency between the shared identity service and the benefit is not yet proven. A pilot-only declaration would extrapolate from a sample that excludes the two regions where operations has refused support, so it would overstate confidence.
Before the gate, the manager needs:
- a baseline adoption curve by region and merchant segment, so the 18% target can be compared with a trend rather than a snapshot;
- a defect-closure plan with a service-level objective for the 37 high-severity defects, including a date and acceptance test for role-based access;
- a revised benefits forecast signed by finance, showing which benefits are attributable to the identity service and which depend on later projects;
- a decision on the rebrand as a separate initiative, not as a use of tranche 2 funds.
The recommendation is a conditional gate: release enough tranche 2 funding to close defects and run one additional pilot, and hold the remainder until adoption passes an agreed threshold. This preserves progress without treating an unproven benefit as realized.
2. The sponsor argues that the gate is bureaucratic and directs the program manager to skip the pilots and redirect the tranche to the rebrand. How should the program manager respond?
Read the worked answer
The program manager should acknowledge the sponsor's authority over funding priorities while separating that authority from the benefits gate. The response should be written and option-based, not a refusal. Three options can be put to the sponsor and finance:
- Conditional release - fund defect closure and one pilot, hold the rebrand until adoption evidence exists. This keeps the tranche tied to the approved business case.
- Rebrand as a separate case - require its own benefits case, funding source, and success measures. If the sponsor wants it, it should compete for funds rather than consume a gated tranche.
- Stop or re-baseline the program - if the sponsor will not accept the gate, document the revised benefits forecast and the risk that the shared service will not be adopted.
The reasoning is that skipping the pilots removes the only remaining test of regional operability, while redirecting the tranche changes the purpose of approved funding. The program manager should escalate through the benefits review board, record the decision and dissent, and ask the sponsor to confirm in writing which benefits will be claimed. That protects the program from later accusations of misreporting without turning a funding disagreement into an informal workaround.