Productivity without a quality blind spot

Productivity should be evaluated across the workflow, with quality and service measures beside the financial result.

I prefer contained tests with feedback from the people doing the work. They help expose unintended consequences before a change is scaled. The objective is a stronger operating system, not an isolated saving that another team must quietly absorb.

The blind spot persists because cost savings are easy to measure and attribute, while the consequences often appear later and elsewhere. A reduction in staffing shows in this period's results; the rise in customer contacts, errors or staff turnover may show in a different budget some months afterwards. By then the connection is difficult to prove and the original programme has been declared a success. Organisations that celebrate savings without tracking those downstream effects teach their managers that shifting effort is as good as removing it.

Before any productivity change is approved, I ask the sponsor to state where the work will go if the team no longer does it, which quality or service measures could deteriorate as a result and who will watch them. I also ask how we will hear from the people doing the work if the change creates problems nobody foresaw. Those answers become part of the proposal. A saving that cannot provide them is not rejected outright, but it is tested on a smaller scale before anyone counts it in a forecast.

Consider a customer service operation that introduces a target to shorten call duration. Average handling time falls and the cost per call improves. A contained test, however, might show that customers are calling back more often because their issue was not fully resolved, and that more cases are being passed to a specialist team. The full workflow has become more expensive even though the measured step is cheaper. Adjusting the target to reward resolution rather than speed may deliver a smaller headline saving and a better overall result.

The counter-argument I hear most often is that insisting on full workflow evidence will paralyse improvement, because every change has some effect somewhere. I accept that perfect measurement is impossible and that some judgement is required. The answer is proportion. Small, reversible changes can proceed quickly with light monitoring. Larger changes that affect customers or safety deserve a contained test and a clear set of measures. The discipline is not to slow everything down but to match the scrutiny to the potential for unintended harm.

This asks the leadership team to recognise savings only when they hold across the workflow, which may mean reporting smaller numbers than a programme initially promised. It asks finance and operations to agree how displaced cost will be tracked. And it asks leaders to protect the people who raise concerns about quality, because they are often the earliest source of evidence. The board can support this by asking how a reported saving was verified and what happened to the measures that sit beside cost, not only by welcoming the total.

Productivity programmes earn lasting support when colleagues see that quality and safety are measured as carefully as cost. I have found that the best ideas for improvement come from the people closest to the work, provided they trust that the gains will not be taken at the expense of the customer or of each other.