Case Study 17.1: The Peonies in October

📜 From the Field

A Tier 3 illustrative composite. The couple, the florist, and the figures are constructed. The pattern — a variety promised in the wrong season, sourced at any cost, and delivered badly — is one of the trade's most reliable failures, and it is a failure of the month-four conversation rather than of the flowers.

The situation

Dominique Farrell and Callum Ross. 130 guests. A restored maltings, mid-October. Budget $54,000. Floral: $3,900, ranked fourth.

Dominique has wanted peonies since she was nineteen. It is not a Pinterest preference; it is a specific, long-standing, entirely reasonable thing about her, tied to a garden she grew up beside. The board has fourteen peony images on it.

Their florist, Rina, is competent and has been in business six years. At the consultation in February she says the true thing:

"Peonies are late spring — May and June here. In October I'd be importing from the southern hemisphere, and they're expensive and the quality is a lottery."

Dominique says she understands. Nobody writes it down.

Rina's proposal, in March, lists "soft blooms in blush and cream" across the centrepieces and the bouquet. It does not name peony and it does not name anything else. The couple read "soft blooms" and see the board.

What happened

When
February Rina says peonies are out of season. Dominique says she understands
March Proposal issued: "soft blooms in blush and cream." No varieties named, no substitution clause, no stem counts
June Deposit paid
September, −5 weeks Dominique emails Rina a new image folder. Eleven of the fourteen are peonies. Subject line: "just so you have these!"
−12 days Rina, believing she has been asked, sources imported peonies. **$9.80 a stem** against the $3.20 garden roses she had costed
−12 days She does not call, because she believes she is delivering what was asked and because the sum still fits — she cuts the stem counts to absorb it
−10 days The peonies arrive. Roughly a third are bruised or blown; the boxes have been in transit eleven days
−9 days Rina calls the planner. The planner is at another wedding
The day The bouquet is peonies and it is beautiful. The centrepieces are 22 stems instead of the 38 she had planned, and half the peonies in them have opened fully overnight in a warm room

On the day, from four feet, the centrepieces look sparse. From a photograph, taken close, they look lovely.

Dominique's bouquet is the best floral object at the wedding, and she says so, twice, genuinely.

At the debrief, Callum:

"The tables looked a bit thin. Not bad — thin. And I don't think that's Rina's fault, because Dom did send her all those pictures in September."

What each person believed

🔍 Why Does This Work? Nobody in this case did anything unreasonable, and the failure is entirely in what was never written down.

Believed
Dominique She had accepted peonies were out of season in February, and was sending September images as inspiration for the feeling — the way she had sent images all year
Rina Eleven peony images at five weeks out, from a client who had wanted peonies all along, is a request. She was being responsive
The planner The proposal said "soft blooms in blush and cream," which is season-agnostic and safe. Nothing needed managing
Callum Dom sent the pictures, so this is on them

Four coherent readings of the same facts, and none of them was ever tested against another.

The document that would have tested them does not exist. A brief that said "blush and cream, soft-textured, 38 stems per table, no peony — agreed February, out of season" makes all four readings impossible.

The three failures

1. The February conversation was had and not recorded.

Rina said the right thing. Dominique heard it. And a spoken agreement in month two has a half-life of about six weeks — not because anyone is dishonest, but because a person who has wanted peonies since she was nineteen does not stop wanting them because a florist explained a growing season.

The fix is one line in the vision document: "Peony: discussed February, out of season for October, agreed not to pursue." Chapter 4's vetoes section, used for a positive want rather than a negative one.

2. The proposal named no varieties and no stem counts.

"Soft blooms in blush and cream" was written to be flexible and it functioned as ambiguity. It could be satisfied by garden roses at $3.20 or by imported peonies at $9.80, and it did not say which the price was built on.

§17.7 point 2: stem counts or dimensions, always. Had the proposal said "38 stems per table," the substitution to peony would have been visibly impossible at the price — and Rina would have had to call, which is all anyone needed.

3. There was no substitution clause, so there was no rule about volume.

Rina absorbed a 3× price increase by cutting stem count from 38 to 22. That is the single decision that produced the bad outcome, and §17.5's clause (c) forbids it explicitly:

(c) does not reduce the stem count or physical volume of the affected item

Under that clause Rina's options at −12 days would have been: source the peony and charge more, or not source it. Both require a phone call. Neither produces a thin table.

Discussion Questions

1. Dominique sent eleven peony images at five weeks out with the subject line "just so you have these!" Was that a request?

Discussion **It was not intended as one and it functioned as one, and both facts matter.** **What she meant:** she had been sending images all year. This was the same behaviour, and at five weeks out she was excited rather than instructing. *"Just so you have these"* is, read plainly, not an instruction. **What it was in context:** eleven images of a specific variety, from a client known to want that variety, arriving at exactly the moment a florist is finalising an order. **A responsive vendor reads that as a signal.** Rina was not stupid; she was attentive. **The general and genuinely useful finding: at some point in an engagement, inspiration becomes instruction, and nobody announces the transition.** Early images are about feeling. Late images arrive when decisions are being made, and vendors read them as direction because that is what most late communication is. **What to do about it, and it is a real practice:** at roughly −8 weeks, tell the couple, in one sentence — *"from here on, anything you send a vendor will be read as a request, so send it to me first."* **And tell the vendors the same thing from the other side:** *"any images from the couple after this point come through me for confirmation."* **That single exchange, twice, prevents this entire case.**

2. Rina cut the stem count to absorb a 3× price increase rather than calling. Why is that the wrong choice, and why did she make it?

Discussion **Why it is wrong:** she made a design decision — reducing volume by 42% — on commercial grounds, alone, without telling anyone, at a point when there was still time to do something else. **The couple bought an amount of flower, and received two-thirds of it, and were not told.** **Why she made it, and this deserves more sympathy than it usually gets:** **She thought she was solving a problem rather than creating one.** From her side: the client had asked for peonies (she believed), peonies cost more, the total still fit the agreed price, and she absorbed the difference in the way florists absorb differences every week. **Adjusting stem count against price is completely routine** — it is how a florist manages the market volatility of §17.2, forty-eight weeks a year, without anyone noticing or minding. **What made this instance different is scale.** Absorbing a 12% price move by trimming two stems a table is invisible and fine. Absorbing a 200% move by cutting sixteen stems a table is a different decision wearing the same clothes, **and there was no threshold anywhere that told her when it changed category.** **Which is exactly what the clause supplies.** Not a prohibition on judgment — a line past which judgment becomes a phone call. **A good vendor with an unbounded discretion will use it well 95% of the time and catastrophically 5% of the time**, and the clause is aimed only at the 5%.

3. The bouquet was the best floral object at the wedding and the tables were thin. Was that the right place for the money to land?

Discussion **By the surface hierarchy: yes, accidentally.** Chapter 16's arithmetic says the bouquet is arm's-length, held all day, and in every portrait; a centrepiece is across-a-table, intermittent, and competing with a person's face. **If $600 of peony had to go somewhere, the bouquet is where it does the most work.** **By the guest experience: no.** 130 guests looked at thin tables for two hours. One person carried a beautiful bouquet. **And that tension is the honest content of this question, because both are true and the book has argued both.** §17.8 says *spend on the bouquet.* §16.6 says *the table in front of a guest is the heaviest surface at the wedding.* They point different ways here. **The resolution is that this was not an allocation decision at all.** Nobody chose to move money from tables to bouquet. **The bouquet got the good flowers because it was made first and made carefully, and the tables got what was left** — which is what always happens when a shortfall is absorbed rather than announced. **The general finding: an unmanaged shortfall lands wherever the production sequence puts it, not where the priorities are.** That is true of floral, of catering, and of a run sheet at 4 p.m. **Deciding where a shortfall lands is a job, and if nobody does it, the shortfall decides.**

4. The planner was at another wedding when Rina called at −9 days. Is that a failure?

Discussion **The unavailability is not a failure. The absence of a fallback is.** A full-service planner works most Saturdays in season (Chapter 1's Saturday problem) and cannot be reachable on all of them. **That is a structural fact about the business, not a lapse.** **What is a failure:** 1. **There was no stated escalation path.** Rina had one number. When it did not answer, she did nothing further, which is a completely rational response to a vendor's position — **she had already delivered what she believed was asked.** 2. **There was no −14-day check-in.** A single scheduled call to the florist at two weeks out — *"anything moved? anything you're worried about?"* — catches this on the day the peonies were ordered rather than four days after they arrived. 3. **The planner's own week was not visible.** Rina did not know she was calling on a wedding day. **The practices that fix it:** - **A shared calendar of your own event days**, sent to every vendor at −6 weeks. Costs nothing. - **A named second contact** for every engagement — an associate, a colleague, or a documented voicemail protocol with a response time. - **The −14-day vendor sweep** as a standing item, not a good intention. Chapter 26 puts it in the production book. **And the broader point, which Chapter 1 raised and this case demonstrates:** a solo planner's capacity constraint is not just how many weddings they can plan. **It is how many weddings they can be interruptible for**, and those are not the same number.

5. Callum said "I don't think that's Rina's fault, because Dom did send her all those pictures." He is being generous. Is he right?

Discussion **He is right about intent and wrong about responsibility, and the distinction is worth being precise about because planners face it constantly.** **Rina acted in good faith throughout.** She said the true thing in February, she responded to what she reasonably read as a request, and she absorbed a cost increase rather than passing it on. **At no point did she try to do less than she was paid for.** **And she is still the party who reduced the volume by 42% without telling anyone.** Good faith does not transfer the consequence — a vendor who makes a large unilateral change and does not communicate it owns the outcome, whatever they believed. **But the more useful answer is that this is not primarily Rina's failure or Dominique's.** It is the planner's, on three counts, and none of them is dramatic: 1. **The February agreement was not written into the vision document.** 2. **The proposal was accepted without stem counts or a substitution clause** — §17.7's checklist, not run. 3. **There was no −14-day sweep and no fallback contact.** **All three are five-minute jobs done in month three or four**, and all three are invisible when they work. **That is the whole shape of this trade** — Chapter 1 called the planner's product calm, and calm is a set of small documents written months before anyone is anxious. **The generous version, which is also the accurate one:** everybody did their job and nobody did the joining-up, and the joining-up is what a planner is.

Connections

  • Chapter 1 — the Saturday problem, and interruptibility as a capacity constraint
  • Chapter 3 — the bad-news promise, which is the mechanism Rina needed and did not have
  • Chapter 4 — the vision document's vetoes, used here for a want rather than a prohibition
  • Chapter 12 — vetting, and the difference between a competent vendor and a well-managed one
  • Chapter 16 — the surface hierarchy, which says the bouquet was accidentally right
  • Chapter 17 §17.5 — clause (c), which forbids exactly what happened
  • Chapter 26 — the −14-day vendor sweep as a production-book item
  • Chapter 30 — the debrief, and Callum's generous sentence