Planning through a system migration: the productivity dip nobody budgets
The dip is not a risk — it’s a certainty
New telephony, a new CRM, a new WFM platform: every major system migration is sold on the steady state it will eventually deliver, and planned as if that steady state arrives on go-live morning. It never does. For weeks, sometimes months, after a cutover, agents are slower, less sure and more error-prone on the new tool, while trainers and floorwalkers pull experienced people off the phones. The productivity dip that follows isn’t a risk to be mitigated; it’s a near-certainty to be budgeted — and the operations that suffer most are the ones that pretended it wouldn’t happen.
The shape of the dip
It follows a J-curve. Handle time jumps as agents hunt around an unfamiliar interface; first contact resolution dips as they miss things the old system made obvious; shrinkage rises with training, hypercare and the floor-walking support a go-live needs. Then, over weeks, the curve climbs back — and if the new system is any good, it eventually settles above the old baseline. The two numbers that matter are the depth of the dip (how much worse, at the bottom) and its length (how many weeks to recover). Plan for both and the migration is a managed bump; plan for neither and you’ve quietly committed to missing service for a quarter while insisting everything is fine.
How to plan for it
Build the dip into the numbers. Add a temporary handle-time uplift and extra shrinkage for training and hypercare for a defined window, and lower the occupancy you expect while people are learning. Carry a deliberate hypercare buffer of capacity in the first weeks — the cheapest insurance a migration has. Phase the cutover where you can, so the whole operation doesn’t hit the bottom of the curve at once, and decide in advance whether you’re protecting service through the dip or accepting a managed, communicated drop. Above all, agree the recovery curve with the project team and track against it, so “we’re three weeks behind the ramp” is a fact you can act on rather than a surprise you explain after the quarter. The steady state will come; the planner’s job is to get the operation across the valley in between.
Pair this with new-hire ramp-up (the same J-curve), twelve-month capacity planning, and what a WFM system is.