library

Common Operational KPI Library

A practical, team-ready catalog of common operational KPIs organized by domain (safety, quality, delivery, cost, reliability). Each entry includes a clear definition, formula, typical targets and caveats, data-source notes, recommended visualization, review cadence, and huddle coaching cues to help teams surface meaningful actions instead of vanity metrics.

Welcome — choose KPIs that predict problems and prompt action

Good KPIs help teams see the right problems early and focus limited time on the highest priority actions. This library organizes reliable operational KPIs by domain and gives practical definition, calculation notes, data-source guidance, recommended visualizations, typical targets (with caveats), review cadence, and coaching cues for huddles.

How to use this library

Pick a small set of KPIs that are:

  • Clearly defined with unambiguous formulas and data sources.
  • Predictive or leading where possible (help you prevent problems).
  • Actionable at the team level — the team can influence the outcome.
  • Stable enough to show trends but sensitive enough to detect real change.

Use the coaching cues during daily or weekly huddles to translate numbers into actions. Avoid vanity metrics that look good but don’t improve outcomes.

Selection checklist (quick)

  • Is the metric tied to an explicit outcome the team cares about?
  • Is the formula and data source documented and owned?
  • Can the team take one or more concrete actions that move the metric?
  • Does it minimize perverse incentives (e.g., productivity at the cost of safety)?
  • Is the review cadence and escalation path defined?

KPIs by domain — practical entries

Safety

Total Recordable Incident Rate (TRIR)

Definition: Number of OSHA-recordable incidents per 200,000 work hours.

Formula: (Number of recordable incidents / Total hours worked) × 200,000

Data notes: Ensure consistent incident classification and complete hours worked. TRIR is lagging — pair with near-miss and leading indicators.

Visualization: Line chart with 12–24 month trend and threshold bands.

Typical target: Industry-dependent; focus first on downward trend rather than a fixed number.

Review cadence: Weekly for huddle highlights; monthly deeper review.

Huddle coaching cues: What near-misses preceded this incident? What preventive action can we pilot today?

Safety Observations / Interactions

Definition: Number of proactive safety observations or coaching interactions completed.

Formula: Count of validated observations per period (week/month).

Why it helps: Leading indicator that correlates with reduced incidents when quality of observations is high.

Coaching cues: What did we observe? Who will follow up and by when?

Quality

First Pass Yield (FPY)

Definition: Percentage of units that pass quality inspection without rework.

Formula: (Good units produced without rework / Total units started) × 100

Data notes: Agree on what constitutes 'rework' and how scrap is recorded.

Visualization: Bar/line with process step breakdown and Pareto of defect types.

Typical target: Depends on product complexity; improvement focus is on defect type elimination.

Huddle cues: Which defect types are most frequent? What countermeasure will we try this shift?

Customer Rejects / PPM

Definition: Parts per million (PPM) of customer rejects or returns.

Formula: (Number of defective items returned / Total shipped) × 1,000,000

Coaching cues: Which root causes link to customer feedback? Are there containment actions?

Delivery

On-Time In-Full (OTIF)

Definition: Percentage of orders delivered both on time and complete.

Formula: (Number of orders delivered on-time and in-full / Total orders) × 100

Data notes: Define 'on time' and acceptable delivery windows; align with logistics and customer terms.

Visualization: Weekly trend and rolling 13-week average by customer or product family.

Huddle cues: Which orders are at risk today? Who owns the escalation?

Lead Time / Cycle Time

Definition: End-to-end time for a unit/order to flow through a process.

Formula: Timestamp(end) − Timestamp(start) (report median and 90th percentile)

Why report percentiles: Average can hide outliers; 90th percentile highlights extreme delays.

Cost

Cost per Unit

Definition: Total production cost allocated per unit (material + labor + allocated overhead).

Notes: Use only for trend and variance analysis — cost allocations vary and can mislead if compared across sites without harmonization.

Huddle cues: What small, testable changes could reduce the unit cost without harming quality or safety?

Scrap Rate

Definition: Percentage of materials scrapped versus input.

Formula: (Scrap quantity / Total input quantity) × 100

Visualization: Pareto of scrap reasons, trend over time.

Reliability & Performance

OEE (Overall Equipment Effectiveness)

Definition: A combined measure: Availability × Performance × Quality.

Formula: Availability (%) × Performance (%) × Quality (%) — report each element separately as well as combined OEE.

Data notes: Define planned vs. unplanned downtime, cycle time targets, and quality acceptance criteria.

Visualization: Daily trend with event markers and downtime reason categories.

Huddle cues: What were the top downtime causes yesterday? Which countermeasure will we test?

MTTR / MTBF

Definition: Mean Time To Repair (MTTR) and Mean Time Between Failures (MTBF) for critical assets.

Formula: MTTR = Total corrective maintenance time / Number of repairs. MTBF = Total operating time / Number of failures.

Use: Track for critical assets; combine with availability metrics.

Recommended review cadence

  • Daily huddle: 1–3 leading KPIs that surfaced risk today (safety observations, throughput, critical machine status).
  • Weekly team review: broader set including FPY, OTIF, scrap — focus on trends and short experiments.
  • Monthly operational review: cost per unit, OEE trends, longer-term reliability issues and investments.

Coaching cues for huddles (templates)

Use short, consistent questions to turn metrics into actions. Example huddle prompts:

  • What changed since the last huddle? (Data highlight)
  • Why did that change happen? (Hypothesis)
  • What immediate containment or support is needed? (Owner, due date)
  • What experiment will we run to improve this metric? (Plan, measure)

Common pitfalls and how to avoid them

  • Unclear definitions — document formulas, data sources, owners.
  • Too many metrics — focus on a few that drive behavior.
  • Vanity metrics — remove metrics that don’t lead to action or improvement.
  • Blame culture — use metrics to learn and experiment, not punish.

Next steps and practical templates

Start by agreeing on definitions for 3–5 KPIs for your team. Capture:

  1. Metric name and formula
  2. Primary data source and owner
  3. Target (or improvement goal) and acceptable variance
  4. Review cadence and huddle prompt

If you want an interactive KPI selection template and a persistent team KPI card that stores your choices and tracks huddle notes, consider adding an interactive KPI chooser and a small team tracker. (See Capability Enhancements below.)

Image search phrase

kpi library dashboard

Discuss Ask the Librarian

Discussion

Comments and conversation will live here.