Transformation-Office Closure Blueprint Director

The mandate

An eight-year transformation has delivered core pension calculation, digital service and data changes, but its central office still arbitrates defects, funds temporary controls and owns decisions the operating functions were meant to absorb. Closing it abruptly would strand member risks; extending it unchanged would institutionalise shadow management. The committee needs a bounded transition design, not another programme health review or a case for indefinite extension.

The required deliverable is a transformation-office closure blueprint containing a residual-obligation inventory, benefit-evidence ledger, decision-rights transfer map, control-owner matrix, capability test, funding unwind, archive design and ninety-day post-closure watch plan. It must distinguish completed scope from accepted debt, temporary workaround from enduring control, and accountable acceptance from the mere reassignment of an overdue action in portfolio software.

Four monthly milestones structure the work: month one establishes the defensible residual baseline; month two tests receiving functions and assigns transfer conditions; month three runs two simulated failures after proposed closure; month four delivers the board blueprint, signed acceptance dossiers and closure calendar. Billing follows those outputs, with unresolved fiduciary, member or regulatory issues carried visibly into the decision rather than averaged into programme completion.

Acceptance occurs when each receiving executive can explain the obligation, control, capacity, funding and escalation inherited; Internal Audit can trace evidence; and the oversight committee signs one of close, close-with-conditions or retain for every office capability. The client returns one consolidated evidence gap list within seven business days of each dossier. Final acceptance requires successful response to an unseen member-calculation defect without reactivating the central office.

The organisation provides the complete project register, benefit cases, risk and issue logs, vendor obligations, control library, audit findings, workforce plan, cost ledger and access to named receiving executives during week one. Delivering residual projects, remediating the pension platform, renegotiating supplier contracts, changing benefits or selecting permanent leaders is excluded. The consultancy designs and tests transfer; management owns the resulting commitments.

Why this is external work

The incumbent office cannot impartially decide which of its own capabilities are necessary, while receiving functions have incentives to resist unresolved obligations. An independent team can force evidence-based acceptance without competing for future headcount. The fixed four-month engagement also prevents closure design from becoming a new permanent layer of transformation governance.

What you will own

• Establish the residual-obligation baseline across benefits, controls, defects, decisions, suppliers, funding and member commitments.
• Separate completed value, accepted technical debt, temporary workaround and unresolved risk using explicit evidence standards.
• Design transfer dossiers naming the receiving executive, capability requirement, funding, control, clock and escalation route.
• Test whether receiving functions can manage two unfamiliar failures without informal support from the transformation office.
• Frame close, close-with-conditions or retain choices for every capability, including the consequence and expiry of conditions.
• Produce the archive, benefit-evidence ledger, decision-rights map, funding unwind and ninety-day post-closure watch plan.
• Resolve consolidated evidence gaps and secure signed acceptance dossiers before presenting the final closure calendar.

Candidate qualifications

• Closed or materially reduced a long-running enterprise transformation office in a regulated, member-facing institution.
• Distinguished real benefit evidence from delivery completion, financial attribution and optimistic programme narrative under scrutiny.
• Transferred controls, unresolved defects, vendor obligations and decision rights into operational ownership without creating shadow support.
• Designed capability tests and unseen failure simulations that exposed whether receiving teams could genuinely operate alone.
• Understands pension administration, fiduciary sensitivity, member harm, audit evidence and operational continuity at executive level.
• Delivered fixed-scope closure recommendations despite strong incentives from both programme staff and receiving executives to defer accountability.

Non-negotiables

• Will not recommend closure from milestone status alone; every material obligation needs evidence and an accepting executive.
• Brings direct transformation-office exit experience in regulated operations, not only programme mobilisation or assurance reporting.
• Can attend four Toronto labs and both committee acceptance sessions despite the otherwise remote delivery model.
• Accepts that management retains project delivery, benefit design, platform remediation, supplier negotiation and appointment decisions.

1. 49 words maximum. Describe a transformation capability you refused to close because operational acceptance was not real.
2. 49 words maximum. How would you distinguish accepted technical debt from a temporarily hidden member-risk obligation?
3. 49 words maximum. What inputs must the client provide in week one to establish a defensible residual baseline?