Skip to content
KPI Systems and Balanced Scorecard | Part 5 of 8

Cascading Key Figures Without a Number Graveyard

Plant, area and line each get what they can influence. One definition at every level, fewer figures as you go down, and a line test for every board.

The quickest way to ruin a good scorecard is to copy it downward. Every area gets the plant page, every line gets the area page, and within a quarter the boards carry numbers nobody at the board can change. That is a number graveyard: a lot of paper, no decisions.

Breaking figures down means something else. Each level gets the figures it can influence, and the count falls as you go down.

Three levels in the example plant

Level What it gets Rhythm Figures
Plant Six per view, one owner each Monthly review, 40 minutes 24
Area (3) Three per view, taken from the plant list Weekly area meeting 12
Line (9) Safety, quality, delivery, output, one improvement figure Daily at the board 5

That produces 24 plus 36 plus 45, which is 105 reported values per period. All of them come from 24 definitions.

That is the test. Many values from few definitions is a cascade. Many definitions is a graveyard, because every definition is a separate argument about what the number means.

How a figure is actually broken down

A plant figure is rarely the same figure one level down. It is usually the thing that causes it.

On-time delivery of the plant becomes schedule attainment of the area and plan attainment of the shift at the line. A line cannot see the customer date. It can see its own plan.

Conversion cost per unit becomes overtime hours and scrap cost of the area, and scrap pieces per shift at the line. Cost is not a line figure. The things that cause it are.

First pass yield at final test becomes first pass yield per area and defects per shift by type at the line. The line needs the defect type, not the percentage.

Skills matrix coverage becomes coverage per area and, at the line, the number of tasks with fewer than three qualified people. A board shows the gap, not the index.

Some figures stop early. Inventory turns stops at area level as work in process, because no line team can influence turns within a week.

The line test

One question decides whether a figure belongs on a line board.

Can the team change this number this week, with what it controls?

If the answer is no, the figure belongs one level up, and the line gets the figure that feeds it. The test is hard to argue with, and it removes about half of what people first propose for a board.

One definition, every level

A figure keeps its definition sheet wherever it appears, measured on the same boundary with the same exclusions. Where that is impossible, it gets a different name rather than a local variant.

Nothing destroys trust faster than two levels reporting the same figure name with two different values and both being right.

What a level needs besides figures

Three things make a cascaded level work, and none of them is a number.

An owner per figure at that level, by name. An update day and time, printed where the figures are shown, so that an empty chart has an address. And a visible link to the figure one level up, so that a team knows what its own number feeds.

In the example plant, line boards are updated by hand at 06:00, area figures on Monday, and the plant scorecard before the monthly review. The Shop Floor Management line covers the daily routine around those boards in depth.

What it is worth

The plant kept 24 definitions and gained 105 reported values. Before the cut it had 146 at the top level alone, with local variants underneath. The cascade did not add work. It replaced four parallel reporting worlds with one.

The next part looks at where the numbers come from, how much they cost to collect, and how to find out whether they are true.

Newsletter

One Lean idea.
Every two weeks.