Business

Growing KPIs: Which Metrics Actually Reflect the Health of Your Operation

6 min read March 8, 2026

"KPIs are for corporations. I run a small operation — I know how it's going." But "knowing how it's going" is a feeling, not a fact. The feeling says "this month is fine" while you haven't yet counted yield and seen it's 15% below last month from two failed batches. Or "fertilizer consumption is normal" — until you find usage doubled after switching coconut coir suppliers. KPIs don't complicate the work — they're 5–10 numbers that tell you where a problem exists before it becomes a financial loss.

Quick glossary: KPI (Key Performance Indicators) — measurable numerical metrics reflecting the state of a production process; tracked over time to detect deviations from normal. Baseline — the average KPI value over a normal reporting period; deviation from baseline is a signal to investigate. Benchmark — a reference KPI value for comparison (industry standards or your own best result).

Why "Going by Feel" Doesn't Scale

With two microgreen trays, the grower remembers everything: when seeded, how much harvested, what was spent. With 50 trays per week, memory can no longer keep up. With 200 — it's impossible without a system.

But even in small operations, intuition fails systematically in one direction: it catches large deviations and misses small ones. A 15% yield drop that happens gradually over two months goes unnoticed. But 15% × 200 trays × sale price = a significant sum every month.

KPIs give you trends in numbers. A deviation becomes visible when it appears — not three months later when it's already substantial.

Eight KPIs That Actually Reflect Production Health

1. Yield per unit area or tray (g/tray or kg/m²)

The core productivity metric. For microgreens: grams per standard tray. For leafy greens: kg/m² per cycle. For tomatoes: kg per plant per season.

Deviation: yield drops 10%+ — check EC and pH for recent batches, seed quality, lighting. See the article on yield calculation for detail.

2. Waste rate (% of harvested product)

The share of product that doesn't meet commercial quality at harvest. Normal for microgreens: below 5%. Above 10% — a systemic problem exists (disease, uneven lighting, unstable EC).

3. Cycle duration (days from seeding to harvest)

Compare against the expected duration for the crop and variety. Cycle extended by 3–5 days? Most commonly: insufficient DLI, lower-than-optimal temperature, or EC below the optimum. A metric that correlates directly with lighting and temperature management.

4. Fertilizer consumption per unit of product (g fertilizer/kg product)

Rising fertilizer use without yield change indicates either declining uptake efficiency (pH problem, Root Rot) or increased drainage loss. See the article on resource consumption for detail.

5. Drain EC relative to feed EC

Drain EC consistently more than 1.0 mS/cm above feed — salt accumulation in the substrate. A trend building over weeks signals that irrigation regime or nutrient recipe no longer matches plant uptake.

6. Successful batch rate (batches without significant deviations)

The ratio of batches harvested without deviations (disease, pests, uneven germination, above-normal waste) to total batches in a month. Target: 90%+. Consistently below 80% — a recurring systemic problem.

7. Water consumption per unit of product (L/kg or L/tray)

Rising consumption without yield change — possible leak, or the system has become less efficient (increased drainage, shift from recirculating to run-to-waste). Decreasing — either improved efficiency or underwatering.

8. Time from harvest to dispatch (hours)

For perishables — the lower the better. Microgreens with proper cold chain keep 7–10 days, but quality is best when dispatched the same or next day. A KPI that reveals logistics or demand problems.

How to Track: a Minimal System

A table — paper or digital — with these eight metrics per month or per week. No CRM or ERP required. Google Sheets or a notebook and 15 minutes once a week to calculate.

Baseline: spend the first 2–3 months accumulating data — don't evaluate, just record. Then you have an average, and deviations from that average become visible.

Response rule: any metric deviating from baseline by more than 15% for two consecutive weeks is cause to investigate. A one-time deviation may be noise. A sustained deviation is a systemic change.

What You Don't Need to Measure Constantly

KPIs should be minimal and actionable. You don't need to:

  • Measure EC every 30 minutes if the system is stable
  • Track every tray individually if batch yield is consistent
  • Monitor 20 metrics — attention fragments and analysis never happens

The eight above are enough to catch 90% of real production problems at an early stage.

Three Mistakes That Cost the Most

Tracking KPIs without responding to deviations. "Yield dropped 20% — noted and moved on." KPIs only have value if a deviation triggers a root-cause investigation. If deviations are logged without response, the time spent tracking is wasted.

Calculating KPIs too infrequently to catch a trend. Quarterly — a trend that started two months ago has already become a financial loss. Weekly or monthly is the right frequency for production KPIs.

Choosing metrics that are easy to calculate rather than important. "I count how many trays I seeded" — easy. But yield per tray and waste rate tell you more. Choose KPIs for their informational value, not calculation convenience.

How to Know the KPI System Is Working

When any of the eight metrics deviates by more than 15% for two weeks, you have a specific hypothesis about the cause and a plan to verify it. Once a month there is a review of all eight metrics compared to the prior month. Your business plan and profitability forecast are updated with current data — not based on initial assumptions made before production began.

For deeper understanding: Yield Calculation: How to Measure It and What Affects Yield Across Different Systems — explains the yield calculation methodology that underpins the most important production KPI, without which all other metrics lose context.