Case Study 23.1: Twenty-Six Combinations

📜 From the Field

A Tier 3 illustrative composite. The couple, the families, and the photographer are constructed; the timings reproduce from §23.4's arithmetic. The pattern — a family list that was never totalled — is the most common single failure in wedding photography, and it costs a cocktail hour every time.

The situation

Saoirse Mullane and Deshaun Carter. 180 guests. A hotel with a walled garden, late August.

Ceremony 2:30. Cocktail hour 3:15–4:45. Dinner 5:00.

Their photographer, Priya, is very good and has been booked for nine hours. She asked for the family list at −8 weeks, as she always does.

It arrived at −9 days.

The list

Twenty-six combinations, and it was built the way every family list is built: by adding.

Nobody ever wrote them on one page until Priya did, at −9 days, and when she did she sent one line back:

"This is about eighty minutes. Cocktail hour is ninety. Can we talk?"

The ninety minutes

Here is what those ninety minutes were already carrying.

💰 Run the Numbers: what cocktail hour was supposed to contain

	Minutes
26 family combinations at 3 min	78
Wedding party photographs	12
Portrait session	30
The couple attending their own cocktail hour	20
Total required	140
Available	90
Over by	50 minutes

And 180 guests were at that cocktail hour, of whom the couple would have seen none.

The list was not unreasonable. It was uncounted — which is a different thing and it is the finding.

What Priya proposed at −9 days

Not a cut. A structure, and a number.

📋 What she sent

"Here is what twenty-six looks like on the day, and I want you to see it before you decide anything.

Each one takes about three minutes and almost all of that is finding people, not taking the picture. Somebody is at the bar, somebody is in the loo, somebody has gone to the car. So twenty-six is about eighty minutes.

Cocktail hour is ninety. Which means you'd get about ten minutes at your own drinks reception and I wouldn't have a portrait session at all.

Three options.

One: cut to twelve. Twenty-two minutes, you get an hour at your reception, and I get a proper thirty minutes with you two.

Two: do half of them before the ceremony, which needs a first look and an earlier morning. Whichever family is on site early.

Three: keep twenty-six and accept that cocktail hour is photographs. Which is a legitimate choice and some couples make it — but I'd rather you made it than discovered it.

And one question, whichever you choose. Is there anybody you'd want a photograph of who isn't in a combination?"

What happened

They took option one and cut to fourteen.

Which was too many by two and took thirty-eight minutes rather than twenty-two, because two of the fourteen involved Deshaun's father's side, who were on the far side of the garden and had not been told.

But the day worked. The couple got fifty minutes at their reception, Priya got twenty-five minutes of portraits, and the family photographs happened.

And the great-aunt from Galway is in three of them, because the question at the end of Priya's note produced a list of four people that had never existed.

The three findings

🔍 Why Does This Work? The list was not too long. It was never totalled.

Twenty-six combinations is a completely reasonable set of relationships. Nine from one mother, seven from another, six from the couple, and four added late — every single one is a real family connection and none of them is frivolous.

The failure is that no single person ever saw all twenty-six at once, next to a duration.

This is the same mechanism as Chapter 16's eleven design decisions and Chapter 20's fifty-four-minute ceremony: items added one at a time, each compared against nothing. And the same fix: a running total, held by somebody, from the first addition.

Which makes this the third instance in the book and the pattern is now general:

Anything a family adds to incrementally needs a ledger from the first item, or it will be discovered at −9 days by a vendor.

Second finding: the photographer caught it, and that is not a compliment to the planner.

Priya asked at −8 weeks, chased, and totalled the list herself when it arrived. She did the planner's job, and she did it at −9 days, which is nine days before the wedding and about seven months after the useful moment.

The list should have been capped in month six, when there were nine items on it and adding a tenth was a conversation rather than a crisis.

Third finding: the fourteen took thirty-eight minutes rather than twenty-two, and the reason was §23.4's third fix, which nobody did: nobody told Deshaun's father's side to stay near the garden door.

One line in the logistics email (Chapter 19) and one sentence at the rehearsal. Sixteen minutes.

Discussion Questions

1. Priya sent the total, the arithmetic, and three options — including "keep all twenty-six." Why is that third option important?

2. The list arrived at −9 days despite being asked for at −8 weeks. Why do family lists arrive late, and what would actually fix it?

3. Fourteen combinations took thirty-eight minutes rather than the predicted twenty-two. Was the estimate wrong or was the execution?

4. Priya did the planner's job at −9 days. Is that a failure of the planner, or a photographer being good?

5. The question at the end — "is there anybody you'd want a photograph of who isn't in a combination?" — produced four names. What is it actually doing?

Connections

• Chapter 16 CS1, Chapter 20 CS1 — the same mechanism: items added one at a time, each compared against nothing. Three instances, and the pattern is now general
• Chapter 19 — the logistics email, where two sentences would have saved sixteen minutes
• Chapter 4 §4.7 — two costed options, neither favoured; Priya's three, and how to tell a genuine option from a fake one
• Chapter 11, Chapter 14 — the same arithmetic: the work is fast and the assembling is slow
• Chapter 23 §23.4 — the cap, the wrangler, and the sentence about people who are not in a combination
• Chapter 26 — the month-six question to every vendor: what do you need, when, and what happens if it is late