A solo content cadence has three stages: capture, draft, ship. When all three are healthy, publishing feels effortless. When one breaks, the system feels impossible – usually because the broken stage is bleeding into the other two.
The rule that holds the cadence together: keep the three stages independent. Capture doesn’t depend on drafting. Drafting doesn’t depend on shipping. Shipping doesn’t depend on capture. Solo content systems collapse because the stages get entangled – a missed draft stops the capture flow, an over-edited piece blocks the ship slot, a stalled ship makes the writer reluctant to capture anything new. Three small habits, one each per stage, keep the entanglement from starting.
The three stages
Capture. What you notice that’s worth writing. A line from a client conversation. A small contradiction you spotted in something you read. A question you keep getting in your inbox. The stage’s job is to record these the moment they arrive – not to evaluate them, not to draft from them, not to decide whether they’re ideas yet. A good capture habit is fast, low-friction, and indiscriminate. The point isn’t to be selective. The point is to not lose anything that might be worth writing.
Draft. What you do when you sit down to actually write. Pick a captured fragment. Expand it. Pull it apart. Let it become an article. The stage’s job is to produce a draft that’s complete enough to read – not polished, not formatted, not edited. Anne Lamott’s case for “shitty first drafts” is the canonical defense of this stage: the draft’s job is to exist, not to be good. Good comes later.
Ship. What you do to take a draft and publish it. Final edit. Headline. Featured image. Schema, if you set up that habit. The stage’s job is to send a finished thing into the world on the schedule the cadence committed to. A good ship habit is mechanical – not creative, not optimising. By the time something hits the ship stage, the creative work is over.
Three stages. Each with a different job. Each with a different rhythm.
Why independence is the rule
The three stages run at different speeds.
Capture is continuous. You don’t sit down to do it. You do it across the week as things land.
Drafting is intentional. You schedule it. It happens in blocks. A draft block produces one article, or a substantial chunk of one. The block has a start and an end.
Shipping is rhythmic. It happens on the publish day. The same day every week, or close to it. A shipping session is mostly mechanical work performed at a fixed cadence.
When you let these speeds bleed together, the slowest one drags the others down. A perfectionist drafter slows the ship cadence. A blocked drafter stops the capture flow because new ideas have nowhere to go. A delayed shipper makes drafting feel pointless because nothing is shipping anyway. The cascade is what kills solo content systems.
The independence rule prevents the cascade. Each stage gets to run at its own speed, regardless of what the other two are doing.
How the stages fail (and how independence catches it)
Each stage has a characteristic failure mode. The independence rule catches each one.
Capture fails through over-evaluation. The instinct is to filter ideas as they arrive – “this is good, this isn’t, this is half-formed.” The filter belongs at the draft stage, not capture. When you evaluate at capture, you lose most of what would have been worth writing later, and you slow the capture habit until it stops. The fix: capture without judgment. Sort later.
Draft fails through premature editing. The instinct is to edit the first paragraph until it’s perfect before writing the second. The edit belongs at the ship stage, not draft. When you edit at draft, you produce one or two perfect paragraphs and a dead article. The fix: write to a finished draft before fixing anything. The draft can be ugly. The ship version is where it gets cleaned up.
Ship fails through scope creep. The instinct is to “just add one more thing” before publishing. The thing belongs in the next draft, not this one. When you let drafting bleed into shipping, the publish slot keeps getting delayed because the article is “almost ready” forever. The fix: when something hits the ship stage, the article is done. Improvements go into the next piece.
Each failure mode is a stage trying to do another stage’s job. The independence rule names the job each stage has and refuses the others.
Setting up the system
The system is small enough to build in a weekend.
For capture, pick one place to put things. Notes app, paper notebook, voice memo – the format doesn’t matter, the singleness does. Two capture surfaces is the same as zero, because nothing actually accumulates in either. Mine is a single Drafts app file titled “ideas.” Everything that might be worth writing goes there, raw.
For drafting, pick a block in the week. Block length matters less than block reliability – the same time each week, defended against other commitments. Mine is Tuesday morning, 90 minutes. The block’s only output is a draft I’d be willing to ship if I had to. Polished is not the goal. Done is.
For shipping, pick a day. Same day each week. Decide once and stop deciding. Mine is Thursday. Thursday morning is the ship session – the draft from Tuesday gets the final edit, the headline, the image, and goes live. If a Thursday catches me without a draft, I ship the one I’d previously deferred. The slot doesn’t move.
That’s the whole system. Three habits, three rhythms, one rule.
The next piece in this series covers the two cases where this system bends without breaking. The piece after that – the engine that runs on three decisions per week – goes deeper into the decision layer that sits above the three blocks.
The rest of the Content Systems archive lives at the Content Systems category. The Solo Operating System frame that sits underneath this – including the question of cadence at the system level – is the prior piece in the cluster.
FAQ
What if I’m bad at one of the three stages?
Pick the stage you’re weakest at and run it for two weeks with the smallest possible commitment. Capture once a day. Draft once a week. Ship once. Build the habit before scaling the volume. The independence rule means a weak stage doesn’t break the system as long as the other two keep running.
Should the three stages happen in the same place?
No. Most solo founders set up one app to do all three and then wonder why nothing flows. Capture and draft can share a tool. Draft and ship can share a tool. All three in one place creates friction. Separate the surfaces. The separation is most of the system.
How long should the draft block be?
90 minutes is the working answer for most people writing 1,200–1,800-word essays. Shorter pieces fit 45-minute blocks. Longer pieces need 2-hour blocks or two consecutive 90-minute blocks on different days. The right length is the longest stretch you can hold focused work without quality degrading.
What if I don’t have time for all three?
Then you have time for capture. Capture takes 30 seconds at a time. Drafting and shipping can wait. A system with healthy capture and no drafting is still a system – the drafting habit can rebuild later, and the capture file will be ready when it does.
How do I know if the stages are independent enough?
If a missed draft block stops your capture habit, the stages aren’t independent. If a delayed ship slot stops your drafting block, the stages aren’t independent. Each stage should be running on its own rhythm even when the others stall.
Three habits, one cadence
The cadence isn’t a discipline. It’s three small habits arranged in a way that lets each one run at its own speed.
Capture as things arrive. Draft on the block. Ship on the day. When you keep the three stages from doing each other’s jobs, the cadence holds. When you don’t, the cadence breaks – not because the work is hard, but because the stages are eating each other.
Three stacks, separated by hand.
The Solo Content System. A printable framework for the three-stage cadence: capture habit, draft block, ship day. Same logic as this article, in one simple guide you can stick beside your keyboard. Download the guide →
