HS
Harshit Singh
Say hi
๐Ÿš€ Advanced Product Managementยทadvancedยท7 min

๐Ÿš€The Product Launch Playbook

What PMs and builders miss about launches. It's not the launch day โ€” it's the 6 weeks before and 6 weeks after.

launchexecution
Why it matters

Most launches underperform because the PM treats launch day as the goal. Real launches are 12-week orchestrated campaigns โ€” pre-launch (build anticipation), launch (coordinated push), post-launch (sustain momentum and measure).

The core idea

A great launch has three phases: 6 weeks of pre-launch (positioning, asset creation, beta), launch day (coordinated multi-channel push), 6 weeks of post-launch (driving adoption, measuring, iterating). Skipping any phase costs you 50%+ of potential impact.

The 12-week launch arc

Pre-launch (weeks -6 to -1)

  • Week -6: Lock the launch narrative. One-page positioning. Customer benefit story.
  • Week -5: Beta program with 20-50 customers. Refine based on early feedback.
  • Week -4: Asset creation. Landing page, demo video, blog post, sales deck, social posts, customer quotes.
  • Week -3: Press outreach (if applicable). Influencer pre-briefings under NDA.
  • Week -2: Sales enablement. Train the sales team. FAQ. Objection handling.
  • Week -1: Final QA. Soft-launch to a small cohort. Monitor.

Launch day

  • Coordinated push across email, social, content, sales, partnerships.
  • Press goes live (if applicable).
  • Internal celebration.
  • War-room for issue triage.

Post-launch (weeks 1-6)

  • Week 1: Daily metrics review. Quick-fix any rough edges.
  • Week 2-3: Adoption push โ€” re-engagement emails, in-product nudges, customer success outreach.
  • Week 4: First retrospective. What worked? What didn't?
  • Week 5-6: Iterate. Ship v1.1 based on learnings.

What teams skip

  • Pre-launch. Teams ship the feature and announce same day. No anticipation, no asset library, weak launch.
  • Beta program. Public launches with bugs because there was no beta filter.
  • Post-launch adoption push. Feature is launched, then ignored. Adoption stagnates at 5%.

The launch tier system

Not every launch needs a 12-week arc. Tier by impact:

  • Tier 1 (major): New product, new category, major redesign. Full 12-week arc.
  • Tier 2 (significant): New feature, expansion to new segment. 6-week arc.
  • Tier 3 (incremental): Improvements, optimizations. 1-week internal launch.

Communicate the tier to the org so people calibrate effort and attention.

The launch metric

Define one launch metric upfront. Adoption (% of eligible users who use the feature in week 1)? Revenue (incremental deals attributable)? NPS impact? Pick one, measure, learn.

Without a launch metric, you can't tell if the launch worked.

Real-world examples

Apple
Apple
The 12-week launch arc, dialed to 11

Apple's product launches are the canonical example: months of pre-launch positioning, a dramatic launch event, weeks of post-launch reviews and content. The discipline is extreme but instructive โ€” what we'd call a 12-week arc is more like a 9-month campaign for a flagship iPhone.

Notion
Notion
Launch as community event

Notion's major feature launches engage their template-maker community and power users weeks in advance. By launch day, there's already a library of community content showing how to use the feature. Adoption is driven by community, not by Notion's marketing team.

Go deeper โ€” recommended reading

Interview questions (1)

Q1
You're launching a major new feature in 6 weeks. Walk me through the plan.
executionsenior
โ–ผ

Six-week compressed plan (full 12-week arc isn't possible):

Weeks -6 to -5: Lock the launch narrative and positioning. One-page brief. Beta with 20-30 customers.

Week -4: Asset creation. Landing page, demo video, blog post, social, sales deck. Get marketing fully engaged.

Week -3: Press outreach if applicable. Sales enablement starts.

Week -2: Final QA. Soft-launch to internal team and friendlies. Train sales fully.

Week -1: Final coordinated prep. Email sequences scheduled. Social drafted. Press embargoes lifted on launch day.

Launch day: Coordinated push โ€” email, social, content, sales, partnerships. War-room for issues.

Weeks +1 to +4: Daily metrics review. In-product nudges to drive adoption. Customer success outreach. Iterate on rough edges.

I'd define one launch metric upfront โ€” likely 'adoption among target segment in week 1' โ€” and rally everyone around it. Without that metric, the launch is just noise.

Related concepts