Every operating outcome in a restaurant — every Guest kept or lost, every cast member who stays or leaves, every dollar earned or extracted — exists due to one of two causes: design, or default. That is the principle. One sentence. Every word carries weight. Every operating outcome — not most outcomes, not typical outcomes, […]
A restaurant is a man-made system. The building was built. The lease was signed. The concept was chosen. The menu was designed. The cast was hired. The prices were set. The Guest was invited. Every element of the operation exists because a human decided to put it there — or because a human did not […]
Definition The per-visit Contract signed between operator and Customer across the execution of the [Customer Experience]. The transactional-form Contract that governs one specific visit — from arrival through the check-close and departure. Not the whole-business [Restaurant Contract Architecture] choice. Not accumulated tenure. The single-visit Contract the Customer arrives ready to sign and either does or […]
Definition The transactional experience an operation produces for the Customer — the paired opposite of [Guest Experience]. What the Customer receives across the arc of a visit when the operation is architected for Road 1 execution: a competent transaction delivered efficiently, at fair value, without imposing relational weight the Customer did not come to carry. […]
Definition The measurable distance between the number of people who arrived at the operation seeking hosting and the number of people the operation actually hosted. Not the gap between Guests and Customers as two different populations — the gap between hosting-seekers and actually-hosted within the same population, on the same shift, at the same operation. […]
Definition Someone seeking hosting. The paired opposite of [Customer], who seeks transactional fulfillment. The distinction is not a euphemism preference — it names two different things a person walking through the door might actually want, and the operator’s read of which one is in front of them determines what kind of value the interaction can […]
The Demand This week you name one cast member who delivers something a Guest cannot get from your nearest competitor, and you name what you are doing to develop the next cast member to deliver the same thing — because if the answer is nothing, your differentiation is one departure away from disappearing. The Work […]
The Demand This week you build a formal VoE program as the internal mirror to VoG, because the cast on the stage sees what the office cannot — which standard is not holding, which Guest left frustrated and why, which process is costing covers the operation cannot afford to lose — and that knowledge stays […]
The Demand This week you find out whether your building punishes bad news, because the cast member who sees a problem and says nothing is not indifferent — they have run the math on what honesty costs in your building and decided it costs too much, and you have designed that outcome even if you […]
The Demand This week you design the mechanism that makes surfacing observations cheaper than staying quiet, because the cast already knows which tables are difficult, which menu items draw complaints, which cast members are struggling, and which vendor deliveries are substandard — and they are not telling you, because [Activity Crowding] and [Social Friction] have […]
The Demand This week you build the repair reflex through low-stakes practice, because [Embedded Repair] does not run automatically — it runs when [Social Friction] is low enough that surfacing an error is the obvious move, not a risk, and if cast members hide mistakes because disclosure costs more than concealment, errors compound until they […]
The Demand This week you build the conditions for [Shared Pulse] deliberately — consistent scheduling, a synchronizing pre-shift, a reflective post-shift — because this coordination cannot be installed through training, it builds through reps, and a cast assembled last week will not move like a cast with two hundred shared shifts unless you protect the […]
The Demand This week you build [Anchored Flexibility] by cross-training the cast on secondary strengths before the pressure arrives, because the cast member who has only ever run their primary role will freeze when the shift demands a stretch — the reflex has to be built in low-stakes conditions, not discovered in high-stakes ones. The […]
The Demand This week you build the permission for [Peer Accountability] explicitly, model it visibly, and protect it the moment it happens, because the social default in your building is silence — cast members who see a peer miss the standard and say nothing, not out of indifference but out of a rational calculation that […]
The Demand Before your next labor cut, you name exactly what relational capacity goes with it, because every reduction in the human line is a reduction in the operation’s capacity to produce the relational experience that converts a Guest into a regular — and if you cannot name what you are cutting, you do not […]
The Demand This week you check whether your unit-level leader is running Unit 2 out of fear, out of ego, or without development — because the leader is the rung’s product, and if you build them wrong, Rung 5 collapses Unit 2 back into Unit 1. The Work Review the last five decisions Unit 2’s […]
The Demand Before Unit 2 opens, or this week if it is already open, you confront which parts of Unit 1’s success were system and which parts were you personally — because the operator who skips this confrontation builds Unit 2 as a clone and discovers months in that what made Unit 1 work was […]
The Demand This week you identify which of the three Trust-At-Distance failure modes you are running with Unit 2, and you correct it, because a satellite unit, a hovered-over unit, or a unit run by exception all produce the same outcome — a unit-level leader who never actually leads. The Work Check whether Unit 1’s […]
The Demand This week you name whether “I can’t afford to trust the unit-level leaders to run it my way” reduces to an unbuilt system, an untrained trust muscle, or a moving-target standard — because at this rung the constraint is never bodies, it is the affordability of trust at distance, and until you name […]
The Demand This week you run the four overwatch functions — guide, direct, coach roles, grow the business — as scheduled work, not as a byproduct of being physically present, because overwatch that turns into watching cameras and texting leads about service flow is [The Scapegoat Model] running from a distance, not leadership. The Work […]