Case Study 22.1: The Best Band Anyone Had Heard

📜 From the Field

A Tier 3 illustrative composite. The couple, the band, and the venue are constructed; the floor counts are modelled from §22.7's mechanisms. The pattern — an excellent vendor delivering an unsuccessful evening — is the chapter's whole argument, and it is the version planners find hardest to accept.

The situation

Nkechi Duru and Owen Halliwell. 175 guests. A converted maltings, late September. Budget $84,000.

The band cost $7,400 and they are superb. Seven pieces, a genuinely excellent singer, a horn section, and a repertoire that runs from Motown to the last three years. Two guests, independently, said afterward that they were the best band they had ever heard at a wedding.

The dance floor peaked at thirty-one people and averaged nineteen.

The evening, counted

The planner's assistant, who had been asked to do it, counted the floor every five minutes.

💰 Run the Numbers: the floor, 9:40 to 12:30

Time On the floor What was happening
9:40 — Cake cutting
9:52 — First dance announced
9:55 2 First dance
9:59 34 Song ends · wedding party join for the last chorus · applause
10:03 9 Couple leave the floor for photographs
10:08 12 Band into set 1 proper
10:20 21
10:35 28
10:48 31 — the peak
11:00 6 Band break 1
11:20 4 Playlist through the PA, quiet, nobody running it
11:25 11 Band return
11:40 24
11:55 27
12:10 5 Band break 2
12:30 9 Band return · last song at 12:45

Average across 170 minutes: 19. Peak: 31, at 10:48.

Of 175 guests, 145 of whom were adults.

The five causes, and the band is not one of them

1. The couple left the floor at 10:03.

Thirty-four people, then nine, in four minutes. The photographer had asked for "a few minutes while the light's good in the courtyard" and the couple went, because nobody had told them not to.

They were gone eleven minutes. The floor never got back above 31.

2. Nobody covered the breaks.

Forty minutes across the evening, and the "playlist through the band's PA" existed but nobody was running it. The bandleader started it at 11:00, at the volume the band had left the desk at, which was too quiet for a room that had been at a band's volume for fifty minutes.

The floor went from 28 to 6 in twelve minutes, twice.

3. There was nowhere to put a drink.

The maltings' dance floor was in a bay with the bar 40 feet away and no surface of any kind between them. A guest with a glass had to choose between drinking and dancing.

Cost of the fix: four cocktail tables, $46.

4. The floor opened after the first dance, not during it.

Song ends, applause, wedding party join for the last thirty seconds, applause again — and then a gap while the bandleader talked, and then set 1 proper at 10:08.

Five minutes of nothing, at the exact moment the room had permission and did not use it.

5. The peak was at 10:48 and there were another 117 minutes to go.

§22.4's rule inverted. The band's best material was in set 1 — because a bandleader with no brief front-loads, which is the correct instinct at a gig and the wrong one at a wedding.

By set 3 they were playing the same quality of music to a room that had already peaked and been interrupted twice.

What the couple said

At the debrief, six weeks later. Nkechi first:

"The band were incredible. I genuinely don't know what happened."

And then Owen, who had been thinking about it:

"I remember standing at the edge at about half eleven and thinking — is this it? And then feeling terrible, because they were brilliant and everyone said so."

Both are correct. The band were excellent and the evening was not, and the couple had no vocabulary for how both could be true.

🔍 Why Does This Work? The band's quality and the evening's failure are almost unrelated, and that is genuinely counter-intuitive.

A wedding dance floor is not an audience. An audience assembles because it came to listen, sits down, and stays. A wedding floor has to be assembled, from people who are eating, talking, holding drinks, and sitting with relatives they see twice a year — and it disassembles the moment any of those becomes more available.

The band's job is the last thirty per cent. The first seventy is permission, timing, furniture, and continuity — all of which are the planner's, and none of which appear on a band's invoice.

Which is why the $7,400 is not the finding.** The finding is that **$46 of cocktail tables, one run-sheet line about photographs, and one person running a playlist during breaks would have roughly doubled the average floor — and that all three were free or nearly free and none of them was anybody's job.

What it should have looked like

🕐 The same evening, restructured

Owner
9:40 Cake, with coffee
9:45 Entrance and first dance, no gap MC
9:47 ★ Floor opened during the song — party at the second chorus, then everybody MC
9:49 Straight into an anchor track. No talking Bandleader
9:49–10:05 ★ The couple stay on the floor. Photographs are not now Run sheet
9:50 Four cocktail tables at the floor edge Bar lead
10:20 Photographs — with the couple's agreement, at a moment the floor can survive Photographer
11:05–11:25 Break 1. Playlist run by a named person, at band volume Named
11:50 ★ The peak — two-thirds through Bandleader, briefed
12:15–12:35 Break 2 Named
12:45 Last song, announced MC

Everything in that table is free except $46.

Discussion Questions

1. Two guests said it was the best band they had ever heard at a wedding. Reconcile that with an average floor of nineteen.

Discussion **Both are straightforwardly true, and the reconciliation is that they are measuring different things.** **The guests were evaluating the band as performers** — musicianship, the singer, the arrangements, the sound. On that measure the band were excellent, and the two guests who said so were probably the two who were listening rather than dancing. **The floor count measures something else entirely: whether a room of a hundred and forty-five adults was converted into a party.** That is a function of permission, timing, continuity, and furniture, and **the band contribute perhaps thirty per cent of it.** **The uncomfortable implication for a planner:** the vendor most likely to be praised is not the vendor most responsible for the outcome. **A band gets credit for the evening because they are the visible thing making it happen** — and a planner who accepts that framing will keep booking better bands to fix problems that better bands do not fix. **And the corollary, which is the useful half:** when an evening works, the band will get the credit for that too. **Chapter 1's product is calm and this chapter's is a full floor, and neither has your name on it.**

2. The photographer asked for a few minutes at 10:03 and the couple went. Who should have prevented it, and how?

Discussion **The planner, in month six, on a run sheet — not on the night.** **Nobody on the night did anything unreasonable.** The photographer saw good light and asked, which is their job. The couple said yes, because a couple asked for four minutes by a vendor at their own wedding always says yes. **And the planner, if they had been standing right there, would have had to overrule two of their own clients in front of a photographer** — which is a bad position and an unnecessary one. **The fix is a line agreed months earlier and known to everyone:** > **"No portraits between the first dance and 10:20. The couple stay on the floor."** **Three things that line does.** It is a decision made when nobody is under pressure. It is **known to the photographer in advance**, so the request never happens. And it gives the couple something to point at — *"we've got a thing about that, sorry"* — which is much easier than declining. **And the deeper point, which Chapter 23 owns:** the photographer's needs and the dance floor's needs collide at exactly one moment every wedding, **and the collision is entirely predictable.** It is scheduled in month six or it is negotiated at 10:03 by tired people. **Cost of the fix: one line. Cost of not having it: twenty-five people, for the rest of the night.**

3. The break coverage existed and nobody ran it. Design the mechanism that makes this impossible.

Discussion **A name, a volume, and a start time — all three, in writing, in the run sheet.** **"A playlist through the band's PA" is not a plan.** It is an object. The plan is: | | | |---|---| | **Who** | A named human. **And it cannot be the band**, who are on a break, or the planner, who is doing eleven other things at 11:00 | | **What volume** | **The same as the band's.** This is the failure in the case: the bandleader started it at desk level and the room heard the evening stop | | **When it starts** | **Before the band leaves the stage**, not after. A four-second gap is enough to empty a floor | | **What is on it** | Agreed with the band, so the transition is not jarring — **and it is the couple's must-play list, which is what it is for** | **Who to name, in order of preference:** a hired DJ for the evening (which also solves the MC problem and costs a tenth of the band's fee) · the venue's AV person, if there is one · **the band's own sound engineer**, who is there anyway and is not on a break. **The last one is the underused answer.** A seven-piece band frequently travels with an engineer, and **"can your engineer run the break playlist at set volume?"** is a question that costs nothing and is almost always yes. **And the general form:** **an object is not a plan.** Chapter 27's rule — an unassigned task is an unhappened task — applies to things as well as to actions. **A playlist, a spare bulb, a first-aid kit, and a fire extinguisher are all objects that do nothing until somebody's name is next to them.**

4. Four cocktail tables cost $46 and the case says they would have made a material difference. Is that plausible, or is it a tidy story?

Discussion **It is plausible and it is not measurable, and both halves of that deserve stating.** **The mechanism is real and it is not subtle.** A person holding a glass has one hand and a constraint. They will not dance with it, they will not put it on the floor, and they will not walk 40 feet to a bar and back. **Given no surface, the reliable behaviour is to stay near the bar** — which at this venue was 40 feet from the floor, which is Chapter 11's proximity problem arriving through a second door. **What is not established is the size of the effect.** The case claims cocktail tables plus the two free fixes would have "roughly doubled" the average floor. **That is a modelled claim, not a measurement**, and a reader should treat it as an argument about direction rather than magnitude. **Why it is worth doing anyway, and this is the actual reasoning:** it costs $46 against a $7,400 band, the mechanism is uncontroversial, and **the downside of being wrong is four tables nobody used.** It is the cheapest intervention in the chapter and it does not need to be proven to be worth making. **And the honest version of the case's claim:** the three free fixes together — the tables, the photograph line, and the break coverage — **address three of the four causes.** Any one of them alone would probably have been worth ten people; all three plus a correctly placed peak is where "roughly doubled" comes from. **It is a stacked estimate and every layer of it is soft.** **Exercise C.1 exists so that you can stop taking this book's word for it.**

5. The bandleader front-loaded, which is correct at a gig and wrong at a wedding. Whose failure is that?

Discussion **The planner's, and it is a briefing failure of exactly the kind Chapter 21 named: nobody told them a number that anything depended on.** **Front-loading is right at a gig.** An audience has come to hear you, they are there for ninety minutes, and you open strong because the first impression is the product. **A wedding is the opposite shape.** The room has to be assembled, it takes forty minutes, **and the peak belongs two-thirds through** — which for this evening was 11:50 and not 10:48. **A bandleader who has not been told this will do what they have always done**, and they will do it well. **What the brief needed, in one line:** *"You've got a hundred and seventy minutes. I'd like the peak at about ten to twelve. Set one is for building — please don't spend your best forty minutes before eleven."* **Every bandleader understands that sentence and almost none of them get it.** **And there is a second half that is worth adding:** *"the room is a hundred and seventy-five people, forty of whom are over sixty-five, and there are two families who don't know each other."* **A band given that will structure set 1 completely differently** — broader, more familiar, more of a floor-filler and less of a statement. **The general finding, which recurs across this book:** vendors deliver the default of their own craft unless told otherwise, **and the default is almost always correct for the context their craft came from and wrong for a wedding.**

Connections

  • Chapter 11 — the floor 40 feet from the bar, and proximity as an activation cost
  • Chapter 12 — vetting a band, and what a showreel cannot tell you
  • Chapter 21 — vendors deliver the default of their own craft unless told otherwise
  • Chapter 22 §22.4 — the peak at two-thirds, and what front-loading costs
  • Chapter 22 §22.7 — the four causes, three of which were live here
  • Chapter 23 — the photographer's four minutes, and the line that should have existed in month six
  • Chapter 26 — the run sheet, where a name, a volume, and a start time live
  • Chapter 30 — the debrief, and a couple with no vocabulary for how both things could be true