Case Study 1: Twenty-Six Names

Tier 3 — Illustrative. The Adeyemi–Novak wedding and all people in it are composites created for teaching. The conversation described is assembled from a pattern that recurs in nearly every over-budget engagement.

This is the case behind the chapter's opening. It is included in full because the cut conversation is the single most avoided conversation in this profession, and avoiding it is the reason it becomes a four-hour crisis instead of a twenty-minute one.


The Situation

Folake Adeyemi and Petr Novak. Budget $54,000. Modeled cost at current plan: **$62,300. Over by $8,300**.

Month nine. Eleven vendors booked. Invitations designed but not printed.

Guest list: 186 invited, of which:

Owner Names
Folake 62
Petr 47
Folake's parents (contributing $16,000) 54
Petr's mother (contributing $4,000) 23

The venue: an all-inclusive event space with a hard capacity of 200 and a step at 160 where a second service kitchen must be opened.


Why It Got Here

Three failures, all of them in the first four months, all of them the planner's.

1. The guest count conversation never happened in month two. The planner had built the budget from a stated count of "about 150" and never revisited it as the list grew. By month six it was 186 and nobody had said a number out loud.

2. There was no Owner column. The list was a single alphabetical spreadsheet. Nobody knew whose names were whose without reading each one.

3. There was no step map. When the budget first went over in month seven, the planner priced the fix at "about $180 a head" and told the couple they needed to cut 46 people. That number was wrong — badly wrong — and it frightened them so much that they stopped discussing it for two months.

⚠️ Common Pitfall: the frightening estimate

The month-seven "cut 46" was calculated as $8,300 ÷ $180. It was wrong in the direction that does the most damage.

It ignored the steps. Working downward from 186, the crossings were: the second kitchen at 160 ($1,900**), the fourth bartender at 165 (**$340), and tables every 10 at $155.

The real answer was 26 names, not 46. The planner's arithmetic asked this couple to cut twenty additional people from their wedding, and — because the number was so large — caused them to avoid the problem for two months, which cost them the option of a smaller ballroom and $1,400 of vendor deposits that could have been renegotiated in month seven.

A wrong estimate in this conversation is not a neutral error. Too high and the client freezes. Too low and you have to come back. Build the step map before you say a number.


The Conversation

Month nine, a Tuesday evening, at their kitchen table. The planner had spent three hours that afternoon building the step map she should have built in month two.

Opening: the number, the correct one

📋 The Planner's Script: the cut conversation

Do not open with sympathy. Open with the number and the fact that it is smaller than they think.

"I've got better news than the last time we talked about this. In month seven I told you we needed to cut about 46 people. That was my mistake — I did the arithmetic badly. The real number is 26."

Naming your own error first does three things: it explains why they were told something different, it converts you from the bearer of bad news into someone bringing relief, and it makes everything you say next more credible rather than less. A planner who quietly revises a number downward without acknowledging the earlier one leaves a client wondering which number to believe.

Then show the arithmetic:

"Here's why. It's not $180 a head evenly. When you come down from 186, three expensive things switch off. At 165 you drop a bartender. At 160 the venue closes the second kitchen, which is nineteen hundred dollars. And every ten people you lose is a table, a linen, and a centerpiece — a hundred and fifty-five each.

So: 186 down to 160 is 26 names. That saves $4,680 in food and drink, $1,900 on the kitchen, $340 on the bartender, and $465 on three tables. **$7,385.** We're $8,300 over, so we still need about nine hundred, and I've found that in the transport line — one shuttle run instead of two, because at 160 they fit."

Then stop. Let them absorb it before you talk about who.

The allocation, when they ask "who?":

"That's the part I can't decide and won't try to. But I can tell you how it splits fairly, and then it's yours.

You're at 186. Folake, 62 are yours. Petr, 47. Folake's parents put in 54, and Petr's mum 23. Proportionally, 26 names is: nine from Folake, seven from Petr, eight from your parents, and three from your mother, Petr.

That's one way. It's not the only way. If you'd rather weight it differently — because your parents are contributing more, or because Petr's family is smaller and every name matters more — that's completely legitimate. I just want it decided on a principle rather than by who gives in first."

The objection that always comes

Folake: "I can't ask my parents to cut eight. They're paying sixteen thousand dollars."

The planner:

"I know. Two thoughts, and then it's yours.

First — you don't have to ask them to cut eight. You could take those eight onto your own list, which would make yours seventeen. That's a real option and some couples do it. I want you to choose it deliberately rather than discover in three weeks that it happened by default.

Second — and this is the bit I'd actually suggest. Don't ask them to cut. Ask them how they'd like to spend forty-six. Same number, completely different conversation. Right now they have 54 names and no idea there's a limit. If you call and say 'we've got space for 46 from your side, they're yours, tell us who' — that's you giving them something, not taking something away. And they'll do it in a day."

They did that. Folake's mother came back within thirty-six hours with 45 names and an apology for having over-listed, which nobody had asked for.

🎤 From the Field: This inversion — "cut eight" into "here are forty-six, they're yours" — is one of the highest-value moves in this chapter and it costs nothing. The same arithmetic, framed as an allocation rather than a subtraction, changes both the emotional register and, reliably, the speed.

It works for exactly the reason Chapter 3's contributor role menu works: people receiving a bounded, ownable resource behave completely differently from people being asked to give something up, even when the resulting number is identical. Use it every time a parent's list must shrink.

The hard part

Folake's own nine, and Petr's seven, took two more evenings.

The planner was not in the room for that, and should not have been. What she did instead was send one document the following morning:

The list, filtered. Every name on their two lists, sorted into four buckets that the couple had defined in a fifteen-minute call:

  1. People we would notice were missing — 71 names
  2. People we'd like there — 24
  3. People we're inviting because of a situation — 9
  4. People we honestly cannot remember why we added — 5

The 16 names in buckets 3 and 4 nearly covered their share of the cut. It took two evenings rather than four because the sorting had already been done, dispassionately, in a phone call, before anyone had to look at a specific human being's name and decide.

This is the transferable technique. Do not ask a couple to cut names. Ask them to sort names — into categories they define, in a low-stakes conversation, before any cut is being made. The sorting is almost painless. The cutting, once sorted, is largely mechanical.


The Outcome

💰 Run the Numbers: the close

Move Names Saving
Folake's parents: 54 → 46 −8
Petr's mother: 23 → 20 −3
Folake: 62 → 53 −9
Petr: 47 → 41 −6
Total, 186 → 160 −26
Food, bar, place settings, cake, favors @ $180 | | $4,680
Second kitchen (step at 160) $1,900
Fourth bartender (step at 165) $340
Three tables with linen and centerpiece $465
Second shuttle run (no longer needed) $900
Total saved $8,285
Deficit $8,300
Remaining $15

Closed, essentially exactly, with 26 names.

And then the forecast. 160 invited, largely local, with Petr's family travelling from abroad:

Category Invited Rate Expected
Immediate family + wedding party 26 99% 25.7
Extended family, local (Adeyemi) 44 88% 38.7
Extended family, international (Novak) 18 45% 8.1
Close friends, local 32 90% 28.8
Close friends, long-haul 14 70% 9.8
Social friends and coworkers 16 74% 11.8
Parents' friends 10 82% 8.2
Total 160 ~82% 131

131 expected from 160 invited — which put them well under the 160 step and, in the event, produced a final guaranteed count of 134 and a wedding that came in $2,900 under budget.

Folake's mother, told about the surplus, asked whether they could add the eight names back. The answer was yes for four of them, because 138 was still comfortably under every threshold.


Post-Mortem

Root cause: the guest count was never treated as a variable. It was a number the planner inherited in month one and did not revisit while it grew by 36 names.

Contributing causes:

  1. No step map until month nine. Which produced a wrong estimate in month seven, which produced two months of avoidance.
  2. No Owner column. Which made the month-seven conversation impossible to have fairly, so it was not had.
  3. The month-seven number frightened them. A "cut 46" that should have been "cut 26" is not a rounding error; it is the difference between a hard conversation and an unbearable one.
  4. No attendance forecast until month nine. Had the 82% forecast existed in month three, the couple would have understood from the start that 186 invited meant roughly 153 attending — and the entire crisis would have been substantially smaller.

What went right:

  1. The planner led with her own error. It cost her nothing and bought the credibility of everything after it.
  2. The step map made the number small. Twenty-six is survivable. Forty-six was not.
  3. The parental ask was inverted"here are forty-six" rather than "cut eight" — and resolved in thirty-six hours.
  4. The couple sorted rather than cut. Four buckets, defined by them, on a phone call, before any name was under threat. Sixteen of the twenty-six came out of buckets three and four.
  5. She left the room for the personal part. The nine and the seven were not hers to be present for.

The transferable rules:

  1. Build the step map before you say a number. A wrong estimate in this conversation is not a neutral error.
  2. Lead with your own mistake if you made one. It converts you from bearer of bad news to bringer of relief.
  3. Invert the parental ask. "Cut eight" becomes "here are forty-six, they're yours."
  4. Sort before you cut. Ask for categories, not decisions.
  5. Run the forecast in month three, and show the client both numbers from the first budget onward.
  6. Leave the room.

Discussion Questions

  1. The planner's month-seven estimate was wrong by twenty names and caused two months of avoidance. She disclosed it in month nine. Should she have disclosed it the moment she discovered it, in month nine, or is there an argument for correcting it silently and moving on?

  2. The four-bucket sort is described as "almost painless." Is that plausible? What makes sorting into categories emotionally different from cutting, given that the outcome is the same?

  3. Folake was offered the option of absorbing her parents' eight names onto her own list. The planner presented this neutrally. Should she have? What would you have said?

  4. The wedding came in $2,900 under and four names were added back. Argue that this proves the cut was excessive. Then argue it does not. What would you have to know to settle it?

  5. Petr's international family forecast at 45%. If it had come in at 70%, the wedding would have gone over the 160 step. What should the planner have done to protect against that, and what would it have cost?


Mini-Project

Build the four-bucket sort as a client-facing tool.

Design the exact call script and the document you send afterward. Consider: who defines the buckets — you or the couple? How many buckets? What are the bucket names, and how much does the naming matter? What do you do about a name where the two partners sort differently?

Then test it: take a real list of thirty people you know — friends, colleagues, extended family — and sort them yourself into your buckets, as though you were inviting them to a wedding. Note how long it took, where you hesitated, and whether any bucket turned out to be useless.

The last question is the one that matters. Most people who do this exercise discover that one of their buckets never gets used and that they need one they did not anticipate.


References

Tier 3 — Illustrative. Folake Adeyemi, Petr Novak, their families, and all figures are composites created for teaching. The step values and attendance rates are illustrative of a mid-cost US market with an international guest contingent.

Related chapters: Step maps and marginal cost — Chapter 5 §5.2–§5.3. List architecture and allocation — Chapter 5 §5.4. Attendance forecasting — Chapter 5 §5.6. Contributor role menu and the bounded-resource principle — Chapter 3 CS1. Budget reallocation and the overage conversation — Chapter 7. Guaranteed counts — Chapter 14.