Phase 10 of 10 · Launch

Stabilisation and early value

How do we make the first year a launchpad, not a cleanup?

The big picture

Every centre goes through stabilisation. Those that treat it as a designed stage, with its own governance, metrics and leadership attention, stabilise faster and keep their people. Those that treat it as a cleanup risk losing the trust of the very stakeholders whose support they need next.

The decisions that matter

  • What “stable” means, in measurable terms, for each phase
  • Which metrics to track from month one
  • How to protect the SME layer during the highest-risk months
  • What the Year 2 capability roadmap contains

What good looks like at the end

  • A stabilisation programme with phase exit criteria and a dedicated lead
  • A monthly dashboard of six metrics, reviewed by the sponsor
  • Quarterly 90-day win targets and reports
  • A Year 2 capability roadmap drafted by month nine

Who owns it

The GCC Head, with the executive sponsor

When

Designed before go-live; runs through the first year.

Six metrics for the first year

MetricWhat it measuresTarget direction
SLA complianceShare of transactions within agreed turnaroundAt least 95% by month 3, trending up
Exception rateShare needing manual intervention or reworkDeclining month on month
Escalation velocityDays from issue identified to resolvedDeclining; under 3 days by month 6
Knowledge independenceShare of queries resolved without onshore helpRising; at least 80% by month 6
SME attritionRolling three-month attrition among analysts and team leadsUnder 15% annualised
Value against baselineMeasured improvement on pre-GCC performancePositive and rising every quarter

Targets from The GCC Advantage. Review weekly in operations and monthly with the sponsor, as a decision meeting, not a status update.

What specialist advisers say

Curated from published work by HFS Research. Summarised in our own words; follow the link for the full piece.

In detail

The approach

  1. Phase one: continuity assurance (to about month 3)

    Keep processes running and close the month on time. The measure that matters is whether issues are being found and resolved faster each week.

  2. Phase two: process hardening (about months 2 to 6)

    Move from fixing issues to removing root causes: the variants that generate exceptions, the hand-offs that create rework, the controls that get bypassed.

  3. Phase three: early value capture (month 4 onwards)

    The first automation wave, the first analytics uplift, and the first improvement idea that originates in the centre rather than with the sponsor.

  4. Track three levels of metrics from month one

    Operational metrics, process health metrics (rework, exceptions, overrides, escalations) and value metrics tied to the business case.

  5. Protect the SME layer in months four to nine

    Start retention before the risk window: a learning programme with career-linked outcomes, monthly conversations with team leads, and early stretch work beyond the transition scope.

  6. Own the stakeholder story

    A monthly update that leads with what improved, admits what is below target, explains why and commits to a next step; plus a direct, regular conversation between the GCC Head and the business unit leader.

  7. Run 90-day wins

    Each quarter, set three to five specific, measurable improvement targets, and report hit or missed, with explanation, to the CFO and sponsor.

  8. Draft the Year 2 roadmap by month nine

    Automation, analytics, scope expansion and a first centre of excellence seed, so stability becomes a launchpad rather than the destination.

Readiness signals

The signs that need attention before a centre moves on from this phase.

  • Each stabilisation phase has written, testable exit criteria
  • All six metrics are tracked monthly and reviewed with the sponsor
  • Retention actions for the SME layer started before month four
  • Quarterly 90-day wins are set and reported
  • A Year 2 capability roadmap is drafted and reviewed with the sponsor

Where organisations go wrong

  • Meeting SLAs while exception rates quietly rise

    What works: Track process health, not only output.

  • Going quiet when performance is imperfect

    What works: Communicate proactively; the business forms its long-term view now.

  • Stabilising, then stopping

    What works: Treat stability as the foundation for Year 2, not an achievement to protect.

Questions for leadership teams

  • Are we managing stabilisation against written exit criteria, or by feel?
  • What is our SME attrition in the last three months, and what is in place before month four?
  • Have we drafted the Year 2 capability roadmap, and when does the sponsor review it?

Read more