Lean KPI

Lean KPIs are the metrics a shop chooses to actually steer with, distilled down from the much larger menu of things that could be measured. A serious lean operating system has fewer KPIs than most non-lean shops, not more. The temptation is always to add another metric whenever a question comes up. The discipline is to resist. The dashboard that gets walked past every morning is more valuable than the report that runs in a database and never changes anyone's behavior.

"If the dashboard has fifteen metrics, it is not a dashboard. It is a hiding place."

How lean KPIs work

A lean KPI set is small, balanced across categories, visible on the floor, and tied to behavior the shop wants to reinforce. The categories most lean shops cover, with one or two metrics each:

The five categories

• Flow. Throughput, lead time, or work-in-process levels. The pace and smoothness of work moving through the value stream.
• Quality. First-pass yield, parts per million, defects per unit. The reliability of getting the work right the first time.
• Delivery. On-time delivery, schedule adherence. The customer-facing and internal-facing views of hitting commitments.
• Cost. Inventory turns, cost of poor quality, scrap rate. The financial signals of how much the operating system is consuming.
• People. Suggestion rate, skill matrix coverage, safety incidents. The health of the team running the system.

The right number is usually one metric from each category, sometimes two. Five to seven total. Anything more dilutes attention; anything less misses important balance. A KPI dashboard heavy on financial metrics and light on people metrics will optimize toward burning the team out. A dashboard heavy on quality with no flow metric will let lead times grow while everyone celebrates yields. The mix matters.

Where lean KPIs fit on the shop floor

Imagine a 45-person electronics contract manufacturer that has been running lean improvement projects for two years. The shop has a KPI dashboard in a digital tool with 22 metrics tracked weekly. Only management ever looks at it. The floor team runs by tribal knowledge and the daily standup. The owner asks why none of the metrics seem to drive behavior.

The diagnosis is the classic over-measurement trap. The 22 metrics are individually defensible. Together they are too many to steer with, and the floor has correctly concluded that none of them matter very much because none of them gets attention. The fix is unglamorous: pick five. Throughput on the main line. On-time delivery to the top customer. First-pass yield at the constraint operation. Days of inventory on hand. A weekly safety review.

Those five go on a whiteboard near the standup area, updated by hand each morning by the shift leads. The other 17 metrics are still tracked but no longer reported on the floor. Within a quarter, the daily standups have measurably more focused conversations. Improvement projects start tying back to one of the five numbers. The shop becomes easier to steer because there is less to steer with. The lean answer here was subtraction, not addition.

Common mistakes with lean KPIs

• Measuring everything. More metrics is not more insight; it is less attention per metric. Keep the dashboard small.
• Choosing metrics nobody on the floor can influence. A KPI the operators cannot affect is a report, not a steering tool.
• Treating KPIs as direct targets. Pushing for the number directly produces gaming. Fix the process; let the metric reflect the improvement.
• Updating the set too often. Frequent changes train the team to ignore the board. Revise rarely and only with deliberation.
• Reporting from a tool the floor never sees. A KPI dashboard that lives only in a browser tab is invisible to the people doing the work. Put the board where the work happens.

Lean KPIs and related Lean tools

The lean KPI dashboard typically includes several of the canonical metrics that lean shops watch: overall equipment effectiveness for equipment-intensive operations, on-time delivery for customer commitments, inventory turns for working capital, and first-pass yield for quality. The right KPI set evolves with the operating system; revisiting it as part of a periodic lean review is healthy, as long as the revisions are deliberate and the dashboard stays small.