Ship30for30: two-mode writing system — outlining sessions vs. output sessions
Why this is in the vault
A mechanically concrete two-mode writing-production system (capture → outline → marinate → expand → distribute) that's directly portable to a solo or small-team newsletter operation.
The core argument
Dickie Bush splits writing work into two distinct session types rather than treating "writing" as one undifferentiated activity:
- Outlining sessions (container-building): Ideas get captured continuously throughout the week into a single "Raw Ideas" note — from books, tweets, podcasts, calendar events, team meetings, personal reflections. During a dedicated morning session, he takes one raw idea and does a 10-minute brain dump into bullet points — no polish, just getting "raw material" out so it can "marinate" for at least a day before being touched again.
- Output sessions (getting ideas out the door): The night before, he pulls one already-marinated outline into its own fresh note and leaves it as the only open window, so it's the first thing he sees when he opens the computer. The next morning's first hour goes entirely to expanding that outline using a fixed menu of expansion angles: tips, stats, steps, lessons, benefits, reasons, mistakes, examples, questions, personal stories.
He doesn't fix a ratio between the two modes — some days are pure output (2-3 hours, several outlines polished), some days are pure outlining (when the day's business demands don't leave bandwidth to write). The design goal is what he calls "idea abundance": always having more outlined ideas in reserve than he can write in a day, so no session ever starts from a blank page. Finished pieces get posted across X, Threads, LinkedIn, Substack, and Instagram Reels.
The email closes with a pitch for Ship30for30's paid "AI Writing Skool" community — the technique content is real and specific, but the piece is structured as a lead magnet for that upsell.
Mapping against Ray Data Co
Most concrete connection: this is close to a spec for a "Raw Ideas" capture note feeding Sanity Check's research-brief → draft pipeline — right now research-brief and draft-review treat topic selection and drafting as adjacent skill invocations, not as a standing capture-and-marinate buffer with an enforced cooldown. Adding a persistent Raw Ideas note (fed by vault reads, X bookmarks, meeting notes) plus a mandatory ≥1-day marinate-before-expand rule would give the founder's own writing practice — and Ray's drafting on his behalf — the same "idea abundance" property Bush describes, reducing blank-page starts on Sanity Check issues.
Secondary connection: the fixed 10-angle expansion menu (tips/stats/steps/lessons/benefits/reasons/mistakes/examples/questions/personal stories) is a reusable checklist that could sit inside draft-review or research-brief as a "have we tried expanding this outline these 10 ways" prompt before an issue is marked ready.
The cross-platform posting list (X, Threads, LinkedIn, Substack, IG Reels) is structurally the same fan-out the remix skill already performs for published Sanity Check issues — no gap there, just confirmation the pattern is industry-standard.
⚠️ Sponsorship
The newsletter is self-promotional: it closes with a direct pitch for Ship30for30's own paid "AI Writing Skool" community (625+ members), positioned as the natural next step after demonstrating the outline/output technique for free. Ship30for30 is a writing-course brand, so the entire email functions as top-of-funnel content for that paid product. The technique itself reads as genuinely extractable and not watered down to force the upsell, but the framing (free value → "want a system like this? join the Skool") is the standard course-brand pattern and should be weighted accordingly — the specifics (10-minute brain dump, night-before staging, 10-angle expansion menu) are usable independent of the pitch.
Related
- [[2026-04-03-justin-welsh-newsletter-writing-process]]
- [[2026-06-11-ship30for30-parkinson-law-writing-constraint]]