There is a familiar arc for founders who start writing. Five articles in the first week. Two in the second. Silence from the third, and two months later nothing remains but the guilt of “I should start again”.
The problem is not laziness. It is starting at a pace nobody could sustain. Search traffic needs time to accumulate, and when publishing stops what had been accumulating fades with it.
Why bursts collapse
Bursts turn writing into an event. Events need preparation, and any week without preparation time gets skipped entirely. Rhythm turns writing into a habit, and habits still run at half speed in a bad week.
Split one article into four pieces
“Write an article” looks like one large task, but it is really four different jobs. Split them and thirty minutes at a time is enough to produce one article a week.
Picking a topic means taking one line off the list you already built: five minutes. Building the skeleton is writing subheadings and nothing else. Drafting means going from start to finish without editing — begin polishing sentences here and the draft never ends. Polishing handles the prose, the internal links and the title and description together.
Attach the pieces to weekdays and the vague weight of “I need to write something” becomes the concrete task of “today I only do the skeleton”.
Build up stock
What actually protects a rhythm is not willpower but stock. Start with two unpublished drafts in hand and publishing survives the week a trip gets booked or the work piles up.
One good approach is to spend the first month writing without publishing at all. After that, hold the buffer by publishing one and writing one. The moment stock hits zero, rhythm becomes a contest of willpower — and willpower eventually loses.
How to come back after stopping
Stopping is not failure; it is scheduled. What matters is deciding the way back in advance. When you return, do the easiest thing available — not a new article, but adding internal links to a published one, or refreshing a single paragraph.
A small task restarts the rhythm. The thought that “two months off means I owe everyone something substantial” is what delays the return longest.
Turning work into a repeatable routine is covered further in the development workflow archive, and how we split our own delivery into stages is published on the process page. For the article skeleton itself, see part three.
Next part
Once publishing continues, the next question arrives: which of these articles is actually working? The next part covers the three metrics that answer it.