KPIs the team trusts

A KPI can be mathematically correct and its interpretation still be unfair.

In KPIs do not improve in Excel I wrote that the number on its own does not improve the work. This essay deals with the next question: how do you build a KPI people trust? One they understand, that does not punish them for what they do not control, and that leads them to an action.

For me, trust in a KPI is built from three things: a clear definition, fair responsibility and the action that follows the result.

Four indicators in last mile

In last mile we worked mainly with four indicators: Damage, Incomplete, Delay and Loading Time.

This is how I understood them:

• Damage: damage to products or orders.
• Incomplete: orders that reached the customer incomplete.
• Delay: delays in carrying out the delivery process.
• Loading Time: the time it took to load the vehicle before departure.

They were four ways of looking at quality, time and operational discipline.

But for the official definition of each indicator, the exact way it was calculated and what was excluded from a delay, I do not have a confirmed document I can quote. And to me it matters not to confuse the practical meaning of an indicator with the official formula a company uses.

That distinction is not a detail. If the team understands a KPI one way and the report calculates it another, trust is lost before the first result is even seen.

When the number is right and the reading is unfair

For a concrete dispute where a delay caused by Outbound was unfairly charged to a driver, I do not have a documented case I can present as fact.

But I have worked with problems that involved more than one stage of the process: missing bags, mixed carts, load organisation and delays at departure. Those situations made me see a KPI differently.

If a driver leaves late because the order was not ready, the problem shows up at departure. But that does not automatically mean the responsibility is the driver's alone. I wrote this in Mistakes get lost between departments too: the place where a mistake is measured is not necessarily the place where it was born.

So before I judge someone's performance, I want to understand which part of the result they could really control.

That does not mean removing individual accountability just because the process is complex. I cannot ask an employee to be accountable for everything that happens in a process several departments take part in. But I cannot erase their accountability either.

The manager's job is to separate what the person controls from what has to be corrected in the system.

The result and the reason

In last mile we followed the KPIs in the operational reports and in the daily stand-up. I worked with reports on Damage, Incomplete, Delay and Loading Time, and with analyses for drivers and DSPs. In the reporting work I also asked for updates during the day, including a 90-minute rhythm for monitoring some of the indicators.

To me it mattered to distinguish two kinds of information.

One showed the result: how many delays, how much damage, how many incomplete orders.

The other showed the reason: what happened in the process that led to that result.

Without the second part, numbers can turn into reporting without learning.

If Delay is high, I want to understand why. Is it linked to order preparation, the organisation of the dock, loading time or another cause? If Damage rises, my question is not only who had the order. I want to know at which stage the damage may have happened and how we can prevent it.

How the team saw it

I do not have a concrete documented reaction where the team experienced KPIs as punishment or as help. I will not invent one.

But my position is clear. A KPI that is used only to show someone they are below target does not necessarily help them improve.

I believe people have more reason to trust a KPI when it is used to understand and improve the work, not only to compare individuals.

No indicator is read alone

For a concrete episode where a KPI led to the wrong behaviour, I do not have a case I witnessed and can describe with certainty. But I see the risk clearly.

If an organisation measures only the speed of loading, without linking it to quality and safety, it can create an incentive for people to rush. That is a possible example, not an incident I am claiming happened.

That is why I would never judge Loading Time in isolation from Damage, Incomplete and safety.

If one indicator improves but another gets worse because of the way the improvement was achieved, we have to check whether we are measuring the right behaviour.

In the hotel: indicators that are not KPIs

A hotel works with a different set of operational information. During Night Audit I checked the daily reports, room status, arrivals, departures, no-shows, the forecast for the next day and the open matters that could affect the operation. An important part was checking that the information was accurate before closing the day.

But I want to make a distinction. These were operational indicators and checks I used in the work. I do not have it documented that they were all formal KPIs with individual targets for the Night Auditor.

In the hotel I understood even better that a number does not always show the whole situation. You can have an accurate report and an open problem that still needs action. That is why the report has to be linked to the real status, to responsibility and to passing the information on to the next shift.

The KPI card

Before you start measuring something, fill in these six lines. If you cannot fill in all six, the KPI is not yet ready to show the team.

1. What are we measuring? In words everyone on the team understands, not only the person who builds the report.
2. How is it calculated? What counts, what does not, and from which source.
3. Who can influence the result? Which part is in the person's hands and which lies in the process, in another stage or in another department.
4. What is the standard? What counts as a good result, and why.
5. What context has to be checked? Which other indicators are read with it, so that improving one does not hide another getting worse.
6. What do we do when it deviates? Who sees it, when, and what the first step is.

You can fill in the card below right here and copy it for your team.

A KPI the team trusts is not necessarily the one that always shows green.

It is the one that measures clearly, is read fairly and helps people understand what they can do better.