Quality Measures as the Counterweight

One measure can be optimised. Two that oppose each other require genuine improvement, which is why pairing is the central technique in this subject.

The measurement warning in “Quality Measures as the Counterweight” matters whenever software records work patterns. Organisations researching employee monitoring software with screenshots can use the full provider overview for time and project context, while outcomes, quality checks and direct feedback remain necessary to explain what the metric cannot show.

What makes a good counterweight

It falls when the volume measure is inflated dishonestly.

For an independent perspective related to “Quality Measures as the Counterweight”, consult the NIST Privacy Framework; it offers a useful external check on definitions, governance and the assumptions built into a proposed measure.

It is collected independently, ideally not by the same people.

It is simple enough to report beside the volume figure.

And it matters to somebody outside the team, which stops it being negotiated away.

The usual pairings

Tickets closed, with reopen rate.

Units produced, with defect rate.

Cases handled, with escalation or complaint rate.

Deliveries completed, with damage or return rate.

Calls answered, with repeat contact rate.

Each pairing has decades of practice behind it in its own industry.

Repeat contact as the general form

Did the person have to come back?

It applies in support, service, healthcare, claims and most transactional work.

And it captures the thing volume misses: whether the work was actually finished, which is the specific failure that volume measurement produces.

Customer-side measures

Satisfaction, complaints, retention.

Noisy individually, informative in aggregate, and independent of the team's own recording.

Slow to move, which makes them a check rather than an operational signal.

Where quality is hard to measure

Professional and creative work, where quality is judged rather than counted.

Here the counterweight is frequently rework: how often something came back for revision.

Imperfect and better than nothing, and its own note covers rework properly.

Reporting the pair

Same page, same period.

And the rule: a rise in volume with a rise in the counterweight is not an improvement, whatever the headline says.

Stating that rule in advance is what makes the pair work, because otherwise the good number gets reported and the other one footnoted.

The counterweight that is not one

A quality measure collected by the same people, on the same basis, with the same incentive.

Self-assessed quality scores move with whatever is being rewarded.

Independence is the property that matters, more than the specific measure chosen.

What to check

Does every volume measure in your reporting have a counterweight?

Is the counterweight collected independently?

Are they reported together?

And has anybody stated that both rising is not an improvement?