The Morgan Project · A walkthrough for the team

SEND
CHAPTER ONE.

We edited 38 chapters before the client heard one. Then his notes reached back to the very beginning. This page is about why that keeps happening to us, and the one habit that ends it.

▼ SCROLL
01 · The receipts

This is us, two weeks ago. In our own words.

Nobody slacked. Elijah edited fast, Jacob QC'd carefully, the spreadsheet was immaculate. The system around that effort is what failed.

AUG 15
🎧 The batch begins
Elijah"Today I completed chapters 12–20. They are checked off on the spreadsheet and have been uploaded."
AUG 15 · LATE THAT NIGHT
⚠️ The warning we texted and then ignored
Greg"Jacob can you approve these tomorrow before Elijah does more so we can send to Morgan and make sure we're on the right track"

The loop was named that same night. Nothing went out.

AUG 16
📋 QC in bulk — 17 chapters in one text
Jacob"Just wrapped QC, here are my notes… Chapter 3: might have overdone the 1:54 edit… Chapter 10: I think he says 'this boat' instead of 'this book'…"

Good ears. But it's our ear checking our own work. Morgan, the one ear that decides, still hadn't heard a single file.

AUG 19
💥 Morgan's "big text"
Jacob"He said he was finding things from the very beginning. Are you 100% sure Claude cross referenced correctly??"
Elijah"Per Morgan's big text, here's an updated version on my end for congruency with our docs"

Every chapter edited before that text carried assumptions Morgan never signed off on.

AUG 21
🔁 The rework round
Elijah"I have uploaded the new chapters 21–29. Plus all four chapters Jacob flagged… they have 'V2' at the end. Ex: Chapter 4 Punch Edit V2 … In terms of the Morgan deep dive spiral, I will use my judgment…"

"V2" is the sound of wasted work. "Deep dive spiral" is what a client does when he's lost confidence in the process.

AUG 29
🚨 Today. Still batching.
Greg"Are we sending to Morgan as we complete the QA?"
Jacob"No but I'll start next week now that Elijah is about half way done"

Ten days after Morgan's spiral, we are holding finished chapters again, waiting to be "half way done" before he hears anything.

38
Chapters edited
1
Client check-in — and it was a spiral
V2
The suffix on our wasted work
02 · The concept has a name

Shorten the feedback loop. Shrink the batch.

Gene Kim calls it the Second Way. Toyota built its production system on it. It applies to punch edits exactly like it applies to code.

⏱ The Second Way — amplify feedback

From The DevOps Handbook and The Phoenix Project: the teams that win are the ones with the shortest path from "we did a thing" to "the customer reacted to it." Fast feedback lets you fix quality at the source. Slow feedback lets defects multiply quietly.

Gene Kim, Jez Humble, Patrick Debois, John Willis

✉️ The envelope game — small batches win

From The Lean Startup (via Lean Thinking): stuffing 100 envelopes one-at-a-time beats fold-all-then-stuff-all-then-seal-all. Because if the letters don't fit the envelopes, one-at-a-time finds out on envelope #1. Batch finds out after folding all 100.

Eric Ries · Womack & Jones — "single-piece flow"

📈 The data — elite teams ship constantly

Accelerate measured thousands of teams. The elite ones deliver in hours, not weeks, and they have fewer failures too. Short loops produce speed and quality at the same time.

Forsgren, Humble, Kim — DORA research

🪢 The Toyota andon cord

Any worker who spots a problem pulls a cord and the line stops immediately, because a defect that travels down the line gets built into everything after it. Morgan's day-one preferences were a defect traveling down our line for two weeks.

Toyota Production System
"Our QC tells us we did it right.
Only Morgan can tell us it is right."
THE WHOLE LESSON, ONE LINE
03 · Watch it happen

38 chapters, two ways.

Same book. Same editor. Same QC. The only difference is when Morgan hears chapter one.

The batch way
DAY 0
Edit everything → QC everything → send when "half way done."
Press play.
Chapter one first
DAY 0
Edit ch. 1 → Morgan hears it day 2 → calibrate → then flow.
Press play.
Edited, unverified Suspect — re-checked against Morgan's notes Done to Morgan's actual standard
04 · The math

A wrong assumption costs whatever you built on top of it.

Morgan wanting tighter breath edits costs nothing. Guessing at his taste for two weeks is what costs a V2 round.

×38
Caught after the batch, 38 chapters are exposed — every one re-checked, some re-cut. That's the V2 round.
×1
Caught on chapter one, it costs one chapter, and every chapter after it is edited to the real standard.

Every day of finished-but-unsent work is a bet that we guessed the client's taste perfectly. The longer we wait, the bigger the stake. The odds never improve.

05 · The protocol

How we run every client project from now on.

Four rules. They cost us minutes and save us weeks.

RULE 1

The first finished unit goes to the client. Same day.

Chapter one of the audiobook. The first mixed song. The first cut of the video. Send it with one line: "Before we do the rest — is this the standard you want?" Clients love this question. It tells them we care about their taste.

RULE 2

Nothing scales until the sample comes back approved.

Keep working while you wait, but on breadth, not depth. Prep, organize, rough passes. Don't polish 37 more chapters against a standard nobody confirmed.

RULE 3

Send as you finish. Never hold for "half way done."

Finished chapters flow to the client in small drops — batches of 3–5, not 19. Small drops get small notes back. Big drops get deep dive spirals.

RULE 4

Three days without client feedback = stop and send.

If it's been three days since the client last reacted to real work, that's the alarm. Stop and send something. Silence is where the V2 rounds grow.

The one-line version
The client hears chapter one
before we touch chapter two.
Tape it to the console. It applies to every project with a client on the other end.