Default pass policies by output type: short emails = single-pass, documents = two-pass, strategic outputs = three-pass with overnight gap
Build default two-pass policies by output type—emails under five sentences single-pass, documents over one page mandatory two-pass, strategic outputs three-pass with overnight incubation—to prevent case-by-case deliberation.
Why This Is a Rule
Without default policies, every output requires a meta-decision: "How much editing does this need?" This meta-decision consumes time and is biased toward under-editing (completion momentum pushes toward "this is fine, just send it") or over-editing (perfectionism pushes toward "one more pass"). Standing policies eliminate the meta-decision by mapping output types to predetermined editing processes.
The three tiers match editing investment to output stakes and longevity (Annotate each output type with its half-life (hours/weeks/months/years) — calibrate investment in durability and polish to actual lifespan): Single-pass for ephemeral outputs (short emails, Slack messages, quick notes) — write, scan for obvious errors, send. These outputs have hours-to-days lifespan and low-to-moderate stakes. Additional passes produce diminishing returns. Two-pass for durable outputs (reports, proposals, documentation over one page) — create, then edit in a separate session (Separate creation and editing into different calendar blocks with 30+ minute gaps — defamiliarization enables fresh-eyes error detection). These have weeks-to-months lifespan and moderate-to-high stakes. The second pass catches what the first missed. Three-pass for strategic outputs (published work, board presentations, client proposals) — create, overnight gap, then three-pass edit (Three sequential editing passes for high-polish outputs: structural (organization) → line (clarity) → copy (mechanics) — never optimize all simultaneously). These have months-to-years lifespan, represent you to external audiences, and justify maximum editing investment.
The policy is a pre-decision (Pre-decisions are defaults — follow them automatically unless genuinely new information justifies override, not familiar resistance in novelty costume): you decide once which output types get which treatment, then follow the policy without re-deliberating each time. This conserves decision energy for the actual content rather than spending it on "how thoroughly should I review this?"
When This Fires
- When creating your personal editing standards for different output types
- When you notice over-editing short emails or under-editing important documents
- When a team needs shared quality standards that scale with output importance
- Complements Annotate each output type with its half-life (hours/weeks/months/years) — calibrate investment in durability and polish to actual lifespan (half-life annotation) and Three sequential editing passes for high-polish outputs: structural (organization) → line (clarity) → copy (mechanics) — never optimize all simultaneously (three-pass editing) by assigning pass counts to output categories
Common Failure Mode
Uniform editing: applying the same level of review to every output regardless of stakes. Either everything gets a quick scan (under-editing important work) or everything gets three passes (over-editing trivial work). The standing policy ensures proportional investment without per-output deliberation.
The Protocol
(1) Classify your common outputs into three tiers: Tier 1 (single-pass): Emails under 5 sentences, Slack messages, internal notes, comments. Write → quick scan → send. Tier 2 (two-pass): Documents over 1 page, external emails, meeting summaries, project updates. Write → gap (30+ min) → edit → send. Tier 3 (three-pass): Published content, strategic proposals, board materials, client deliverables. Write → overnight gap → structural/line/copy edit (Three sequential editing passes for high-polish outputs: structural (organization) → line (clarity) → copy (mechanics) — never optimize all simultaneously) → send. (2) Post this classification somewhere visible. When creating an output, identify its tier and follow the prescribed process. (3) Do not upgrade tiers (over-editing) or downgrade tiers (under-editing) based on "feel." The policy handles the decision. (4) Adjust tier boundaries based on experience: if two-pass outputs keep having quality issues, expand the tier-2 criteria or upgrade some to tier 3. (5) The goal is consistent, proportional quality investment with zero per-output deliberation.