Defining KPI’s is not easy — these five steps will fix that

Ask five people in your company what an “active customer” is and you’ll get five different answers. Ask them what counts as an “order,” a “lead,” or “sell-out,” and you’ll get five more. Nobody notices this is a problem until someone builds a dashboard on top of it, presents it to the board, and a VP says “that number doesn’t match what I’m seeing.” Now you’re not talking about strategy anymore. You’re arguing about definitions.

This happens at companies with 15 people and companies with 15,000. The scale changes, the mess doesn’t.

Two very different kinds of reporting

Most companies bundle everything under “reporting” and wonder why it never quite works. In reality there are two distinct jobs:

These need different inputs, different owners, and different cadences. Treating them as one blob is where most reporting builds go sideways, you end up with a “strategic dashboard” that’s really just twelve operational metrics stapled together with no target, no owner, and no deadline attached.

The hierarchy nobody skips on purpose (but everyone skips anyway)

There’s a natural progression in any good measurement setup, and it only works in this order:

The mistake almost everyone makes is jumping straight to step 3. They set a target on a metric that was never properly defined in step 1, and it falls apart the first time someone questions the number, usually in the exact meeting where it matters most. Well-defined indicators are the foundation. Skip that step and everything built on top of it is unstable, no matter how good the dashboard looks.

This shows up a lot in organizations with both global and local teams: global defines “active customer” one way for consolidated reporting, the local sales team defines it another way for their day-to-day pipeline, and the first time someone compares the two numbers across markets, the KPI stops being trusted, not because the target was wrong, but because the indicator underneath it was never agreed on.

Where the targets actually come from

A KPI without a real anchor is just a number someone picked because it sounded ambitious. Where that anchor comes from varies by company and by how formal you want to be about it:

Either way, the same rule applies: the target only holds up if it’s set on top of an indicator that’s actually well-defined. A KPI born out of a great strategy session is just as fragile as one born out of a management meeting if nobody agreed what “active customer” means underneath it.

A ten-person company might set its KPIs entirely the second way and never need the first. A group of companies with a shared board usually needs both, the structured exercise to align on direction, and the recurring management conversation to keep targets current between full re-assessments.

A process that doesn’t need a big platform to work

You don’t need a data warehouse, a BI team, or six months to do this properly. The shape of the work is the same at any size:

Get this right and the rest follows

The reason most reporting initiatives underperform isn’t the tooling, and it isn’t which method you used to pick the target. It’s that step one, agreeing on what an “order,” a “customer,” or “active” actually means, gets rushed or skipped entirely, because it feels like admin work standing between you and the dashboard everyone’s waiting for.

It isn’t admin work. It’s the foundation. Boring, unglamorous, and the single biggest predictor of whether your KPIs will still mean something six months from now, whether you’re a three-person team or a group of companies reporting to a board.

Back to all articles