Measuring Productivity After a Platform Change
Major platform transitions break old baselines. Work types change, routing changes, staff behaviour changes, source fields change, and teams spend time learning new workflows. Treating the first post-change number as a simple productivity result can create the wrong story.
The risk is not just poor analysis. The risk is that leaders make workforce, performance, or change-management decisions from a number that looks precise but is not yet stable.
The first post-change number is rarely the answer
After a platform change, productivity can move for many reasons:
- Staff are learning new workflows.
- Work is being routed differently.
- Some case types take longer in the new system.
- Source fields have changed meaning.
- Demand has shifted at the same time as the transition.
- Teams transition at different times.
- Backlog, queue ownership, or channel mix has changed.
If those factors are not controlled, the report may confuse transition friction with sustained productivity loss.
A better measurement frame
A more useful approach compares performance across three periods.
| Period | Purpose |
|---|---|
| Before transition | Establish the old baseline and normal variation. |
| During transition | Identify ramp-up, training, routing, and system effects. |
| Stabilisation period | Test whether performance has recovered or reset to a new pattern. |
The goal is not to hide a decline. The goal is to separate temporary transition effects from a genuine operating-model issue.
Adjust before interpreting
Productivity reporting should account for:
- Demand: Did work volume rise or fall?
- FTE: Did available staffing change?
- Work type: Did the mix become more complex?
- Channel: Did work move between phone, email, queue, or case channels?
- Seasonality: Is the period normally higher or lower?
- Ramp-up: Are the first weeks after transition a fair baseline?
- Outliers: Were outages, bulk actions, or unusual spikes present?
- Cohorts: Did teams transition at the same time and under similar conditions?
Raw movement can be useful as a warning signal, but adjusted movement is usually more useful for executive interpretation.
Example executive interpretation
A weak summary says:
Productivity declined after the platform change.
A stronger summary says:
Raw productivity declined after transition. After adjusting for demand, available FTE, work type mix, ramp-up weeks, and outliers, the estimated ongoing impact is materially smaller. The first transition weeks should be treated as an unstable baseline. Recommended next steps are targeted workflow support, cohort monitoring, and rechecking the measure after the stabilisation period.
This type of wording gives leaders a decision path. It does not overstate certainty, and it does not treat the number as blame.
Common measurement mistakes
The biggest mistakes are usually:
- Comparing one pre-change week with one post-change week.
- Using headcount instead of available FTE.
- Ignoring ramp-up and training time.
- Treating all work types as equal effort.
- Mixing teams that transitioned at different times.
- Removing outliers without documenting why.
- Presenting raw movement without known limitations.
What good reporting should trigger
Good productivity reporting after a platform change should help leaders decide:
- Where support or training is needed.
- Whether staffing assumptions need to change.
- Whether work routing is creating friction.
- Whether a process or system issue needs escalation.
- When the new baseline is stable enough for performance management.
The best reporting after a platform change guides support rather than blame. If a measure shows friction, it should help leaders target training, process repair, system fixes, workflow redesign, or workforce planning.
Related resources:
- Related demo: PACE Productivity Impact Simulator
- Related case study: PACE Productivity Impact Measurement