Interim Global Services COO — Migration Recovery

The mandate

A global services migration has left several transitioned processes with unresolved handoffs and control-evidence gaps. Recipient teams have created temporary workarounds, but no single executive owns recovery priorities across centres. The interim COO will hold operating authority for the affected service platform, distinguishing immediate continuity measures from the durable process ownership needed before migration activity can safely resume.

The nine-month assignment begins on 26 October 2026, while a permanent global services COO search runs in parallel. An approved extension may address a documented recovery dependency, subject to a 24-month overall maximum. Handover requires stable agreed service measures, tested control-evidence retrieval and a completed recovery rehearsal across critical processes. The successor must inherit a platform that can operate without the incident team continuously repairing ordinary handoffs.

The COO may pause migration waves, redeploy approved service capacity and set recovery priorities within the existing operating budget. Permanent site closure, material outsourcing commitments and structural staffing changes require executive or board approval. Technology, financial policy and regulated recipient-business authority remain with their respective owners. The operating chief must not treat urgency as permission to bypass specialist approval or represent temporary manual workarounds as sustainable recovered control.

Approximately 800 service staff report through five process executives, with recipient managers participating in recovery tests. The perimeter excludes redesign of the group's commercial products, broad ERP replacement and retrospective review of individual conduct. The interim will preserve evidence needed by authorised reviewers but focus on restoring the operating chain. Success is a verified handover of service and resilience, not a promise that every historical incident or legal question will be conclusively resolved.

What you will own

• Establish a recovery perimeter that reconciles transitioned processes, recipient workarounds and outstanding control gaps, identifying which services require immediate containment and which can continue under documented temporary arrangements.
• Decide migration pause and restart recommendations through explicit readiness evidence, using delegated stop authority when service or control consequence is unacceptable and recording the recovery conditions required before the next wave proceeds.
• Redeploy operating capacity across affected processes within approved limits, prioritising critical obligations and preventing backlog reduction in one queue from increasing downstream correction or recipient-business exposure.
• Lead joint service rehearsals with recipient managers, testing handoffs, approvals and evidence retrieval so recovered performance is verified by the business relying on the work rather than only by the delivering centre.
• Present candid recovery papers to the steering committee, distinguishing containment from sustainable resolution and escalating technology, policy or structural changes that remain outside the interim's operating delegation.
• Transfer tested process ownership and resilience arrangements to the permanent COO, including residual issue decisions, staffing coverage and a practical demonstration that ordinary cycles no longer require incident-team intervention.

Candidate qualifications

• Bring COO or equivalent global shared-services operating responsibility within a 22–28-year career, with substantive financial-services, consumer-product or contract-service experience. Show a migration or operational recovery where you held executive decision authority. Participation in an incident task force is insufficient unless you can explain the operating choices, approval boundaries and consequences you personally owned.
• Demonstrate end-to-end process knowledge across finance or business-service chains, including how control evidence and recipient handoffs are maintained during disruption. Explain a temporary workaround you deliberately did not accept as a permanent solution and the tests used before recovery was declared. ERP and automation familiarity must support operational judgement, not replace qualified technology or financial-policy approval.
• Have led process executives and recipient stakeholders through contested priorities under time pressure. Evidence should include a pause, capacity shift or revised transition decision and how you protected higher-consequence obligations. Selection will examine whether your reported recovery reflected genuine recipient stability or merely improvement in local queue measures while rework remained elsewhere.
• Be available for five-day onsite executive leadership from the stated date, with planned recipient-region travel where testing requires it. Bring a deliberate interim exit method and succession capability. The permanent COO should receive verified operating arrangements and honest residual exposure, not a collection of optimistic status slides or a dependency on the interim's personal relationships to resolve every cross-centre issue.

Application

Applications for this mandate are received in one way only: through the India Board Terminal's application process. It is automated end to end. Your Executive Passport travels to the mandate holder in its confidential form, your answers to the three questions below are read before anything else in your file, and every stage that follows is recorded on your applications page.

There is no address to write to and no intermediary to call. The mandate holder reads what the Terminal delivers and nothing else, which is what keeps the process the same for every applicant and keeps your name out of it until you release it. Applications close on 14 October 2026. Mandate reference CVU-INT-2026-IND-119.