The SSC/GBS transition plan — FTE sizing, knowledge transfer, and the exit to BAU
The short answer
A shared-services / GBS / BPO transition plan has six parts: the FTE sizing (volume divided by productivity, multiplied by a ramp uplift — you fund the ramp, not the steady state), the choice of transition model (lift-and-shift, lift-shift-transform, build-operate-transfer, or staged), a four-stage knowledge transfer (observe, do-with-support, do-with-review, do-independently) that advances on objective evidence rather than a calendar, governance with a status that writes itself from the metrics, a hypercare phase with explicit BAU-exit criteria, and the retained organisation that keeps accountability on the home side. Transitions rarely fail on the work moving; they fail on a knowledge transfer signed off by date instead of by competence.
The transition plan — the eight moves from scope to BAU
- 01
Scope the work and pick Wave 1 on evidence
Inventory the processes, their volumes, their complexity and their dependencies. Wave 1 is the work that is stable, documented and low-risk enough to prove the model — not the most painful process you wish would leave first. Sequencing is a governance decision, not a wish list.
- 02
Size the FTE with the ramp uplift, not the steady state
Headcount = transaction volume / target productivity, multiplied by a ramp uplift for the learning curve. The classic underfunding error is sizing to the steady-state number; you fund the ramp (often a ~20-week curve to full productivity), then taper. Under-resource the ramp and quality collapses in month two.
- 03
Choose the transition model deliberately
Lift-and-shift (move as-is, transform later), lift-shift-transform (re-engineer during the move), build-operate-transfer, or staged. Each trades speed against risk and against how much change the receiving team can absorb at once. Name the model; do not drift into one by default.
- 04
Run knowledge transfer in four stages — and advance on evidence
Observe, do-with-support, do-with-review, do-independently. Advance a process to the next stage on objective evidence (error rate, throughput, a sign-off against a competency checklist) — never because the KT calendar says week six. A KT signed off by date instead of by competence is the single most common cause of a transition that 'completed' and then failed.
- 05
Stand up governance with a status that writes itself
Define the steering cadence, the RACI, and the metrics — then have the status report derive from the metrics rather than from optimistic narration. Leading indicators (KT stage completion, defect trend, shadowing hours) warn you; lagging ones (SLA breaches) only confirm the failure after it lands.
- 06
Plan hypercare as a phase with explicit exit criteria
Hypercare is where the transition is judged. Staff it, define the incident-triage path, and write the criteria to exit hypercare into business-as-usual — a sustained SLA over a defined window, defect rate below threshold, no open critical issues. 'It feels stable' is not an exit criterion.
- 07
Design the retained organisation before go-live
Moving the work does not move the accountability. Decide what stays on the home side — vendor/relationship management, controls, escalation, process ownership — and staff it. A transition with no retained organisation re-insources itself within a year.
- 08
Capture the run book so the next wave starts from a baseline
The SOPs, the KT evidence, the metric baselines and the governance pack become the template for Wave 2 and the next transition. The consulting hours that touched each were perishable; the documented operating model compounds across every wave and every site.
Transitions fail on knowledge transfer, not on the work moving
The work moving is the easy part — the volumes are known, the systems are the same. What fails is a knowledge transfer that was signed off by the calendar instead of by competence: week six arrives, the KT is marked complete because the plan said so, the receiving team is shadowing at 60% accuracy, and by month two the SLA is breaching and the home side is quietly running parallel. The transition “completed” and failed at the same time.
So the plan above is mostly governance dressed as logistics. The FTE math and the model choice are the structure; the four-stage KT that advances on evidence is the control that actually decides the outcome.
You fund the ramp, not the steady state
The most expensive sizing error is funding the steady-state headcount. A transition runs up a learning curve — often around twenty weeks to full productivity — and if you resource only the end-state number, quality collapses in the first two months while the team is still climbing. Size to volume ÷ productivity × a ramp uplift, fund the curve, and taper as competence is evidenced. It looks like over-staffing on a spreadsheet; it is the difference between a transition that holds and one that gets re-insourced.
The retained organisation is not optional
Moving the work does not move the accountability. Vendor and relationship management, controls, escalation and process ownership stay on the home side — and if nobody designs and staffs that retained organisation before go-live, the transition re-insources itself within a year as the business rebuilds the capability it gave away. Decide it up front; it is part of the plan, not an afterthought.
This guide is operator practice, not a consulting engagement — adapt the models, FTE assumptions and gates to your own scope and validate with your delivery and finance functions. The full end-to-end method, including engagement and BAU exit, is the Transition Operator’s Course; the sizing math is also covered in the free guide Sizing an offshoring or SSC transition.
Frequently asked
How do I size the FTE for an offshoring or SSC transition?
Headcount = transaction volume divided by target productivity, multiplied by a ramp uplift for the learning curve. The common error is funding the steady-state number; you fund the ramp — often a ~20-week curve to full productivity — and taper as competence builds. Under-resourcing the ramp is what collapses quality in the second month.
What are the stages of a knowledge transfer plan?
Four stages: observe, do-with-support, do-with-review, do-independently. A process advances to the next stage on objective evidence — an error rate, throughput, a competency sign-off — not because the calendar reached a given week. KT signed off by date rather than by competence is the most common cause of a transition that completes on paper and fails in practice.
When can a transition exit hypercare into business-as-usual?
On explicit, pre-agreed criteria: a sustained SLA over a defined window, a defect rate below threshold, and no open critical issues — not a subjective 'it feels stable.' Hypercare is staffed as its own phase with an incident-triage path and a written exit gate, because it is where the transition is actually judged.
Is this consulting advice?
No. It is an operator-grade planning toolkit and method, drawn from running real transitions. It does not constitute a consulting engagement; adapt the models, FTE assumptions and gates to your own scope and validate against your delivery and finance functions.
The done-for-you version: an 18-tab transition management workbook plus a 15-page, 12-phase delivery handbook (the FTE math worked, the four models, the knowledge-transfer deep-dive that advances on evidence, the retained organisation, leading-vs-lagging metrics, the recovery move) and engagement templates. The standalone toolkit beneath the Transition Operator's Course.
Get the Transition Management Operator's Workbook — $179 →Written by Petko Petkov — 15 years inside enterprise IT operations. Vihren Labs publishes operator-grade templates and playbooks for the enterprise IT stack.