Release Blog and Launch Narrative
Parent: Writing and Documentation · Published reference · snapshot 2026-09-08 · skill content-and-marketing-writing/references/release-blog-and-launch-narrative.md
↓ Facts as markdownall context files
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).
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
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). [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#overview]
1. Four launch archetypes
- Heuristic: If you can't name the archetype in 10 seconds, the launch isn't ready. [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#1-four-launch-archetypes]
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." [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#beat-1-name-the-shift-the-why-now]
Beat 2 — Stakes (the cost of the old game)
- What does the reader lose by staying with the old way? Quantify if possible. [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#beat-2-stakes-the-cost-of-the-old-game]
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]." [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#beat-3-the-reveal]
Beat 4 — Proof
- Customer logos, quotes, measurable outcomes, demo link. One outside voice is worth ten internal claims. [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#beat-4-proof]
Beat 5 — Call to action and honesty
- Clear CTA - one primary CTA, one secondary at most. [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#beat-5-call-to-action-and-honesty]
- What's not in v1 - the honest-disclosure section. [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#beat-5-call-to-action-and-honesty]
3. The "why now" paragraph
- A working "why now" paragraph: [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#3-the-why-now-paragraph]
- Names a shift that has already occurred. [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#3-the-why-now-paragraph]
- Establishes the cost of operating as if the shift hadn't happened. [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#3-the-why-now-paragraph]
- Creates urgency that is "you're already behind if you ignore this." [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#3-the-why-now-paragraph]
- Template: > 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. [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#3-the-why-now-paragraph]
- Anti-pattern: "AI is everywhere." This is a backdrop, not a why-now. It has no specific shift, no cost, no urgency. [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#3-the-why-now-paragraph]
4. The cross-channel launch ladder
- Sequencing rules: [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#4-the-cross-channel-launch-ladder]
- The blog post is the canonical source. Every other piece links to it. [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#4-the-cross-channel-launch-ladder]
- Analyst and press briefings are under embargo. [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#4-the-cross-channel-launch-ladder]
- Release notes accompany the announcement. When the blog post says "today we're launching X," the docs and the changelog must already reflect X. [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#4-the-cross-channel-launch-ladder]
5. The "what's not in v1" honesty section
- Template: > 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]. [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#5-the-whats-not-in-v1-honesty-section]
- 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. [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#5-the-whats-not-in-v1-honesty-section]
8. Anti-patterns
- The "we're excited to announce" opener. Cut. Open with the shift. [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#8-anti-patterns]
- The "this changes everything" overclaim. [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#8-anti-patterns]
- The "product-first" structure. Specs, then features, then maybe a sentence about who cares. [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#8-anti-patterns]
- The hidden "what's not in v1." [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#8-anti-patterns]
- The "AI/cloud/edge is everywhere" why-now. [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#8-anti-patterns]
- The post that doesn't match the docs. [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#8-anti-patterns]
- The four-CTA ending. If you list four CTAs the reader picks zero. [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#8-anti-patterns]
9. Success criteria for a launch
- Define before launch day. Sample tiers: [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#9-success-criteria-for-a-launch]
- Unique pageviews on the blog post in week 1 [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#9-success-criteria-for-a-launch]
- Hacker News front page [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#9-success-criteria-for-a-launch]
- Signups attributable to launch [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#9-success-criteria-for-a-launch]
- New-product activation rate in week 1, week 4 [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#9-success-criteria-for-a-launch]
References
- Andy Raskin, "The Greatest Sales Deck I've Ever Seen" (Medium / Mission.org, 2016) [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#references]
- Apple Newsroom (apple.com/newsroom) [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#references]
- Linear changelog (linear.app/changelog) [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#references]
- Stripe Blog launches (stripe.com/blog) [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#references]
- Lenny Rachitsky, lennysnewsletter.com [archived source: https://llms-explorer.com/sources/mdb-context-hub/release-blog-and-launch-narrative/#references]
Where this helps
- Announcing a new product or major feature where the writer needs to justify why now, rather than just listing what shipped. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Coordinating a launch across multiple channels — blog, social, email, in-product — using a consistent narrative ladder instead of disjointed one-off announcements. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Writing an honest "what's not in v1" section to set expectations and avoid the backlash of overpromising a first release. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Choosing the right launch archetype for what's actually being announced, since the narrative beats differ between a category-creation launch and an incremental-feature launch. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Defining success criteria for a launch up front, so a marketing or product team can evaluate its actual impact afterward instead of relying on vibes. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
How to apply this
- Draft the "why now" paragraph before writing anything else — it forces articulating the market or technical shift that makes the launch timely rather than arbitrary. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Walk through the five-beat structure — name the shift, stakes, reveal, proof, call-to-action-and-honesty — as an outline before drafting full prose, checking each beat is present. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Write the "what's not in v1" section honestly and early in drafting, not as an afterthought bolted on before publishing. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Build the cross-channel launch ladder — which beats appear on the blog versus social versus email — as a single shared plan so every channel tells a consistent version of the story. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Common mistakes
- Skipping the stakes beat and jumping straight to the reveal, so readers never understand why the old way of doing things was actually costly. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Presenting proof that's purely internal claims — screenshots, adjectives — instead of external validation like customer quotes, benchmarks, or early-access results. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Omitting a "what's not in v1" section and letting users discover missing functionality themselves, which erodes trust faster than stating limitations up front would have. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Reusing the same beats and tone across every channel verbatim instead of adapting the launch ladder to each channel's actual audience and format. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Limitations
- A launch narrative works best as a one-shot event — reusing launch-style beats for routine, continuous updates that belong in a changelog dilutes both the launch's impact and the changelog's usefulness. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- The "why now" argument ages quickly; a launch blog reused or republished later without updating that framing can read as stale or confused about timing. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Success criteria defined after the fact tend to cherry-pick favorable numbers — criteria need to be set before launch to be a credible evaluation. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Honesty sections like "what's not in v1" carry real tension with launch-deadline marketing pressure, which is exactly when teams are most tempted to cut them. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
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