This piece is not a rejection of Will Guidara. Guidara stated a principle my framework adopts and extends — that the operator’s unreasonable standard belongs applied to how the Guest feels, not to plate technique. Eleven Madison Park is the most credible external validation source in the industry for the relational model. What this piece prosecutes is the counsel class’s inability to decompose the principle from its execution — the trade press, the conference circuit, and the ceiling-lowering prescriptionists who have all reduced Guidara’s argument to a script that runs at one band. All three moves prove the same failure. The counsel class cannot read principle-vs-execution.
Recent Bon Appétit coverage argues that operators should adopt “reasonable hospitality” — that the standard the industry has canonized around Unreasonable Hospitality is unsustainable, that Guests should learn to embrace their role in the exchange, and that the language of “dreamweaving” and “bespoke gestures” has become a burden the working operator cannot carry. The piece points to real damage. It gets the specimen right and the mechanism wrong. And its prescription would harm the same operators it claims to defend.
The Counsel Class Cannot Decompose Principle From Execution
The counsel class only knows two operating modes: canonize the practitioner or condemn the practice. Both are content. Neither is architecture.
The canonizers read Unreasonable Hospitality, extract the executable moves — the hot dog run, the dreamweaver role, the bespoke gesture — and prescribe them at every band as if the moves were the principle. The condemners read the harm the canonizers produce, extract the exhaustion, and prescribe the ceiling be lowered as if the ceiling were the problem. Neither carries the vocabulary to decompose what Guidara actually said from what a $65 PPA operator can actually execute.
The modern hospitality gospel was written at restaurants doing $300 per Guest. Most operators are running at $65. That is not a mindset gap. It is a math gap. And the counsel class cannot close it, because closing it requires vocabulary the counsel class has never carried.
The Mislabeled Discipline
The Bon Appétit prosecution names “hospitality” as the problem. What it is actually describing is service. Guidara’s most important distinction — the one operators still get wrong — is that hospitality is how you make people feel when you do the things, and service is the things you do. Service is operational. Hospitality is relational. You can have perfect service and zero hospitality. You cannot have hospitality without adequate service underneath it.
The Bon Appétit piece conflates the two throughout. The exhausted server memorizing preferences, the pressure to remember a Guest’s birthday, the choreographed table-touch — those are service execution moves. When they are executed without the operator having designed the relational contract underneath them, they land hollow, and the exhaustion is real. But the exhaustion is a design failure, not a hospitality failure. The counsel class cannot see the difference because it does not carry the [Hospitality-Service Distinction] as vocabulary. So the prescription lands on the wrong object. Fix the service execution and the “hospitality problem” resolves.
At the cumulative level: every time the counsel class prosecutes hospitality when it means service, it corrodes the operator’s ability to teach the distinction to their own cast. The cast reads the trade press. The cast picks up the frame. The kitchen manager and the lead pick up the frame. The operator now has to un-teach the counsel class’s confusion before they can teach the actual work.
What the operator would do instead: name the two disciplines in-house. Draw the line explicitly. Every training document, every pre-shift, every one-on-one carries the distinction. The exhausted server is not exhausted by hospitality. The exhausted server is exhausted by service moves the operator asked them to execute without the [Restaurant Contract Architecture] that would make the moves legible to the Guest. Fix the contract. Watch the exhaustion resolve.
The Unspoken Exception
The counsel class runs its whole conversation about Guidara from inside an unstated frame: fine dining is a different category with different rules. This is the [Fine-Dining Exception] the industry has been running for forty years. It is not physics. It is a rhetorical carve-out that protects the top from architectural examination and protects everyone else from having to name their own composition.
The exception says: at $300 PPA, the food justifies the price, so the hospitality can be as elaborate as the operator can afford. At $65 PPA, the food has to carry the ticket, so the hospitality has to shrink to whatever labor is left after the plate is on the table. That framing sounds like sense. It is not physics. It is arbitrage.
The physics: at any band, the totality of the Guest’s contract with the operation produces the ratification ceiling. The food is one component of that totality at band-appropriate composition weight. Eleven Madison Park at its ceiling was composed at fine-dining weight across every component — cast, room, pacing, service execution, hospitality architecture, Guest-cohort read — with the food-component at fine-dining weight inside the totality. The food alone did not produce the ceiling. The totality did. The dreamweaver was one component in that totality. The neighborhood Italian’s maître ‘d remembering the booth is the same architectural move at a different composition weight.
The counsel class cannot see this because [Fine-Dining Exception] is baked into every read it produces. It reads Guidara’s execution weights as fine-dining substance rather than composition weight at band. Once the exception falls, the principle scales. The exception has to fall before the pair — canonizer and condemner — can be read for what they actually are.
At the cumulative level: every essay written from inside the exception reinforces the operator’s belief that hospitality-at-band is a lesser thing rather than the correct architecture at their composition weight. Counsel-class writing since the book landed has produced a generation of operators who read Guidara, hear the exception, and conclude the moves are not for them. They are for them. The exception is the arbitrage.
What the operator would do instead: refuse the exception in your own operating language. Every time you hear yourself or a peer describe hospitality as a fine-dining thing you can’t afford, name the exception operating in the sentence. Then compose your Product at your band’s weight and price to your band’s ceiling.
The Lowered Ceiling
The Bon Appétit prescription is “reasonable hospitality” — meet the Guest’s basic expectations, don’t try to exceed them, stop chasing the magic. This is a Road 1 concession. It solves the operator’s execution problem by lowering the Guest’s contract. Which means the operator now competes on the same axis as every quick-service and casual competitor within a mile: price, throughput, and adequate execution.
The operator who lowers their ceiling loses the one asset that separates them from the delivery apps. The Guest can already get “reasonable” from a hundred faster, cheaper alternatives. What the Guest cannot get from those alternatives is the relational contract a Road 2 operation can design at its band. The lowered-ceiling move surrenders the moat.
At the cumulative level: when the counsel class prescribes ceiling-lowering across every band, it produces a market where independent restaurants converge on quick-service architecture at full-service prices. That is the middle-market squeeze the industry has been writing about for fifteen years without recognizing that the counsel class is one of its primary drivers.
What the operator would do instead: raise the design standard, not the execution burden. [Band-Appropriate Investment] means composing hospitality moves whose input cost sits inside your unit economics and whose ratification value sits at your band’s ceiling. The neighborhood Italian’s booth-recognition move costs almost nothing and delivers full contract ratification at its band. That is a raised ceiling executed at the correct band. That is the move the counsel class cannot see.
The Diner Moral Instruction
The Bon Appétit piece includes a passage about how diners must “learn to embrace their role” — that Guests bear responsibility for holding up their side of the hospitality exchange, that the two-way street of restaurant hospitality has become a one-way transaction, and that the industry should be teaching Guests better behavior.
This is a category error. Guests are produced by the operation’s architecture. The operator designs the contract. The operator designs the moves that ratify the contract. The Guest reads the contract, decides whether to enter it, and behaves accordingly. If the Guest is behaving badly, one of three things is true: the operation’s contract is unclear, the operation is attracting the wrong cohort, or the operation’s execution is producing the misbehavior. In all three cases the pattern lives inside the operation, not inside the Guest.
The counsel class defaults to moralizing Guests when it cannot design contracts. It cannot design contracts because it does not carry the vocabulary — no [Restaurant Contract Architecture], no [Guest-Customer Distinction], no [Guest Production Architecture]. So it teaches the Guest a lesson instead of teaching the operator the move.
At the cumulative level: when the counsel class publishes essays instructing Guests in proper behavior, the operator absorbs the frame and starts running the same argument in-house. The kitchen manager gets it. The lead gets it. The floor culture starts orienting toward Guest-fault attribution. Which is a cast culture that will not produce ratifiable hospitality at any band.
What the operator would do instead: run [Voice Of The Guest Harvest Architecture] on the specific behaviors the counsel class calls Guest failure. Read the pattern back to the contract. Redesign the contract. Watch the Guest behavior shift.
Both Positions Concede Magic Is A Borrowed Thing
The four arguments above are symptoms. The deeper mechanism is that the counsel class only knows how to canonize or condemn — because it has never carried the vocabulary that would let it teach principle-vs-execution.
The canonizers publish the executable moves as if the moves were the principle. The dreamweaver, the hot dog run, the bespoke gesture — reproduced as prescription at every band. Which is why an operator running at $65 PPA reads the book, tries to install a dreamweaver role their unit economics cannot support, burns their cast out inside a quarter, and blames the principle when the execution collapses.
The condemners publish the exhaustion the canonizers produce as if the principle were the problem. Which is why the Bon Appétit prescription is a lowered ceiling instead of a corrected execution frame. The condemners are reacting to the canonizers’ misread, not to the principle. And their prescription harms exactly the operators the canonizers already harmed.
Both positions concede the same thing. The canonizer says perform the borrowed moves. The condemner says stop performing them. Neither position sees magic as something the operator engineers inside their own brand architecture at their own composition weight. Both treat magic as the imported thing — one telling the operator to import it, the other telling them to give up on it. Neither one teaches the operator to build their own.
That is the failure the pair prosecutes. You don’t stop engineering the magic. You engineer it inside your own brand architecture. The magic is not the dreamweaver role. The magic is not the hot dog run. The magic is what happens when the operator has designed the [Restaurant Contract Architecture] at their band, composed the moves at their band’s weight, and executed the moves inside a Guest cohort that has entered the contract. That magic is engineerable at any band. What is not engineerable is a borrowed magic imported from a band above yours. The Bon Appétit prescription tells you to stop trying. The counsel class canonization tells you to install someone else’s moves. Both are wrong. The correct move is the third position neither one carries.
Neither can read what Guidara actually said as a principle. A principle scales. A principle takes composition weight from its band and re-composes at other bands with different weights and different specific moves — same principle, band-appropriate execution. Guidara’s principle is that the operator’s unreasonable standard belongs on how the Guest feels. That principle runs at $300 PPA. It also runs at $65. What changes is composition weight, not the principle.
The counsel class cannot teach [Band-Appropriate Investment] because it has never named [Concept Band]. It cannot refuse [Fine-Dining Exception] because refusing it would eliminate half of what the counsel class writes about. It cannot decompose principle-vs-execution because doing so would reveal that the class itself has been running an arbitrage — selling operators a script rather than teaching them how to engineer their own.
The modern hospitality gospel was written at $300 PPA. Most operators are running at $65. Neither the canonizers nor the condemners have closed that 4.6x gap. Which is why the years of counsel-class writing since the book landed have produced a generation of exhausted operators running lowered ceilings while blaming the principle they never actually engineered at their own band.
Four Tests That Sort Counsel-Class Writing From Architecture
Four tests. Run them against your operation and against the pieces you have been reading.
Test One — The Principle-Execution Decomposition Test. Pick any counsel-class piece you have read in the last six months about Guidara, Unreasonable Hospitality, or the state of hospitality in the industry. Can you name — from the piece — the principle it is arguing about, separate from any specific execution move it references? If the piece cannot decompose the principle from the moves, it is content, not architecture. Discard.
Test Two — The Band Test. Look at the hospitality moves currently running in your operation. Name the [Concept Band] each move was designed for. If a move was designed at a band above yours, it is running as vantage substitution — imported from a higher band, executed at yours, producing exhaustion. Redesign or kill.
Test Three — The Exception Test. Listen to your own operating language for a week. Every time you use the phrase “fine dining” or hear yourself describe a hospitality move as something a fine-dining place would do, name the [Fine-Dining Exception] operating in the sentence. Then compose the equivalent move at your band’s composition weight. Practice the refusal until the exception stops being available as vocabulary.
Test Four — The Diner-Blame Test. Look at your last thirty days of Guest complaints, negative reviews, and cast frustration with Guest behavior. For each item, ask whether the operation’s contract could be redesigned to produce different Guest behavior. The number of items where the answer is yes is the number of items the counsel class taught you to attribute to the Guest instead of to the contract. Read each item back to the contract. Redesign as indicated.
Score sort: three or four failures across the tests means you are running counsel-class frames inside your operation. The frames are corroding your ability to design at your band. Rebuild the operating language before rebuilding the moves.
The Decomposition Read You Run Tomorrow
Pull three sentences from any counsel-class piece you have read about hospitality in the last quarter. For each sentence, ask two questions: what principle is this sentence teaching, and what band was the execution designed for. If either question cannot be answered from the sentence, the sentence is not architecture. Then compose the equivalent architectural read in your own operating language, at your band’s composition weight. Write it down. Post it in the office. That single practice — decomposing principle from execution, and naming your band — is the read discipline the counsel class has never taught and the one that separates operators who use Guidara from operators who blame him.
Engineer The Magic Inside Your Own Architecture
The counsel class cannot read the template because reading the template would require vocabulary the counsel class has never carried. Which is why the industry keeps producing the same hospitality conversation every six months and never advances the operator’s actual read. The failure is not Guidara. The failure is not Unreasonable Hospitality as a body of work. The failure is that the interpretive class between the practitioner and the working operator cannot decompose principle from execution — so the operator gets sold a script that runs at one band, blames themselves when it breaks, and never gets taught the architecture that would let them engineer the magic at their own.
You don’t stop engineering the magic. You engineer it inside your own brand architecture. That is the move neither position in the counsel-class conversation can name — and it is the only move that closes the gap they have been talking past for years.
To understand the ideal state, go to Restaurant Physics.
Positions On The Record
-
Be As Unreasonable About How You Make People Feel — https://kb.jeffreysummers.com/be-as-unreasonable-about-how-you-make-people-feel
-
The Casual FullService Problem Isn’t The Food — https://jeffreysummers.com/the-casual-fullservice-problem-isnt-the-food
-
Moving From Service To Hospitality — https://kb.jeffreysummers.com/moving-from-service-to-hospitality
-
Reimagining Hospitality: The Experiential Loop — https://kb.jeffreysummers.com/reimagining-hospitality-the-experiential-loop
-
Hospitality Or Manipulation — https://kb.jeffreysummers.com/hospitality-or-manipulation
-
You Cannot Script Hospitality — https://kb.jeffreysummers.com/you-cannot-script-hospitality
-
Never Treat A Guest Better Than An Employee — https://kb.jeffreysummers.com/never-treat-a-guest-better-than-an-employee
-
I Have Been Saying The Same Things For Decades — https://jeffreysummers.com/i-have-been-saying-the-same-things-for-decades
Term Definitions From The Knowledge Base
-
[Hospitality-Service Distinction] — https://kb.jeffreysummers.com/hospitality-service-distinction
-
[Fine-Dining Exception] — https://kb.jeffreysummers.com/fine-dining-exception
-
[Price Ceiling Physics] — https://kb.jeffreysummers.com/price-ceiling-physics
-
[Concept Band] — https://kb.jeffreysummers.com/the-concept-band
-
[Band-Appropriate Investment] — https://kb.jeffreysummers.com/band-appropriate-investment
-
[Restaurant Contract Architecture] — https://kb.jeffreysummers.com/restaurant-contract-architecture
-
[Guest-Customer Distinction] — https://kb.jeffreysummers.com/guest-customer-distinction
-
[Guest Production Architecture] — https://kb.jeffreysummers.com/guest-production-architecture
-
[Voice Of The Guest Harvest Architecture] — https://kb.jeffreysummers.com/voice-of-the-guest-harvest-architecture
-
[Vantage Substitution] — https://kb.jeffreysummers.com/vantage-substitution
-
[Totality Scaling] — https://kb.jeffreysummers.com/totality-scaling
-
[Product Composition] — https://kb.jeffreysummers.com/product-composition
