How Company, Department and Individual KPIs Connect

Most companies have KPIs at two levels: the company has some, and individuals have some in their review form. The middle is missing, the two ends don't connect, and nobody notices until someone asks how a person's objectives relate to the company's and the room goes quiet.

This is how the levels should relate, and what genuinely changes between them.

The four levels

Two things change as you go down: the horizon shortens and the influence tightens. A company KPI moves over a year and nobody individually controls it. An individual KPI moves over weeks and the person largely does.

What each level is for

Company level — the arithmetic

One North Star plus three to five supporting measures. The supporting measures should plausibly add up to the North Star; if they don't, the plan has a hole in it.

The most common failure here is too many. Nine company KPIs is not a strategy, it is an unwillingness to choose, and it pushes the choosing down to people with less context.

Department level — the translation

This is the level most companies skip, and skipping it is why individual objectives so often look disconnected from the company's.

The department level answers: given the company's priorities, what is this function accountable for? It translates rather than repeats. If the company measures net revenue retention, Support translates that into resolution quality and time-to-resolution, Product into activation and feature adoption, Sales into expansion within existing accounts.

Same company priority, four different department measures. That translation is the work.

Team level — the delivery

Where the measure becomes weekly. Team KPIs need to be visible without asking anyone and movable by the team's own decisions — see how to set team KPIs for the four tests worth running.

Individual level — the contribution

Two to four measures reflecting what this specific person contributes, not a copy of the team's.

If everyone on a five-person team carries the same number, no one has an individual measure — they have a team measure written down five times. The individual level should capture what would be different if this person were replaced by someone competent but different.

The cascade, worked

One company priority, all the way down:

COMPANY   North Star: Net revenue retention 118%
          Priority: reduce involuntary churn from onboarding failures

DEPARTMENT (Customer Success)
          % of new accounts reaching activation within 30 days
          Health-score coverage across the book

TEAM (Onboarding)
          Median days to first value
          % of accounts completing the setup milestone
          Escalation rate during onboarding

INDIVIDUAL (Onboarding Specialist)
          Accounts activated per month
          Median days to first value, own book
          Quality score on setup reviews

Notice what happens down the chain: the measure gets shorter-horizon, more controllable, and more specific. Nobody repeats "net revenue retention," and yet every level is legibly serving it.

Why cascading the same number fails

The instinct is to give everyone the company number so everyone is "aligned." It fails for three reasons:

1. It doesn't tell anyone what to do differently. An engineer measured on revenue has no Monday-morning implication.
2. It removes accountability by diffusing it. If forty people own the number, nobody does.
3. It's unfair in both directions. People get credit for outcomes they didn't influence and blamed for ones they couldn't prevent.

Translation, not repetition. Each level should be able to explain in one sentence how their measure serves the level above.

Department KPIs are the missing middle

If you only fix one level, fix this one. It is skipped most often — and search behaviour reflects that: people look for "sales team KPIs" and "engineering KPIs" constantly, and almost nobody looks for "departmental KPIs" as a concept. Teams think in functions, not in org-chart layers.

Which is a useful hint about how to run it: define department KPIs function by function, in the function's own language, rather than as an abstract layer in a hierarchy diagram. See the KPI examples by department hub for function-specific starting points.

Individual KPIs and job descriptions

These two drift apart in every growing company, and annual planning is the natural moment to re-sync them.

The test: read someone's job description, then read their KPIs. Do they describe the same job? If the JD says one thing and the measures reward another, the measures win, and the JD is now a historical document.

Practical rule: when individual KPIs change materially, the job description changes in the same edit. Not the next review cycle.

Common failure modes

Levels that skip. Company → individual with nothing between. Individuals invent their own interpretation of company priorities, and forty people interpret differently.

Levels that repeat. Same number at every level. Alignment theatre.

Departments measured on activity. "Tickets handled," "campaigns run." Activity is a leading indicator, not an accountability.

Individual KPIs set by managers alone. A person who argued their way to their own measures defends them. A person handed measures optimises them, which is not the same thing.

No one owning the ladder. Somebody — usually a Chief of Staff or COO — needs to own whether the levels still connect. Absent that, they drift apart within two quarters.

Where to start

If you have company KPIs and nothing below: build the department layer first. It is the missing middle, and once it exists the team and individual levels follow relatively easily.

If you have nothing at any level, the honest answer is that this is a planning problem rather than a measurement problem — the annual planning calendar sets out when in the year to do it, and it's the gap our free workshop exists to close.

Software helps maintain the ladder once it exists, though it will not create it for you — see how to evaluate strategy execution software for what to look for.