Chapter 2 — Teaching Notes

What this chapter is doing

Chapter 1 established the book's epistemic posture (check the number) and its central technical concept (prime cost). Chapter 2 has a harder job: it has to take the most romantic part of the restaurant business — the idea, the vision, the room in somebody's head — and convert it into an object that can be tested and found wrong, without killing the reason anybody wanted to do this in the first place.

That tension is the chapter. Teach it as a conversion, not as a debunking. Students who leave believing "concepts are silly and only numbers matter" have learned the wrong thing; the chapter's actual claim is that a concept is enormously powerful precisely because it constrains every number that follows, which is why it deserves to be specified rather than felt.

The single sentence to leave on the board: a concept is a claim about a market, and a claim that cannot be wrong cannot be tested.

Timing

  • A 75-minute session: §2.1 and the three-sentence test (15 min) → §2.2 with the occasion-mix calculation worked live (20 min) → §2.3, ending with the capture-rate arithmetic (25 min) → §2.4's competitive set and the supply calculation (15 min). Assign §2.5–§2.7 as reading.
  • Two sessions: split after §2.3. Session two opens with the competitive-set survey (ideally assigned as fieldwork between sessions — see the demonstration below), then §2.5's check build, then §2.6 and §2.7.
  • Self-paced: 5–7 hours including exercises. Exercises 2.20 and 2.25 are field exercises and should be assigned at least a week out.

Common misconceptions

1. "A concept is the cuisine and the vibe." Nearly universal on day one. The fastest correction is the Figure 2.1 chain: ask a student to name their concept, then ask what service style it implies, then what labor model, then what check, then how many covers a night — and let them watch the room realize that four answers were determined by the first one. Do not lecture this; make them derive it.

2. "Our target market is people who appreciate good food." The most common persona in every classroom. The correction is §2.2's alternative field. Ask: "Where does this person eat when they don't eat with you?" Students who cannot answer discover, in real time, that they have not described a customer. This single question does more work than the rest of the persona framework combined.

3. "7.7% of the trade area sounds easy." This is the chapter's best moment and its most reliable teaching failure. Students hear a small percentage and relax. The counter-move is to restate the same number as households: about one in three affluent households in the entire ten-minute drive time. Show both figures at once, on the same board, and do not explain the discomfort — let them find it. The lesson is that a capture rate can be stated in a way that flatters or a way that informs, and the founder chooses which one they look at.

4. "The competition is other restaurants." Students consistently build competitive sets of similar restaurants and omit the grocery store, delivery, and cooking at home. Assign Exercise 2.23 (which occasions map to which competitors) before discussing it — the discovery that there are four different lists is much stronger when they produce it themselves.

5. "Our differentiator is quality." Run it through the three-part test in front of them. Perceptible before ordering? Usually not. Copyable? Yes, by Tuesday. Priced? Never. Then ask what would actually have to be true, and steer toward the durable answers: capital equipment, physical room, location, trained team, cost structure, accumulated neighborhood relationship.

6. Confusing "the occasion is real" with "the position is defensible." This is Case Study 2's whole job, and it is the most sophisticated point in the chapter. Boston Market got the occasion right and lost anyway. Do not teach it as a story about bad management; teach it as sentence three of the three-sentence test failing four years after it was written.

The hardest point to teach

That a check average is an output, not a decision.

Students accept it in principle and then immediately revert. You will see it in their plan drafts: "our average check will be \$48." Ask where \$48 came from and you get a competitor's menu.

What works is the two-table sequence in §2.2's 🧮 Run the Numbers callout, worked live and slowly. Build the \$46 from the four occasions. Then change one input — the celebration segment from 30% to 20% — and let a student do the arithmetic on the board. The check falls \$1.60. Then multiply by 24,700 covers and let the \$39,520 sit there. Then ask the question that lands it:

"Which report would have shown you this?"

The answer is none of them. Covers were on plan, the menu did not change, the room looked identical. That is the moment students understand why Chapter 24 tracks party size and check by daypart, and why Chapter 4 needs an assumptions register.

A useful extension for a stronger class: ask which is easier to move, the mix or the prices. Most will say prices. The better answer is the mix — through reservation policy, table mix, marketing channel, and how the bar is programmed — and every one of those is a management decision rather than a guest-facing price increase.

A demonstration that works

The field survey, assigned between sessions.

Send students out in pairs to a real restaurant district with three tasks: (1) survey at least five establishments — format, approximate seats, dinner per-person average from the posted menu, dayparts, and the occasion each one owns; (2) count covers in one establishment at 6:30 and again at 8:00 on a weeknight; (3) draw the barrier map for the district.

Then, in class, build the composite price ladder and positioning map on the board from everyone's data. Three things reliably happen and all three are teachable:

  • Different pairs place the same restaurant differently, which surfaces that positioning is a claim about perception, not a fact about a business.
  • Somebody's cover count contradicts the room's apparent busyness, which is the first time most students experience the gap between "it felt packed" and a number.
  • The empty space on the map is argued about, which is exactly Case Study 1's closing lesson: is it empty because no delivery model exists to occupy it, or because the arithmetic does not close?

If fieldwork is impossible, the same exercise works with online menus and a mapping tool, at maybe 60% of the value. The cover count is the part that cannot be simulated, and it is the part they remember.

Shorter alternative (15 minutes): the pre-mortem. Have every student write the paragraph — "it is three years from now and this restaurant has closed" — for a concept the class has been discussing, independently, then read four aloud. The convergence is startling and the point makes itself.

Assessment notes

  • Exercises 2.9, 2.11, 2.16, 2.18, and 2.28 are the computational core. A student who can do those five can do the arithmetic in the rest of Part I.
  • Exercise 2.22 (find the flaw) is the best single diagnostic in the chapter. The arithmetic is correct, which is the trap; students who "check the math" and stop have missed it. Look for whether they compute sales per seat and whether they notice the check-versus-turns contradiction.
  • Exercise 2.30 rewards students who realize that revenue per daypart-day is the wrong question. The five-dinner-plus-two-brunch answer lands within \$360 of the target with seven daypart-days while the lunch route needs ten — the comparison, not the arithmetic, is the graded part.
  • Exercise 2.34 is designed to fail: no two of the four gap-closers reach \$139,240. Students who report that honestly, rather than fudging a pair into sufficiency, have understood the chapter. Reward it explicitly.
  • Exercise 2.31 (the gentrification question) is the best writing prompt here and works well as a graded short assignment. Grade on honesty rather than on the position taken. Answers that resolve the tension cleanly in either direction are weaker than answers that hold it.
  • Exercise 2.32 (write the Concept & Market Analysis) is the natural first milestone of a semester-long business-plan project.

Connections forward

Flag these so students build the map: the occasion mix → Chapters 22, 23, 24. The capture rate → Chapters 27 (cost per cover acquired) and 35 (cannibalization). The check build → Chapters 10, 11, 15, 16. The revenue identity → Chapters 4, 24, 32. The shape of the week → Chapters 19 and 24. The differentiation test → Chapters 3, 12, 38. Concept discipline under revenue pressure → Chapters 35 and 39. And the \$139,240 gap → Chapter 24, which students should be told explicitly is where it gets settled, so they stop trying to close it.