Six leading indicators predict program stall before the financial dashboard moves. Cycle time, right-first-time, exception ratio, override rate, platform reuse, decision velocity. Watch them monthly. Act when any drifts ten percent off baseline.
Why leading indicators
Operating health shows up in lagging financial metrics two quarters after the operating system actually slipped. By the time the metric is red, the operating system has been deteriorating for six months. The standard executive dashboard cannot prevent this because the standard executive dashboard is composed of lagging indicators. The diagnostic that prevents the slip uses six leading indicators that move before the financial metrics do.
The six signals are not exotic. They are the operating signals every well-run program watches anyway. The discipline of the diagnostic is treating them as the primary read rather than as supporting detail to the lagging dashboard.
The six signals
Cycle time at the decision unit. When the time from input to decision drifts upward, the operating system is absorbing complexity faster than it is metabolizing it. The drift is visible before the throughput metric moves.
Right-first-time at the same unit. When quality drops, the cost is paid later in rework, escalation, or customer churn. The quality signal leads the cost signal by six to ten weeks.
Exception ratio. When the fraction of work that breaks the standard path climbs, the standard path is becoming a fiction. Exception ratio leads operating cost by a quarter.
Override rate on AI-assisted decisions. When humans override the AI output more often, either the AI is degrading or the policy underneath it has shifted. Either way, attention is required before the financial impact lands.
Platform reuse. When the next use case rebuilds rather than extends, the platform is failing as a platform. Reuse leads cost-per-use-case by one to two quarters.
Decision velocity. When the time from question to commitment lengthens, the governance layer has slowed. Decision velocity leads everything else, because the operating system runs on the decisions the governance layer produces.
How to use the diagnostic
Instrument the six signals from the start of the program. Review them monthly with the program leadership. When any signal degrades by more than ten percent against its baseline, run a focused root cause review before the next monthly. The discipline catches the stall while there is still time to act. Without it, the next read is on the lagging dashboard, by which time the corrective action is harder, slower, and more expensive.
Closing
Operating health is observable before financial health declines. Teams that read the operating signals run a different program than teams that read the financial dashboard. The difference compounds across cycles. The diagnostic is the discipline.