Work the most downstream pipeline stage first — Deliver before Polish, Polish before Review, Review before Draft — pull from bottlenecks, don't push WIP
Before every work session, consult your pipeline board and work on the most downstream stage that contains items (Deliver before Polish, Polish before Review, Review before Draft) to pull from bottlenecks rather than accumulating work-in-progress.
Why This Is a Rule
The natural instinct when starting a work session is to begin something new — draft a fresh article, start a new project, create a new document. New starts are exciting and feel productive. But each new start adds an item to the pipeline's upstream stages without moving anything toward completion. The pipeline fills with half-finished work, nothing ships, and the sense of progress is illusory.
The downstream-first rule reverses this instinct by prioritizing completion over initiation. Before starting anything new, check: is there an item in the Deliver stage? Ship it. In Polish? Polish it. In Review? Review it. Only if all downstream stages are empty should you Draft something new. This is the pull system from lean manufacturing applied to personal production: work is pulled from downstream stages rather than pushed from upstream.
The mechanism is Goldratt's Theory of Constraints (Optimize only the single slowest step — improvements to non-bottleneck steps are wasted effort regardless of their magnitude) at the pipeline level: the constraint is always the most downstream stage with items in it, because items downstream are closest to delivering value. Improving throughput at the constraint (getting items out of the pipeline) produces more value than improving throughput upstream (putting more items into the pipeline). Every item you deliver clears pipeline capacity; every item you start consumes it.
When This Fires
- At the start of every production work session when deciding what to work on
- When your pipeline has many items in early stages but few reaching completion
- When you feel busy but aren't shipping or delivering outputs
- Complements Set WIP limits per pipeline stage (solo: Draft=3, Review=2, Polish=2) — don't start new items until existing ones advance (WIP limits) and Move outputs forward through pipeline stages (Draft → Review → Polish → Deliver) — no skipping, no backward oscillation without explicit regression decisions (pipeline stages) with the session-level prioritization rule
Common Failure Mode
New-start addiction: always choosing to draft new items because starting is more fun than finishing. The pipeline accumulates 10 drafts, 3 items in review, 2 in polish, and 0 deliveries this week. The backlog grows while nothing ships. The downstream-first rule forces you to finish before starting.
The Protocol
(1) Before each work session, scan your pipeline board from right to left: Deliver → Polish → Review → Draft. (2) Work on the first stage (from the right) that contains items. If there's an item ready to deliver → deliver it. If Polish has items → polish them. (3) Only move to the next upstream stage when the downstream stage is empty or blocked. (4) New drafts are the last priority — only start new work when all downstream stages are clear or waiting on external input. (5) This feels counterintuitive (you want to create, not polish), but it maximizes actual output throughput by prioritizing completion over initiation.