Daily Reserve Writing Ritual
Write daily, build a reserve, and make tomorrow's publication automatic
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 98%
Godin separates daily writing from daily publication quality. He writes every day whether or not he uses the result, a practice he learned from Isaac Asimov. Knowing that typing will begin tomorrow changes what he notices today and what his mind works on before sleep. He also keeps posts in reserve, so illness does not break the publication cadence or force a weak same-day draft into public. The night before publication, he reviews, rewrites, or deletes. His editing rule awards points for making the post shorter but not for making it longer; once it cannot be boiled down further without becoming deliberately deceptive, it is done. Most importantly, the decision to publish daily was made years ago. Each post is not forced to prove that the entire practice should continue.
Origin
Godin says he learned daily writing from Isaac Asimov and describes the reserve-and-review ritual behind more than 8,500 daily blog posts.
Core principles
- 01Write every day whether or not the draft is used
- 02A known writing appointment changes what you notice beforehand
- 03Publish from a reserve rather than from today's emergency
- 04Editing should reward clarity and compression
- 05Cadence is a prior decision, not a daily referendum
How to run it
- 1
Precommit to the cadence
Decide the publication rhythm once rather than reconsidering the entire practice every day. Treat the cadence as the stable container for individual drafts.
Pro tip Choose a rhythm you can support with a reserve.
Watch out If streak tracking makes you feel bad, do not let software weaponize it against you.
- 2
Write regardless of use
Create something every day without requiring that every draft be published. Repetition keeps the noticing and invention process active.
Pro tip Knowing tomorrow's writing session is coming helps your mind collect material today.
- 3
Build the reserve
Keep enough usable work ahead that illness or a poor writing day does not determine what readers receive tomorrow. Separate continuity from immediate performance.
Watch out A reserve should support the practice, not become an excuse to stop creating.
- 4
Review the night before
Revisit the selected post before publication. Rewrite it, replace it, or delete it if necessary while another reserved post protects the cadence.
- 5
Edit toward the essence
Reward changes that make the post shorter and clearer. Stop when further boiling down would make it deliberately deceptive.
Pro tip Use reduction as a rule rather than waiting for a feeling of completion.
Watch out Shortening must not remove a qualification required for truth.
- 6
Publish without a referendum
Release the chosen post on schedule without requiring it to be the best thing you have written. Let the body of work, not one day's perfection, carry the promise.
In the wild
Godin writes posts in advance and reviews them the night before. Because another post is already available, getting sick does not leave the next day's publication dependent on producing something new.
→ The cadence survives ordinary disruption without lowering the editorial standard.
Godin says something is published every day because he decided that 24 years earlier, not because he reconsiders each day whether the current post is good enough.
→ The recurring decision consumes less mental energy and no single post must justify the practice.
Common mistakes
Publishing every daily draft
The practice is to write every day whether the work is used, not to remove editorial judgment from what becomes public.
Making streaks punitive
A streak that creates guilt is not helpful; the ritual should support attention and output rather than become a software-driven punishment.
Reconsidering the practice daily
Demanding that each post prove it is good enough to continue the whole cadence restores noise and resistance.
Is it for you?
Best for
Writers who want a dependable cadence and can separate daily creation from the decision to use each draft.
Not ideal for
People for whom a public streak creates harmful guilt or whose work requires infrequent long research cycles.
From the transcript
“I write blog posts in advance and then the night before I review them I rewrite them I delete them”
“you wa get points if you make it shorter you don't get points if you make it longer”
“I write blog posts every single day whether I use them or not and I learned that from Isaac azimov”
From the episode
#728: Seth Godin — Coaching Tim on Overcoming Resistance, Lessons from Isaac Asimov, Writing Secrets After 8,500+ Daily Blog Posts, The Dangers of Authenticity, Practices for Consistency, and Much More
Seth Godin