A transition is the period when work moves from one team to another: from a client’s in-house staff to a BPO, from one vendor to another, or from one of a BPO’s sites to a different one. Customers should notice nothing. Behind the scenes it is one of the riskiest phases in the life of an account, because the knowledge that makes the process work sits in people’s heads, half-documented procedures and tool shortcuts that nobody thinks to mention.
A well-run transition is built around one idea: knowledge and responsibility should move in small, verified steps, with a clear test at each step before the next one starts.
Following one transition from start to finish
Take an insurance company moving its motor claims intake from its own Pune team to a BPO in Chennai. The phases below are typical, though names and lengths vary between companies.
1. Planning and due diligence. The transition manager and the client agree on scope (which call types, which queues, which back-office tasks), volumes, hours, systems access, security requirements and a timeline. A transition plan sets out who trains whom, which documents must exist, and what the exit criteria are for each phase. Dependencies such as network connectivity, VPN access, telephony routing and user ID creation are listed early, because they cause more delays than training ever does.
2. Knowledge transfer (KT). Subject matter experts from the Pune team train a first batch of Chennai trainers, team leaders and senior agents, often called the “train the trainer” group. Sessions cover the product, policies, systems and the process flow. The output is not just trained people but documents: standard operating procedures, process maps, FAQs, escalation matrices. If the client’s procedures were never written down, KT is the moment they get written, and the receiving team should own that writing.
3. Shadowing. The Chennai group now watches the Pune team do real work. They listen to live calls, sit beside processors (in person or on screen share), and see how cases are actually handled, including all the exceptions that never made it into training slides. The incumbents do the work; the new team observes, takes notes and asks questions. This is where undocumented steps surface: “we always check this second screen before approving” or “for this dealer we call the surveyor directly”.
4. Reverse shadowing. Roles flip. The Chennai team handles live work while the Pune experts watch, correct and approve. Every transaction is still protected by an experienced reviewer. Errors are logged by type, and the process feeds them back into training and documents. Reverse shadowing ends when the new team meets agreed thresholds, for example accuracy above a set level on a minimum number of transactions, and no open critical knowledge gaps.
5. Go-live, often in waves. The new team takes full ownership, frequently starting with a share of the volume or the simpler call types, then expanding. A parallel run, where both teams process the same work for a short time, is sometimes used for high-risk back-office processes.
6. Hypercare and stabilisation. For the first weeks after go-live, extra support stays in place: client SMEs on call, daily review meetings, relaxed SLAs or a “glide path” where targets step up over a few months. The transition formally closes when steady-state SLAs are met for an agreed period and the account moves to normal governance.
Shadowing versus reverse shadowing
| Shadowing | Reverse shadowing | |
|---|---|---|
| Who does the work | Existing team | New team |
| Who observes | New team | Existing team |
| What it proves | The new team has seen the real process, including exceptions | The new team can perform it to standard under supervision |
| Main risk | Passive watching without testing understanding | Reviewers stepping in too early, so the new team never truly owns a case |
Shadowing builds familiarity; reverse shadowing builds evidence. Skipping reverse shadowing to save time is one of the most common reasons transitions fail after go-live.
Where transitions usually go wrong
Unwilling knowledge givers. When the outgoing team is losing its jobs, or an incumbent vendor is losing a contract, enthusiasm for teaching the replacement can be low. Contracts often oblige exiting vendors to support transition, but goodwill is harder to contract. Clients who manage this well involve their own people visibly and recognise those who help.
Tribal knowledge. The SOP says one thing and experienced staff do another, because the SOP is out of date. KT that relies only on documents carries the old errors across. Shadowing on real volume is the antidote.
Access and infrastructure. Trained agents sitting idle because user IDs, application access or telephony routing are not ready is a familiar picture. Infrastructure readiness should be a tracked workstream with its own owner, not an afterthought.
Losing the first batch. The first trained group carries most of the knowledge. If several of them resign or are promoted out during the first months, the process has to relearn from documents. Many providers protect against this by training more people than strictly needed and by recording sessions and building a knowledge base during KT.
Volume surprises. The new team is staffed on the client’s historical volume, but the transition itself can create extra contacts, for example from a new phone number or changed IVR. A buffer in staffing during hypercare is cheaper than missing SLAs in the first month.
Exit criteria make the difference
The single most useful habit in transition management is defining, before each phase starts, what must be true for it to end. “Reverse shadowing ends after two weeks” is a date. “Reverse shadowing ends when each agent has processed at least an agreed number of cases at or above the target accuracy, all critical SOPs are signed off by the client, and the escalation matrix has been tested” is a gate. Dates get met whether or not the team is ready. Gates protect customers.
The same framework applies in reverse when an account exits or moves to another provider. A provider that runs its own exits responsibly, with honest documentation and real shadowing support, builds the kind of reputation that wins the next transition.
Written by the RP Strativa Team. The insurer, locations and phases in the example are illustrative.
Leave a Reply