Definition
The design discipline that runs before execution, not after variance: design the architecture based on what the read reveals — menu engineering, labor modeling, pricing architecture, concept design, systems structure — so that every decision that will show up in the P&L is made with the P&L in view before it is made.
Explanation
Most operators design after the fact. The number comes in soft, and the operator reacts — repricing, recutting labor, re-engineering the menu in response to a variance that already happened. [Operational Performance Engineering] reverses the sequence: the design work happens with the outcome in view from the start, so the P&L is a confirmation of the design instead of a correction to it.
The discipline only works as one piece of a larger sequence. Design feeds Execution — the deliberate delivery of a designed standard, in real time, on the stage, through the cast — because execution without design produces inconsistent results no matter how hard the cast works. Execution then feeds [The Re-Read], which checks what execution actually produced against what the design intended. And the re-read feeds [Recalibration], which updates the design itself when the gap reveals the original design is no longer current.
Skip any step and the loop breaks. Design without execution is a plan nobody ran. Execution without a re-read is data nobody used. A re-read without recalibration is an accurate diagnosis nobody acted on. The engineering only compounds when all four steps run as one continuous loop, not as isolated fixes applied whenever something breaks.



