Archive for the ‘F0: The Summers Principle’ Category

The principle claims there are only two causes of outcomes inside the operating domain of the restaurant. Design and default. That claim is exhaustive. It leaves no room for a third. Operators resist this claim harder than any other move the principle makes. They want a third cause. They want luck. They want timing. They […]

There is a distinction inside the principle that most operators miss on the first read, and that missing it produces a specific kind of failure — the operator who believes they are designing when they are actually defaulting, because they have confused two things that look similar from the outside but are opposite in cause. […]

The operator hearing the principle for the first time often lands on a version of this objection: I do not have the capacity to design like a bigger, better-funded, more experienced operator. The principle assumes I can design against my dimensions, but I lack the knowledge, the capital, the time, the authority to do so. […]

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 […]

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, […]