🔬 Case Study 39.2: Twenty-Two Changes, Four Slots
📜 Tier 3 — Illustrative in its costings; the findings themselves are the book's own. Every change below was produced by a chapter of this book, sourced. The implementation estimates and the ranking are the author's.
The audit
Thirty-eight chapters. Every systems change this book has produced, in one table, for the first time.
| # | The change | The artefact | From |
|---|---|---|---|
| 1 | Write the unit and the assumption next to every number — "89 — seated dinner @ 12 sq ft" | Every document | Ch.28, 30, 32, 34 |
| 2 | A finding logged in an audit gets an owner and a due date, or it is not logged | Finding log | Ch.30 |
| 3 | The contingency tracker nets line variance weekly, not just explicit decisions | Budget template | Ch.30 |
| 4 | The budget sheet totals its lines and flags any unallocated remainder in red | Budget template | Ch.30 |
| 5 | Access questions move onto the RSVP template | RSVP template | Ch.29 |
| 6 | −6 months: send the access text, from a family member, not from me | Trigger set | Ch.29 |
| 7 | "1" on an RSVP generates an entry on the alone-list, and every entry gets a name at the rehearsal | Guest list template | Ch.29 |
| 8 | The ceremony hour gets its own planning sheet — seating, reserved rows, ushers' brief, water, and is anybody speaking who is not a vendor? | New artefact | Ch.29, 30 |
| 9 | Every permission carries two fields: granted to whom and extendable? | Vendor/permissions tracker | Ch.28 |
| 10 | The rain crew must contain at least two people who are not guests | Rain-plan template | Ch.28 |
| 11 | Any consumable revenue mechanic is scoped at guest count × 0.9 | Event-revenue template | Ch.32 |
| 12 | Every room the event touches goes in the space column — including the ones where nothing is built | Production schedule | Ch.34 |
| 13 | The first production meeting happens when the largest technical supplier is appointed, not at −6 weeks | Trigger set | Ch.34 |
| 14 | A per-venue file, kept forever | New artefact | Ch.34, 39 |
| 15 | Final numbers go to the caterer once, on the Thursday | Trigger set | Ch.30 |
| 16 | Anything announced is also printed | Standing rule | Ch.30 |
| 17 | Anything involving a named family member, resolved or not, is reported at the next scheduled conversation | Decision protocol | Ch.30 |
| 18 | The catering brief's service time is populated from the rehearsal-confirmed duration, and re-sent after the rehearsal as standard | Catering brief | Ch.30 quiz |
| 19 | A scope note and a guest-count band on every proposal | Proposal template | Ch.37 |
| 20 | An annual fee review, same month, whether or not you change it | Trigger set | Ch.37 |
| 21 | A tier kept because refusing was hard gets a cap and a review date | Service definitions | Ch.37 |
| 22 | An attribution column — how did you hear about me and who mentioned my name | Enquiry form | Ch.38 |
Twenty-two.
Every one correct. Every one cheap. Every one produced by a real finding on a real event.
The problem
🚪 A working planner will implement three or four of these in a season, and this table is the reason most systems advice fails.
The book has spent thirty-eight chapters producing changes and has never once totalled them.
Which is exactly the failure Chapter 30 diagnosed and Chapter 39 named: a list of correct findings, accumulating, producing the feeling of rigour.
Twenty-two entries with no owner and no dates is Rasheeda's ninety-one, in a textbook.
💰 Run the Numbers: implementation cost, honestly estimated
Estimated time Under 15 minutes — 4, 7, 15, 16, 20, 22 ~1.5 hrs total 15–45 minutes — 2, 6, 9, 10, 11, 13, 18, 19, 21 ~4.5 hrs 1–3 hours — 3, 5, 12, 17 ~7 hrs Ongoing or substantial — 1, 8, 14 ~6 hrs to start, then permanent TOTAL ~19 hours Nineteen hours. Which sounds entirely achievable and is exactly why this fails.
Nineteen hours of unbilled, unurgent, invisible work, competing against a season — and Chapter 36 established that the non-billable 40% is already fully committed to marketing, sales, bookkeeping, and chasing payment.
The nineteen hours is not the constraint. The absence of anything that forces them is.
The ranking
Using §39.11's criteria: prevents an expensive error · compounds · has caught you twice · under thirty minutes · closes an old finding.
⚡ The four for this season
Why it wins #1 — the unit next to the number Prevents four documented expensive errors (Ch.28's barn, Ch.30's contingency, Ch.32's wine pull, Ch.34's tape). Caught the book four times. Compounds across every document. And it costs four words per number #2 — the finding log's second column It is the mechanism by which the other twenty become possible. Without it, this list is a diary #14 — the venue file Highest compounding item available. By the fifth event at a venue it is worth more than any software, and it absorbs #9, #12's local knowledge, and most of Ch.34's corridor conversation #22 — the attribution column Twenty minutes, and without it Chapter 38's entire analysis is permanently unavailable. You cannot recover last year; you can start today Note what the ranking did not choose.
Not #8, the ceremony-hour planning sheet — which is arguably the single most consequential finding in Part VI, cost a real wedding a great deal, and is a substantial new artefact. Deferred to next January, with a date, because it is three hours and it will not survive being squeezed into February.
Not #5 and #6, the access questions — also important, also deferred, and the honest reason is that #22 and #5 both touch the enquiry-and-RSVP flow and doing them in the same sitting next year is cheaper than doing them separately now.
🚪 And #2 is the one that makes the argument work
#1, #14, and #22 are each valuable on their own.
#2 is valuable only because of what it does to the other twenty-one. It converts a list into a queue with dates, which means next January's audit starts from eighteen deferred items with a ranking rather than from a fresh feeling of being behind.
Which is the chapter's threshold concept, doing work on itself: the mechanism by which a finding becomes a change is itself one of the changes, and it must be chosen first or the others do not compound.
The deferred list
Eighteen items, with dates, because §39.11 says a change you decided not to make is a decision and a change you forgot is a finding that died.
⚡ The deferred eighteen
Date Items Next January's audit #8 ceremony-hour sheet · #5, #6 access questions and trigger · #3, #4 budget template · #12 space column Next January's fee review (Ch.37, same afternoon) #19 scope note · #20 annual review · #21 tier cap On next contact with each vendor category #9 permissions fields · #15 final-numbers rule · #18 catering brief First large build #13 production-meeting trigger First event with a consumable revenue mechanic #11 Next rain-plan draft #10 Standing, no work required — just do it #16 print what is announced · #17 the family-member disclosure rule Next guest list built #7 the alone-list Three things this list does that a pile of findings cannot.
It attaches most items to a trigger rather than a date — "on next contact with each vendor category" — which is §39.2a's whole argument applied to systems work itself.
It identifies two items (#16, #17) that require no implementation at all, only a decision — and those were sitting in the same undifferentiated pile as a three-hour artefact build.
And it groups by artefact, so that next January's ninety minutes opens the budget template once and makes two changes rather than opening it twice.
What it looks like a year later
💰 The second audit
Carried forward 18 Standing decisions, done immediately −2 (#16, #17) Closed by trigger during the season −4 (#9, #10, #11, #15) New findings from the season +9 On the table at the second audit 21 Chosen 4 The list did not shrink.
It went from twenty-two to twenty-one across a full year of doing this well.
🚪 And that is the honest ending of this chapter, because it would be easy to write a different one
A systems practice does not clear a backlog. It converts an accumulating, undifferentiated, guilt-producing pile into a ranked queue that produces four good changes a year, permanently.
Ten of the twenty-one now have dates and triggers. Six are standing decisions. Four are next year's.
And the four closed in year one are four classes of error that have stopped happening — which is the only measure that matters and is invisible in the total.
The number of open findings is not the score. The rate of closure is.
Discussion Questions
DQ1. The book produced twenty-two changes across thirty-eight chapters and never totalled them until now. Is that a flaw in the book?
Consider
**Yes, and it is the same flaw it has been diagnosing, which is why it is worth stating rather than quietly fixing.** **Each chapter's key-takeaways names its own changes and no chapter is responsible for the aggregate** — **which is precisely Rasheeda's ninety-one entries: correct, well-written, individually reasonable, and never counted.** **And the mechanism is the same one §39.1 describes: producing a well-articulated finding at the end of a chapter feels like resolution.** **What the book should arguably have done is carry a running total from about Chapter 20** — a visible counter, growing, uncomfortable. **It did not, and a reader who has followed thirty-eight chapters conscientiously has been accumulating obligations at roughly one every two chapters without ever seeing the pile.** **Which is a genuinely useful thing to have experienced rather than been told about.**DQ2. Nineteen hours is not much. So why does it not happen?
Consider
**Because none of the nineteen hours has a deadline, a client, or a consequence for being late.** **Chapter 36 established that only about 60% of a planner's hours are billable and the remaining 40% is already fully committed** — marketing, sales, bookkeeping, chasing payment, contracts, insurance. **Systems work does not compete with leisure; it competes with those.** **And it loses, every time, because those have external pressure and this does not.** **An unpaid invoice chases you. A template does not.** **Which is why §39.11's fix is not motivational.** **It is a scheduled ninety minutes, in the same month every year, in the diary, with the artefacts open** — **manufacturing the external obligation that the work does not naturally have.** **And the second half of the fix is Case Study 39.1's finding: three of four real changes happened because the artefact was already open.** **The audit's job is to make that condition occur on purpose.**DQ3. The ceremony-hour planning sheet — arguably Part VI's most consequential finding — was deferred. Defend that.
Consider
**On the criteria, and uncomfortably, it is right.** **#8 is a substantial new artefact: three hours to design properly, and it is the kind of document that is bad if rushed.** **A ceremony-hour sheet built in a hurried February is worse than none, because it will be trusted.** **And the ranking's criteria are about *implementation reliability*, not about importance.** **Under thirty minutes** and **compounds** both favour #1, #14, and #22 — **all of which will actually get done.** **The counter-argument is real and should be heard: Chapter 29 found that twenty-eight chapters of planning had never once addressed the ceremony hour, and a wedding's most emotionally significant sixty minutes had no seating plan, no water, and no plan for the woman who had to speak.** **Deferring that for a year has a cost.** **What makes the deferral defensible rather than negligent is that it has a date.** **It is on next January's list, grouped with the other artefact-building work, in a ninety-minute slot that exists.** **A deferral with a date is a plan. The same deferral without one is what produced the eighteen-month barn error.**DQ4. After a year of doing this well, the list went from twenty-two to twenty-one. Should that be discouraging?
Consider
**Only if you are measuring the wrong thing, and most people will.** **The intuition is that a good system clears a backlog.** **It does not, because a working practice generates findings continuously** — nine new ones in the year, which is what a planner running events and paying attention should produce. **A shrinking list would mean either that nothing was being noticed or that the criteria for logging had quietly tightened**, and both are worse. **What did change is everything except the total.** **Four classes of error stopped happening. Two standing decisions were made. Four items closed against triggers during the season without anybody thinking about them. And ten of the twenty-one now have dates.** **Which is the case study's stated conclusion and it generalises well beyond planning: the number of open findings is not the score; the rate of closure is.** **And there is a second, quieter measure: the list is now ranked, so the four that matter most are visible.** **Twenty-two undifferentiated obligations and twenty-one ranked ones are not the same object**, which is Rasheeda's *"decision, not a debt."*DQ5. Change #2 — the finding log's second column — is chosen because of what it does to the other twenty-one. What class of decision is that?
Consider
**A decision about the mechanism rather than about the outcome, and it is systematically under-chosen.** **#1, #14, and #22 all produce visible value.** **#2 produces none on its own** — it is a column in a spreadsheet, and at the end of the season nothing about any event will have been better because of it. **What it does is make the next four years' changes possible**, and that return arrives late and diffusely. **Which is why it needs to be argued for explicitly rather than competing on the same criteria as the others.** **§39.11's list — prevents an expensive error, compounds, caught you twice — does not obviously select it.** **And the general form appears throughout this book.** **Chapter 26's audit is an instrument that finds nothing on its own. Chapter 30's finding log produces no improvement by existing. Chapter 34's dependency map builds nothing.** **Every one is a mechanism, every one is invisible in the year it is built, and every one is what makes the visible work possible in the years after.** **A planner who only ever chooses changes with visible returns will build a practice that is slightly better every year and never becomes a system.**DQ6. What should a reader of this book actually do with the twenty-two?