Ch37 Discussion

Discussion Guide

Prompt 1 — "Write down how you do it." Run the grilled-cheese or Hearth-Chicken exercise first, then ask: What did you leave out, and why did you leave it out? Which of the omissions would a guest actually notice?

Listen for: students discovering that the things they omitted are the things they consider obvious — which is precisely the category the Starbucks case says will disappear silently. Strong answers separate "I left it out because it doesn't matter" from "I left it out because I never noticed I was doing it." Push anyone who says "you can't write down craft" to identify one specific element that genuinely cannot be specified, and then ask how they would audit that thing instead. Watch for the class arriving at the specification/procedure distinction on its own; if they do, name it and move on rather than lecturing it.

Prompt 2 — "Who audits the owners?" Chapter 34 left this open. In a two-partner business, what would you actually change on Monday — and what would it cost you, personally, to be the partner who proposes it?

Listen for: the social cost, not just the mechanics. The four mechanisms in §37.4 are cheap and obvious; the reason they are so rarely in place is that proposing them to your business partner sounds like an accusation. Strong answers notice that the framing matters enormously — a delegation-of-authority table that includes the owners is easier to propose than a rule aimed at the owners — and that doing it before there is any reason for suspicion is the only time it is easy. Push back on anyone who says "we trust each other" by asking what happens when there is an investor, a buyer, or a divorce.

Prompt 3 — Growth: the trade in Figure 37.4. Group margin at ten units (9.5%) is lower than at one (12.0%), and far below Bellwether's owner-run 16.8%. So why would anyone do it? And what would have to be true for you personally to make that trade?

Listen for: students moving from percentages to dollars — \$1,465,000 versus \$186,000 — which is the correct reframe. Then push harder: the second thing you buy is a business that produces money while you are asleep, and separation from your own labor. Strong answers name what is given up as well: the chef stops cooking, the operator stops running rooms, and both spend materially more time in a car. Make room for the student who says "I'd stay at one," and validate it — §37.8 says explicitly that one excellent restaurant run well for twenty years is a complete and honorable career. Watch for the class treating growth as the default and stasis as failure; name that assumption out loud when it appears.

Prompt 4 — The comp that is all price. A group reports +4.0% comps built on +6.0% price and −2.5% traffic. The owners are pleased. What do you say to them, and what do you say when they answer that the price increase was necessary because costs went up?

Listen for: the recognition that both things are true — the increase may well have been necessary and it is borrowing from next year. Strong answers separate the decision from the reporting: the problem is not that they raised prices, it is that the consolidated comp line lets them not notice the traffic loss. Push for what they would do instead of a second across-the-board increase: targeted increases on low-elasticity items, mix work, a look at whether the loss is concentrated in a daypart or a unit. Someone will eventually ask whether traffic loss is always bad — good question; the honest answer is no (you can shed unprofitable traffic deliberately), but only if you can show you meant to.

Prompt 5 — Standardization versus the product. Every efficiency decision in the 2007 Starbucks memo is a decision Chapter 37 recommends. So is the chapter wrong, or was the company?

Listen for: students resisting the urge to pick a side. The productive answer holds both: variance reduction is mandatory above one unit, and it can remove the thing being sold, and no formula distinguishes them in advance. Strong students land on the asymmetry — you can measure the efficiency gain immediately and you cannot measure what disappeared until much later, so the decision is systematically biased toward the change. Push them to design a counterweight: what question would you require on every efficiency proposal? ("What disappears if we do this, and how would we know?") Then ask whether their counterweight would have caught the espresso machines. Usually it would not, and that is worth sitting with.

Prompt 6 — The bench, and where you send your best people. §37.8 says you should send your most experienced people to the new building and hire strangers into the original one. Every instinct says the opposite. Whose instinct is right?

Listen for: the logic — the original unit has systems, a reputation, and trainers, and is therefore the easy one to hire into; the new unit has none of those and is where the culture has to be installed by human beings. Strong answers connect this back to Chapter 35's "no management bench" and realize the bench is not an HR nicety but the culture strategy itself. Push on the risk: what happens to the original if you are wrong? Then ask the harder version — if you are not willing to send your best people, what does that tell you about whether your systems are actually written down? That question usually ends the session in the right place.

Optional prompt 7 — The log that was filled in from memory (Exercise 37.35). A good manager falsified two weeks of cooling logs because they were afraid of the audit result. What do you change?

Listen for: students who fix the manager and leave the system intact. The finding is that a measurement with a consequence and no safe route to report a failure will eventually produce a false record from someone who is not a bad person. Strong answers arrive at the structural fixes — a documented failure correctly handled should improve an audit result, not damage it — and connect it to the sick-employee paid-leave change in Case Study 1, which is the same insight from the opposite direction.