KPIs every manager should know

The problem it solves

When a company decides to "measure more", it usually ends up with a long report that is distributed punctually and discussed never. The numbers are there, and nobody changes anything because of them.

The monthly meeting is where it shows. Figures are read aloud and nobody asks what to do about them. Each department arrives with its own version of the same number, and the discussion is spent deciding whose is right. An indicator sits in red for weeks without anyone knowing whether that is serious, because nobody ever said at what point it would be. And when the quarter's result comes as a surprise, it turns out the warning was in a report somewhere; nobody was reading it as one.

The cause is almost always the same: what got measured was what the system could export, not what the business needed to know. An indicator nobody decides with is not an indicator, it is a collection cost. And while the dashboard grows, the handful of figures that actually govern the business stay out of sight. The cost is not only the hours spent assembling the report. Management grows used to finding out late, when all that is left is to explain what already happened. Over the months the report turns into one more routine chore, and the company keeps steering by instinct while paying to measure.

What it covers

The workshop runs the usual process backwards. Instead of starting from available data, it starts from the decisions a manager takes each week and each month, and asks which number would make any of those decisions different. What survives that question is a KPI; the rest is information. The angle is deliberately the area manager's rather than the system's: the question is not what the company is able to measure, but what one specific person needs to know in order to decide in time.

It then separates lagging indicators — which report what already happened — from leading ones, which warn in time that the result is about to move. A dashboard made only of the first is a very high-resolution rear-view mirror. It also takes on a risk that rarely gets discussed: indicators that can be improved without lying and without improving anything, such as a response time that falls because cases get closed before they are solved. Any indicator with consequences invites that game, so it is better chosen with eyes open. And it asks how many indicators a team can genuinely carry before none of them gets real attention.

The final part installs what keeps a dashboard alive: who owns each indicator, how often it is reviewed, and which specific conversation it triggers when it leaves range. A KPI with no threshold and no owner is a number on a sheet again.

Most of the session is hands-on. Each participant writes down the decisions they take regularly, derives indicators from them, marks which ones lead and sets a threshold for each. Anyone who brings an existing report or dashboard puts it through the reverse test: indicator by indicator, which decision would change if it vanished tomorrow. Whatever fails goes on a retirement list with its reason, and that is usually where the discussion heats up. Participants leave with a short set of indicators tied to decisions they actually make, each with a threshold, an owner and a review cadence, plus a written record of what they will stop measuring. Often the leading indicator a manager needs cannot be measured because the process that should produce it was never defined, and it is in designing that process, rather than the dashboard, that ALUD's Operations engine does its work.

What participants learn

• Derive indicators from decisions rather than from available data.
• Separate lagging from leading indicators and use both.
• Set thresholds that trigger a specific conversation.
• Assign an owner and a review cadence to every indicator.
• Shrink an existing dashboard by removing what changes no decision.

Agenda

1. 01From decision to indicator: the right order
2. 02Lagging and leading indicators
3. 03How many KPIs a team can actually carry
4. 04Thresholds: when a number demands a conversation
5. 05Owner, cadence and review forum
6. 06Indicators that can be gamed without lying
7. 07How to retire indicators without losing control
8. 08The minimum dashboard of an area manager

What the organization leaves with

• A short set of indicators tied to real decisions.
• A written threshold for each selected indicator.
• An owner and a review cadence per indicator.
• A list of current indicators to retire, with the reason.