Pre-produce 3-5 buffer outputs before launching any public…

When This Fires

• Before launching any recurring public output (newsletter, blog, podcast, social series)
• When an existing cadence has no buffer and you're one bad week from breaking it
• When planning ahead for known disruptions (vacation, busy season, life events)
• Complements When one routine element fails, execute minimum viable… (graceful degradation for routines) with the output-specific buffer strategy

Common Failure Mode

Launch-day-one production: announcing a weekly newsletter and writing the first issue the day before the first send date. No buffer exists. The first disruption — a busy week, a creative block, a family obligation — breaks the cadence immediately. The newsletter goes silent after 3 issues and never recovers.

The Protocol

(1) Before announcing or launching any public cadence, produce 3-5 complete outputs. These are your buffer. (2) When the cadence launches, publish from the buffer while continuing to produce new outputs. As you produce, the buffer replenishes (or grows). (3) When a disruption prevents production for a week, publish from the buffer. No gap is visible to the audience. (4) After the disruption, rebuild the buffer to 3-5 before relaxing production intensity. (5) Monitor buffer level: 5+ outputs → safe, can absorb extended disruptions. 3-4 outputs → adequate, maintain production pace. 1-2 outputs → warning, prioritize buffer rebuilding. 0 outputs → emergency, one disruption breaks the chain. Produce 2-3 immediately before any other work.