What does it mean that the output pipeline?

Move outputs through stages — draft review polish deliver — systematically.

Example: You have a blog post that has been "almost done" for three weeks. You drafted it, then got distracted, then re-read it and made edits that were really re-drafting, then lost confidence, then started polishing a section that still needed structural changes. Without defined stages, you oscillated between drafting and polishing indefinitely — never knowing which activity was appropriate because you never defined the transitions. A pipeline would have told you: this post is in Stage 2 (structural review). The only valid action is evaluating the argument structure, not wordsmithing paragraphs.

Try this: Map your last five completed outputs to a four-stage pipeline: Draft, Review, Polish, Deliver. For each output, estimate how much time you spent in each stage and how many times you regressed from a later stage back to an earlier one (e.g., going from Polish back to Draft). If you find more than one regression per output on average, you have a stage-discipline problem. Design a pipeline with explicit gate criteria between stages — three concrete questions that must be answered "yes" before an output advances. Write these criteria down and tape them next to your workspace. Apply them to your next output.