Release Blog and Launch Narrative
Parent: Writing and Documentation · researched 2026-05-29T19:22:35.560Z· 7 sources · 9 concepts · skill release-blog-and-launch-narrative
A launch is a one-shot narrative event — distinct from a landing page (steady-state conversion), an exec memo (internal alignment), or a changelog (continuous release log).
Overview
- A launch is a one-shot narrative event - distinct from a landing page (steady-state conversion), an exec memo (internal alignment), or a changelog (continuous release log). [source]
1. Four launch archetypes
- Heuristic: If you can't name the archetype in 10 seconds, the launch isn't ready. [source]
Beat 1 — Name the shift (the "why now")
- Open with a one-paragraph claim about a shift in the world. Never open with the product. Andy Raskin's whole thesis: "the old game is over; a new game is starting." [source]
Beat 2 — Stakes (the cost of the old game)
- What does the reader lose by staying with the old way? Quantify if possible. [source]
Beat 3 — The reveal
- Now - and only now - name the product and the one-line description. Apple's pattern: "Today, Apple introduced [X], a [category] that [primary benefit]." [source]
Beat 4 — Proof
- Customer logos, quotes, measurable outcomes, demo link. One outside voice is worth ten internal claims. [source]
Beat 5 — Call to action and honesty
3. The "why now" paragraph
- A working "why now" paragraph: [source]
- Names a shift that has already occurred. [source]
- Establishes the cost of operating as if the shift hadn't happened. [source]
- Creates urgency that is "you're already behind if you ignore this." [source]
- > Until recently, [old default] was the only way to [task]. But [shift A] and [shift B] have changed what's possible. Teams that adapt are [outcome]. Teams that don't are [cost]. Today we're announcing [product] to help you [verb] in this new world. [source]
- Anti-pattern: "AI is everywhere." This is a backdrop, not a why-now. It has no specific shift, no cost, no urgency. [source]
4. The cross-channel launch ladder
- Sequencing rules: [source]
- The blog post is the canonical source. Every other piece links to it. [source]
- Analyst and press briefings are under embargo. [source]
- Release notes accompany the announcement. When the blog post says "today we're launching X," the docs and the changelog must already reflect X. [source]
5. The "what's not in v1" honesty section
- > v1 deliberately ships without [X], [Y], and [Z]. We chose this scope to get [primary benefit] in your hands sooner. [X] is on the roadmap for [quarter]. If [X] or [Y] is a hard requirement for you today, [alternative path]. [source]
- What this section does: Lets engineers in evaluation mode answer "can I use this yet?" without booking a call. Pre-empts the inevitable Hacker News commenter who finds the missing feature. [source]
8. Anti-patterns
- The "we're excited to announce" opener. Cut. Open with the shift. [source]
- The "this changes everything" overclaim. [source]
- The "product-first" structure. Specs, then features, then maybe a sentence about who cares. [source]
- The hidden "what's not in v1." [source]
- The "AI/cloud/edge is everywhere" why-now. [source]
- The post that doesn't match the docs. [source]
- The four-CTA ending. If you list four CTAs the reader picks zero. [source]
9. Success criteria for a launch
References
Children
- Problem-to-Solution-to-Demo-to-CTA Arc (frontier)
- Why Now Paragraph (frontier)
- What's Not in v1 Honest-Disclosure Section (frontier)
- Embargo and Sequencing (frontier)
- Cross-Channel Launch Ladder (frontier)
- Launch-Day Comms Tree (frontier)
- Pre-Launch Teasers (frontier)
- Success Criteria for Launches (frontier)
- Relaunch Problem (frontier)
Frontier under this node: Cross-Channel Launch Ladder, Embargo and Sequencing, Launch-Day Comms Tree, Pre-Launch Teasers, Problem-to-Solution-to-Demo-to-CTA Arc, Relaunch Problem, Success Criteria for Launches, What's Not in v1 Honest-Disclosure Section, Why Now Paragraph