4.X — Leading vs. Lagging: Both Sides of the Loop #
There are two kinds of numbers in your operation and they do different jobs. Most operators run on one side only and wonder why the other keeps surprising them.
Profit metrics — — food cost %, labor cost %, prime cost — — are lagging outcomes. They report what already happened. By the time the P&L shows up, the shifts are over. The reporting lag is structural: it’s not one shift you missed, it’s every shift that fed into the period close.
The stage work — — leading indicators — — is where you have leverage in real time. Cover counts, ticket times, table turns, void and comp rates, server check averages, repeat Guest rate, complaint count, recovery saves, prep accuracy, line speed, hand-off cleanliness. That is where the operator moves outcomes before they become history.
The lag does not make the lagging numbers useless. It changes what they are for.
Lagging numbers are how you decide: whether the menu mix is funding the model you think it’s funding; where to cut, where to invest, where to hold; which periods, dayparts, stations, or items are carrying weight and which are bleeding; when to renegotiate a vendor, drop a SKU, restage labor, or kill a daypart; whether the upstream work is producing the financial outcome the plan targeted.
The lag is what makes lagging numbers strategic instead of tactical. You don’t run today’s shift off last month’s food cost — — but you absolutely set next month’s plan off it.
The operator who only watches lagging numbers is doing strategic-altitude work without the upstream feedback loop. The operator who only watches leading indicators is running shifts well and managing the business badly. Both sides are required. Neither is optional.
There are two altitude failures inside Non-Named Numbers:
The KPI-altitude failure: holding the indicator without the KRA / KPO / KPA scaffolding. The four-layer stack is the name. A number without it floats free of accountability.
The strategic-altitude failure: treating lagging outcomes as scoreboard instead of as the next plan’s input. The operator sees food cost %, files it, runs the next month the same way. The lag becomes inert because the read stops at the number.
Both failures are operators dropping the scaffolding around a number. At KPI-altitude, they drop the upstream definitions. At strategic altitude, they drop the downstream decision loop.
The Read is where leading and lagging meet. The numbers pulled in the Read fold lagging financials into next-period planning, while the stage reads run the leading indicators in real time. That is the complete loop. Both sides feeding each other. That is what performance management actually looks like.
