Claim
Lowering the internal publishing bar and hitting publish while still unhappy with the draft produces more cumulative value than waiting for a draft the author can accept, because readers evaluate only what is published.
Mechanism
Authors perceive a gap between their draft and an imagined final version they are working toward. Readers have no access to that imagined version. They evaluate only what is published. The flaws the author sees are largely invisible to readers who lack the author's internal standard. Perfectionism produces unpublished drafts with zero reach and zero value. Publishing something imperfect immediately produces reach, feedback, and accumulated credibility over time. Every draft held back is a sunk cost with no upside.
The insight is not about lowering quality. It is about recognizing that the quality threshold in the author's head is calibrated incorrectly. Readers cannot perceive the delta between the published post and the better post the author imagined, because they never saw the imagined version.
Conditions
Holds when: the author has technical knowledge worth sharing; the audience is practitioners who extract value from imperfect prose; the author's internal standard is high enough that "unhappy" still clears a reasonable quality floor.
Fails when: accuracy errors could cause harm (medical, legal, safety-critical instructions); the platform has formal editorial standards requiring factual verification before publication.
Evidence
Willison's direct instruction:
"My number one tip for blogging is to lower your standards! Aim to hit publish while you are still actively unhappy with what you have written"
He supports this by noting no reader can perceive the delta between the published work and the better version the author imagined, since the author is the only one who ever saw the imagined version.
Signals
- Blog output increases after lowering the internal bar; each published post produces at least one reader who shares it
- The author stops using the phrase "I should really write that up" about topics already partially drafted
- Drafts that ship generate replies or corrections within a week; drafts that stay in a queue generate none
Counter-evidence
High-stakes public writing (formal case studies, research claims, API documentation, security advisories) requires accuracy over publication speed. Willison's advice targets personal technical blogging and practitioner essays, not reference documentation or peer-reviewed work. For writers whose internal quality bar is genuinely low, lowering it further produces unhelpful content rather than imperfect-but-valuable content.
Cross-references
- (none in current corpus directly)