Author Archive

Once the operator accepts that there are only two causes, they need a diagnostic tool. Some way to know, in a given moment, which cause is running. Design or default. Right thinking or wrong thinking. Engineered intent or its absence. The operator cannot judge that from the inside of their own thinking. Intention feels sincere […]

The Summers Principle is stated. Its extensions are stated. Its boundaries are named. The operator has read F0 through and either accepts the principle or does not. The question at this point is what the operator does next. The answer is small and specific. Not a dramatic reorganization. Not a sweeping strategic overhaul. Not a […]

The Summers Principle produces the operational discipline that allows the operator to run the operation by design rather than default. That discipline has a name in the framework: the Read. The Read is the operator’s continuous act of seeing what mode is running on which dimension, tracing outcomes to their causes, and deciding where design […]

The framework teaches five fundamentals: Perspective, Product, People, Performance, Profit. Operators sometimes read them as five separate disciplines to run — five skill areas to build capability in, five domains to master. That read misses what the fundamentals actually are. The fundamentals are not five separate disciplines. They are five terrains where the natural law […]

The principle governs the operating domain of the restaurant. It does not claim jurisdiction outside that domain. Every natural law has a boundary condition, and naming the boundary is what separates a law from a universal metaphysical assertion. Newton’s laws hold at non-relativistic speeds. They do not claim jurisdiction over subatomic physics or over the […]

The principle assumes there is an operator. Someone whose engineered intent or absence of intent produces the outcomes. In a single-owner-operator restaurant, that is clean. One person makes the calls, holds the accountability, and either designs or defaults on the dimensions of the operation. Most restaurants are not single-owner-operator. Most have multiple decision-makers: owners and […]

The principle covers two categories of outcomes: direct and emergent. Both trace to design or default, but through different mechanisms, and understanding the difference is what allows the operator to design at the right layer for the right kind of outcome. Direct outcomes are the immediate result of specific operator choices. The hire made this […]

The Summers Principle is not a slogan. It is a law with a falsifiable prediction attached. That prediction is what separates the principle from a rhetorical device or a philosophical stance. Naming the prediction directly is necessary — otherwise a sophisticated reader will conclude that the principle is unfalsifiable, and unfalsifiable claims are not laws. […]

The principle operates at every abstraction layer the operator designs at. Design against a specific outcome covers that specific outcome. Design against a category of outcomes covers the whole category. Design against uncertainty itself covers whatever unknowns arrive. The principle scales with the depth of the operator’s design work. This is the answer to a […]

A common objection to the principle: I know operators who defaulted on almost everything and got lucky. They ran a hot concept, hit a market wave, made money, cashed out. And I know operators who designed carefully and got killed — the neighborhood shifted, the pandemic hit, the anchor tenant closed, they lost the lease. […]

The principle names two operating modes: design and default. In practice, no operator runs pure design on every dimension of the operation at every moment of every shift. The operator is designing intensely on some dimensions right now, defaulting on others, designing lightly on still others. The reality is mixed. This can produce confusion about […]

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

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

Default is the absence of engineered intent. That is the definition. But absence is the wrong word to start with, because it makes default sound like nothing — like a gap, a vacuum, a place where the operator simply did not act. Default is not nothing. Default is a specific mode of outcome production, and […]

Design is engineered intent. That is the definition. But engineered intent is a phrase most operators have never had to sit with directly, and the definition needs unpacking to become operating vocabulary. Design has three components. All three have to be present for design to be running. If any one is missing, design has collapsed […]

Operators want an exception. The market turned. The lease renewed hot. A key cast member quit. A review landed wrong. The economy shifted. The health department showed up. The weather closed the block. Every operator has a list of events they file under “things outside my control.” The principle does not deny that these events […]