Volume 19, Chapter 2
Timelines, Milestones, and Approvals
Definition
A large custom order proceeded all the way to final assembly before the customer ever saw a completed sample. That's when a misunderstood specification finally became obvious, far too late to correct without significant rework and a missed deadline.
A timeline breaks a project into dated stages. A milestone is a specific, named checkpoint with a real deliverable (a concrete thing produced), not just a date passing. An approval is a deliberate sign-off before the next stage begins, so a problem is caught at the checkpoint, not discovered at delivery.
Why does it matter exactly where in the process a mistake gets caught, if it gets caught either way? Because the cost of the same mistake grows enormously the later it's found, a misunderstanding caught before production costs a conversation; the same misunderstanding found at final assembly costs the whole order. Milestones exist to move that discovery earlier, while it's still cheap.
A project without milestones has exactly one checkpoint: the deadline itself, by which point it's too late to fix anything. Breaking a large order into a handful of named, dated, signed-off stages turns one big, high-stakes deadline into several smaller, manageable ones.
A Milestone Structure
| Milestone | Deliverable | Sign-Off |
|---|---|---|
| 1. Deposit Received | Funds in, project formally begins | Recorded per Volume 07, Chapter 1 |
| 2. Design/Measurements Approved | Customer confirms specification before production starts | Customer sign-off, in writing |
| 3. Production Check | Work-in-progress inspected against Volume 14's quality standard | Internal inspection |
| 4. Delivery | Completed work handed over, final balance settled | Customer confirms receipt |
A milestone without a real deliverable is just a date on a calendar. Each one needs something concrete to check, a signature, an inspection result, a payment received, not just "day 10 has arrived."
Why Approvals Matter Between Stages
Each milestone is a natural point to apply Volume 14's inspection logic at the project level: a design misunderstanding caught at Milestone 2 costs a conversation; the same misunderstanding discovered at Milestone 4 costs the entire order. Large or unusual commitments made along the way should also pass through Volume 11's approval ladder, the same as any other significant decision.
Example Story: The Approval Point That Was Missing
Here's the full version of the missing-approval story from the start of this chapter.
A large custom order proceeded all the way to final assembly before the customer saw a completed sample, at which point a misunderstood specification became obvious, far too late to correct without significant rework and a missed deadline.
Nothing about the production work had been wrong. The checkpoint had simply never existed. Adding a single milestone, customer sign-off on the design and measurements before full production began, caught the exact same kind of misunderstanding when it cost almost nothing to fix.
Across Industries
The specific checkpoint changes by trade, but its job is always the same: catch a misunderstanding before it becomes expensive.
| Business | A Milestone Specific to Them |
|---|---|
| Golden Crust Bakery | Tasting/sample approval before a large event order is finalized |
| Rapid Auto Works | Customer approval of a repair estimate before work begins on a large job |
| Precision Print & Press | Proof approval before a full print run starts |
Common Mistakes
By definition, too late to fix anything discovered there.
A date passing isn't the same as a checkpoint being verified.
This is the exact gap in the example story. The time "saved" early is often lost many times over in late-stage rework.
Quiz Yourself
Practice Exercise
Take your current largest active order or a recent large project. Break it into 3–5 milestones, each with a real deliverable and a named approver, using Chapter 1's project criteria to confirm it deserves this treatment.
Quick Summary
Quick Summary
- A timeline breaks a project into dated stages; a milestone is a real, checkable deliverable within it, not just a date.
- Approvals between stages catch problems while they're still cheap to fix, applying Volume 14's inspection logic at the project level.
- Volume 19 complete. Next, Volume 20, Chapter 1: The Business OS treats the whole business as a designed information system.