Mandatory quality pause between "I think this is done" and delivery — use an explicit checklist, not optional review when time permits

Why This Is a Rule

The moment between "I think this is done" and "I've delivered it" is the highest-leverage quality intervention point. Before this moment, you're still creating — quality checks interrupt flow and are resisted. After this moment, the output is in someone else's hands and errors become expensive to fix (reputational cost, rework cost, recall cost). The "done but not delivered" gap is where checking is cheap, errors are still fixable, and the creator is mentally transitioning from production to review mode.

Most people skip this pause point because of completion momentum: the relief of finishing creates urgency to deliver. "Finally done! Let me send this immediately." But the "finally done" moment is exactly when your error-detection is lowest — you've been looking at the work for hours, you're blind to its flaws, and your brain is pattern-completing what it expects to see rather than reading what's actually there. The mandatory pause breaks the momentum and forces a fresh-eyes review.

The explicit checklist converts the review from subjective ("Does this look okay?") to systematic ("Does this meet criteria 1-5?"). Subjective review during completion momentum catches maybe 30% of issues. Checklist-based review catches 80-90% because it forces attention to each quality dimension independently, regardless of how the work "feels."

When This Fires

• At the moment you believe any deliverable is complete
• When you notice a pattern of post-delivery errors that could have been caught before sending
• When designing quality processes for recurring output types
• Complements Define completion as binary observables (draft exists) not subjective evaluations (draft is good) — clear termination prevents perfectionism spirals (binary completion criteria) and Define both good-enough criteria and over-investment thresholds for each output type — cap effort to prevent perfectionism on low-stakes work (good-enough thresholds) with the timing of verification

Common Failure Mode

Optional review: "I'll check it over if I have time." Under time pressure (which is almost always), the optional review is skipped. The mandatory nature of this pause is essential — it must be part of the delivery process, not an add-on that requires extra discipline.

The Protocol

(1) For each output type, create a pre-delivery checklist with 3-7 binary items specific to that type. Email: "Correct recipient? Attachments included? Tone appropriate? Key information present?" Report: "Data current? Charts labeled? Executive summary present? Proofread?" (2) When you reach "I think this is done," do NOT deliver. Instead, open the checklist and work through it item by item. (3) Each item gets a pass/fail. Any fail → fix before delivery. (4) The checklist should take 1-3 minutes for simple outputs and 5-10 minutes for complex ones. This is not a deep review — it's a systematic final scan. (5) After the checklist passes, deliver. The pause is a gate, not a delay — once the checklist clears, delivery is immediate.