Mandatory quality pause between "I think this is done"…
Position quality verification between 'I think this is done' and delivery as a mandatory pause point with an explicit checklist, not as optional review when time permits.
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)… (binary completion criteria) and Define both good-enough criteria and over-investment… (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.