Key Failure Indicator

Every company tracks KPIs. Revenue growth, customer acquisition cost, net promoter score, monthly active users — the dashboards glow green when things go well and amber when things slow down. What almost no company tracks with the same rigor is the inverse: the leading indicators of failure. Key Failure Indicators. KFIs. The metrics that tell you not how you're winning but how you're dying.

The distinction is not semantic. KPIs are lagging indicators dressed in real-time clothing. Revenue this quarter reflects decisions made two quarters ago. Churn this month reflects dissatisfaction that accumulated over the last six months. NPS this week reflects experiences from last week. By the time a KPI turns red, the damage is already compounding. KFIs operate on a different timescale. They track the precursors — the hairline fractures that precede the break. A KFI doesn't tell you that the building has collapsed. It tells you that the foundation is shifting.

Amazon tracks "defects per million opportunities" — DPMO. Not because Jeff Bezos celebrates low defect rates. Because defects compound. A single misrouted package is a $5 cost. A million misrouted packages in a quarter is a $5 million cost, plus customer service escalations, plus refund processing, plus the invisible cost of customers who never return. Amazon's obsession with DPMO is not quality management. It is failure prevention at scale. The KFI framework says: don't wait for the revenue decline that a million defects will eventually cause. Track the defects now, in real time, and kill the failure before it metastasises.

Bridgewater Associates operates on a different version of the same principle. Ray Dalio tracks "believability-weighted disagreement" among senior investment professionals. When people with high track records in a specific domain disagree strongly about a decision, that disagreement is itself a failure indicator. Not because disagreement is bad — Dalio's entire culture is built on radical transparency and productive conflict — but because high disagreement among credible people signals that the decision-making process is broken. Either the data is ambiguous, the framework is flawed, or critical information is missing. The KFI isn't the investment loss that might follow. The KFI is the disagreement pattern that precedes it.

The logic generalises. Every system that fails gives off warning signals before it breaks. Bridges develop micro-cracks before they collapse. Economies develop yield-curve inversions before they enter recession. Startups develop rising customer complaints before they lose market share. The question is not whether the warning signals exist. The question is whether anyone is measuring them. KPIs measure the health of the system's outputs. KFIs measure the health of the system's inputs and processes — the upstream variables that, if they deteriorate, will inevitably degrade the outputs that KPIs track. The best operators don't wait for the output to degrade. They monitor the inputs. They track what kills them, not what celebrates them.

The practical challenge is that KFIs require intellectual honesty that most organisations lack. A KPI dashboard that shows revenue growing 30% year-over-year makes the executive team feel competent. A KFI dashboard that shows engineering defect rates climbing, employee attrition accelerating in the top-performer cohort, and customer complaint severity increasing makes the same executive team feel threatened. The KFI dashboard is delivering the more valuable information — but it requires a culture that can absorb uncomfortable truths without shooting the messenger.