Case Study 39.1: Ninety-One Entries and Four Changes

📜 Tier 3 — Illustrative. Rasheeda Iyaloo, her practice, and every figure here are constructed. The pattern is extremely common; the numbers are the author's.

The log

Rasheeda Iyaloo kept a finding log for three years, exactly as this book recommends.

Written the night of the event, or the next morning. Factual. Specific. Genuinely good.

⚡ A sample, and it is representative

12 May	Cake table was in the photographer's light for the whole of the cutting. Nobody had checked the direction. This is a floor-plan question and I treat it as a décor one.
7 Jun	Two vendors both told me they'd been given the loading bay at 8. Neither knew about the other. I had told them both.
21 Jun	Second time this season a guest count moved more than 15 after the seating plan was drawn.
9 Aug	Ashcombe's back gate is locked at 6 and the caretaker leaves at 5:30. Found out at 6:10.
14 Sep	The mothers' corsages arrived and nobody knew who was supposed to pin them on. Third time.

Ninety-one entries in three years.

Four documents changed.

What she did with the other eighty-seven

Nothing, and she did not notice.

🎤 Rasheeda, when she counted

"I thought the log was the system. I wrote it every time, I never missed one, and I'd have told you it was the most disciplined thing I did."

"And it was disciplined. It just wasn't connected to anything."

"What actually happened is that writing a really good entry felt like dealing with it. The better I described the problem, the more finished it felt — and the ones I wrote best are the ones I did least about."

🚪 The mechanism, stated precisely

A finding log with one column is a diary.

It records that something happened and produces no obligation. And because the act of writing it is effortful and satisfying and happens at the end of a long day, it carries the emotional weight of a resolution.

Which is why §39.1's first mechanism is found and fixed being the same column — and why the fix is not "try harder," it is a second column that stays visibly empty.

What the entries were actually worth

💰 Run the Numbers: four of the eighty-seven, costed

The entry	Times it recurred	What it cost
Corsages — nobody assigned	3, then 5 more over two years	8 × ~10 min of confused people at a moment that matters. And once, a mother who was not wearing hers in the photographs
Two vendors, one loading bay	4 across three years	~90 min of delay each. One caused a rig to run into a crew meal — Chapter 34's penalty
Guest count moving after the seating plan	7	~4 hrs of rework each = 28 hrs, or roughly $1,900 at her required rate
Ashcombe's back gate	2	The second time was a $180 taxi for a vendor who could not get in

Four entries. Twenty-one recurrences. Somewhere between $3,000 and $4,500 of cost, plus the corsages.

And every one had been correctly identified, in writing, the first time it happened.

The four that did change something

Worth examining, because they are not the important-looking ones.

⚡ What distinguished them

The change	Why this one and not the others
Added a "who pins the corsages" line to the assignment sheet	Made in the same week, while she was already editing the sheet for another reason
Added the caterer's phone number to the emergency page	Took ninety seconds and the document was open
Started sending run sheets on the Wednesday	A vendor asked her to
Added a "power?" column to the vendor tracker	After a generator failure that frightened her

Three of the four happened because the artefact was already open.

One happened because somebody else asked.

None happened because it was on the log.

🚪 Which produces the finding, and it is more useful than the diagnosis

Changes get made when the artefact is open, or when somebody external creates an obligation.

So a system's job is to manufacture both: a scheduled moment at which the artefacts are open (§39.11's annual audit) and an external obligation (a due date, and a name in a column — even if the name is yours).

Note that the corsage entry was one of the four that got fixed, and it had already recurred three times before the change happened. It was not fixed because it recurred. It was fixed because she happened to be editing that document.

What she changed

⚡ Three things, in about an hour

1. A second column	Artefact · Owner · Due · Closed — added to the existing log
2. A ninety-minute audit, in January, in the diary	All artefacts open at once. §39.11
3. Retro-processing	She went through all ninety-one entries once, and assigned an artefact to each

Item 3 is the interesting one and it took four hours.

Entries	91
Could be assigned a specific artefact	58
Could not — observations, one-offs, things about people	33
Already fixed by circumstance	12
Genuinely still open and worth doing	46
Chosen for the first year	5

Forty-six worth doing and five chosen — which is §39.11's capacity problem, arriving as a real number.

And the forty-one deferred were written into a dated list, which she says is the part she was most reluctant about and now considers the most valuable.

🎤 Rasheeda, a year later

"The deferred list is the thing. Forty-one items I have consciously decided not to do this year."

"Before, I had ninety-one things I felt vaguely bad about."

"It's the same information. But one of them is a decision and the other one was a debt."

Discussion Questions

DQ1. Thirty-three of ninety-one entries could not be assigned an artefact. What were they, and does that mean the log was wasted?

DQ2. Three of the four changes happened because the artefact was already open. What does a system do with that?

DQ3. The guest-count entry recurred seven times and cost roughly $1,900. Why did seven recurrences not force a change?

DQ4. "One of them is a decision and the other one was a debt." Unpack that.

DQ5. Forty-six worth doing, five chosen. Is that a failure?