4.X — The Numbers You’re Watching Aren’t Named #
Here is what happens in almost every operation I walk into: the operator hands me a spreadsheet. Sometimes it’s printed. Sometimes it’s on a screen. It has numbers on it — — labor cost, food cost, covers, revenue per available seat, Guest scores, maybe a training-hours line somebody’s proud of. The operator looks at the spreadsheet the way a pilot looks at instruments. Serious. In command. And then I ask one question: what is each of those numbers measuring, specifically, against what objective, inside what area of work, rolling up to what result you actually care about?
Silence. Then some version of: “Well, you know — — it’s the labor number. We watch the labor number.”
That’s a Non-Named Number. And almost every operator in this industry is running on a dashboard full of them.
A Non-Named Number is a KPI the operator holds without the scaffolding above it. No Key Performance Area to locate the work responsible. No Key Performance Objective to state what specifically must be achieved. No Key Result Area to name the broad outcome domain the whole thing rolls up to. The number isn’t anonymous because it can’t be named. It’s anonymous because the operator hasn’t done the intellectual work of building the stack. A number without its KPA, KPO, and KRA above it is not a metric. It’s a measurement with nowhere to live and no one truly accountable for it — — and it will lie to you every single time.
Non-Named Numbers create the illusion of measurement without the discipline of accountability. The operator can tell you what the number is. They cannot tell you who specifically owns the path to it, what it needs to hit to count as a win, or what broader result it is contributing to. When the number moves — — in either direction — — the operator has no clean causal read. They guess. They call a meeting. They add a line to the next shift huddle. They watch the number for a few more weeks.
What they do not do is run the stack.
Business people latch onto one thing because it’s simple, without understanding the entire intellectual framework. They hear “KPI” in a seminar or read it in a management book, go back to their operation, and start tracking things. Food cost. Labor. Guest scores. They put them in a spreadsheet and they feel like they’re managing performance. They are not. They are accumulating numbers. A dashboard is not an operation.
Here is the stack that gives the number its meaning.
KRA — Key Result Area. The broad outcome domain. Revenue Growth. Guest Retention. Labor Efficiency. This is the altitude where the business result lives.
KPO — Key Performance Objective. The specific, time-bound target inside the KRA. Grow new-Guest revenue 20% by year end. Reduce server turnover to below 40% in the next two periods. This is where the result gets a deadline and a number.
KPA — Key Performance Area. The area of work responsible for delivering the KPO. New Guest Acquisition. Cast Development. Scheduling Discipline. This is where accountability lives — the specific domain of work that owns the outcome.
KPI — Key Performance Indicator. The number that tells you whether the KPA is delivering. $100k in new sales per month. Two coaching conversations per manager per week. SPLH above $58 on Tuesday lunch. This is the instrument. Not the result. The instrument.
Most operators hold the KPI and drop everything above it. The number floats without an objective, without a performance area, without a result domain. It is a measurement with nowhere to live and no one truly accountable for it. That is not performance management. That is a dashboard with the meaning stripped out.
Run the stack. Every number you track should have all four layers named. If you cannot name them, you do not own the number. You are just watching it.
The Two Sides of the Loop #
Here is where most operators make the second mistake — and it is just as expensive as the first.
There are two kinds of numbers in your operation. Leading indicators live on the stage and in the kitchen. They are the numbers you can act on in real time: cover counts, ticket times, table turns, void and comp rates, server check averages, repeat Guest rate, prep accuracy, line speed. These are KPA-altitude numbers — they tell you whether the work is happening right now, in this shift, before the result is locked.
Lagging indicators are the financial outcomes. Food cost percentage. Labor cost percentage. Prime cost. Flow-through. These numbers report what already happened. By the time the P&L lands on your desk, the shifts that produced it are weeks behind you. The reporting lag is structural — it is not one shift you missed, it is every shift that fed into the period close.
Most operators treat lagging numbers as scoreboard. They read the food cost, file it, and run the next month the same way. The lag becomes inert because the read stops at the number.
That is the wrong read.
Lagging numbers are not tactical. They are strategic. They are not telling you how to run tonight’s shift — they are telling you how to build next month’s plan. They tell you whether your menu mix is funding the model you think it is funding. They tell you where to cut, where to invest, where to hold. They tell you which periods, dayparts, stations, or items are carrying weight and which are bleeding. They tell you when to renegotiate a vendor, drop a SKU, restage labor, or kill a daypart. They tell you whether the upstream work — the leading indicators, the stage reads, the coaching, the pre-shift preparation — is producing the financial outcome the plan targeted.
The lag is what makes them strategic. The operator does not run today’s shift off last month’s food cost — but absolutely sets next month’s plan off it.
The operator who watches only lagging numbers manages the business strategically and flies blind on the stage. The operator who watches only leading indicators runs shifts well and manages the business badly. Both halves are required. Neither is optional.
Leading indicators tell you what is happening. Lagging indicators tell you whether it matters. Read both. Act on both. At the right altitude. That is the loop — and the operator who closes it is the one whose numbers eventually start making sense.
