product-launch-playbook

Product Launch Playbook

Overview

The Product Launch Playbook skill guides product managers through all phases of launching features or products, from pre-launch planning through post-launch analysis. It ensures coordinated execution across engineering, marketing, sales, and support teams.

When to Use This Skill

• Planning major feature launches
• Launching new product or product line
• Planning beta testing programs
• Executing go-to-market strategies
• Communicating with stakeholders
• Managing launch day operations
• Analyzing post-launch performance
• Planning customer success initiatives

Launch Framework Overview

Launch Timeline (8-12 weeks):

1. Pre-Launch Phase (4-5 weeks) - Strategy, assets, readiness
2. Beta Phase (2-3 weeks) - Customer validation, feedback
3. Launch Phase (1-2 weeks) - Coordinated release
4. Post-Launch Phase (4+ weeks) - Support, iteration, analysis

Pre-Launch Planning (4-5 weeks before)

Launch Steering Committee Formation

Core team members:

• Product Manager (Owner)
• Engineering Lead
• Design Lead
• Marketing Lead
• Sales Lead
• Support/Customer Success Lead
• Analytics Owner

Responsibilities:

• Weekly launch status meetings
• Escalation authority for decisions
• Budget and resource approval
• Cross-functional alignment

Go-to-Market (GTM) Strategy

Target Customer Definition:

• Primary segment: [Specific customer profile]
• Company size, industry, use case
• How they will benefit most
• Why they should care vs. competitors

• Secondary segment: [Broader customer profile]

Value Proposition:

• Core benefit: [One sentence, customer-focused]
• Supporting benefits: [3-4 specific advantages]
• Differentiation: [vs. competition or status quo]

Positioning Statement: "For [customer segment], [product/feature] is a [category] that [solves problem]. Unlike [alternative], our [feature] [key differentiator]."

Example: "For remote engineering teams, Real-time Project Sync is a collaboration system that eliminates status update meetings. Unlike email and Slack, our feature creates a persistent, queryable project state that updates in real-time."

Messaging Framework

Message Hierarchy:

Core Message (One-liner)

• "Eliminate status meetings with real-time project visibility"

Supporting Messages:

• "Keep everyone in sync without synchronous meetings"
• "Cut meeting time by 50% while improving alignment"
• "Build an asynchronous-first team"
• "Know project status instantly from anywhere"

Audience-Specific Messages:

For Engineering Leads:

• Focus: Productivity gains, tool consolidation
• Message: "Stop switching between tools to get status"

For Managers:

• Focus: Team alignment, visibility
• Message: "See what your team is doing without asking"

For C-suite:

• Focus: ROI, efficiency
• Message: "Reduce meeting overhead, improve productivity"

For Individual Contributors:

• Focus: Ease of use, personal efficiency
• Message: "Get work done faster with better visibility"

Channel and Timing Strategy

Launch channels:

• Email (existing customers): Week 1
• In-product (feature flag, highlight): Week 1
• Sales team: Week 1 (for new sales)
• Marketing: Blog post, social media, Week 1-2
• Press/media: Day 1 (coordinated announcement)
• Community/events: Weeks 1-2

Timing consideration:

• Avoid holidays, competitor launches, industry conferences
• Consider customer business cycles
• Target day of week: Tuesday-Thursday (engagement)
• Target time: 9-11 AM (when users online)

Beta Testing Program (2-3 weeks)

Beta Participant Selection

Participant tiers:

Tier 1: Lighthouse customers (5-10)

• Most enthusiastic early adopters
• Willing to provide detailed feedback
• Access to decision-makers for follow-ups
• Commitment: Daily testing, weekly feedback calls

Tier 2: Early adopter customers (20-30)

• Strong product advocates
• Regular users of current features
• Engaged customer community
• Commitment: 3-4x per week testing

Tier 3: Interested customers (50-100)

• Curious about new features
• Broad user base for feedback
• Less intensive commitment
• Commitment: Try at least once, optional feedback

Selection criteria:

• Existing customer (for product features)
• Active/engaged users
• Willingness to participate
• Geographic/segment diversity
• Mix of power users and new users

Beta Program Communication

Beta Kickoff Email:

Subject: "You're Invited to Beta Test [Feature Name]"

"Hi [Name],

We're excited to invite you to our private beta for [Feature Name] launching [date].

What's it about: [2-3 sentence description of feature and benefit]

Why we're asking you: You're one of our most engaged customers, and your feedback will help us make this feature amazing.

What we need:

• Try [feature] over the next 2 weeks
• Share feedback via [form/survey/call]
• Report any bugs or issues
• Expected time commitment: 30 minutes

What's in it for you:

• Early access to the feature
• Direct influence on our roadmap
• [Early bird pricing/exclusive benefits]

Get started:

1. Access beta at [link]
2. Complete [onboarding/setup]
3. Share feedback via [link]

Have questions? Reply to this email.

Thanks for being an awesome customer! [PM name]"

Beta Feedback Collection

Feedback form structure:

1. Feature Usability (Rate 1-5)
2. "How easy was it to learn?"
3. "Was the workflow intuitive?"
4. "Did it work as you expected?"

1. Value/Benefit (Rate 1-5)
2. "How useful is this feature?"
3. "How likely to use regularly?"
4. "Worth the effort to learn?"

1. Open-ended questions:
2. "What did you like most?"
3. "What was confusing?"
4. "What would make it better?"
5. "Who else should have this?"

1. Bugs and issues:
2. "Did you encounter any errors?"
3. "Did anything break or not work?"
4. "Any performance issues?"

Feedback analysis:

• Compile feedback into themes
• Calculate NPS for feature (how likely to recommend)
• Identify critical bugs vs. nice-to-haves
• Plan iterations based on feedback

Beta Iteration Plan

Response time for critical bugs: 24 hours

• Show beta participants you're responsive
• Build goodwill for launch feedback
• Demonstrate commitment to quality

Iteration cadence:

• Daily: Monitor for critical bugs, respond immediately
• 2-3x per week: Non-critical improvements
• Weekly: Gather feedback, plan iterations
• Mid-beta: Major feedback-driven improvements

Beta success criteria:

• 90%+ of participants try feature
• 70%+ would recommend (NPS 50+)
• All critical bugs fixed
• No deal-breaker feedback
• Performance within targets

Launch Week Preparation

Launch Day Checklist (1 week before)

Engineering:

• [ ] Feature code complete and merged
• [ ] All tests passing (unit, integration, e2e)
• [ ] Load testing completed, results reviewed
• [ ] Deployment runbook written and tested
• [ ] Rollback plan documented
• [ ] Monitoring and alerts configured
• [ ] Feature flags configured for gradual rollout
• [ ] Database migrations tested
• [ ] API contracts finalized and documented

Product:

• [ ] Feature documentation written (help center, in-app tooltips)
• [ ] Acceptance criteria all met
• [ ] Success metrics defined and tracked
• [ ] Launch checklist review completed
• [ ] FAQ prepared for support team
• [ ] Launch talking points finalized
• [ ] Key stakeholder communication scheduled
• [ ] Post-launch measurement plan reviewed

Design:

• [ ] UI finalized and reviewed
• [ ] Edge cases and error states designed
• [ ] Accessibility review completed (WCAG 2.1 AA)
• [ ] Mobile/responsive tested
• [ ] Help text and tooltips reviewed
• [ ] Onboarding flow finalized

Marketing:

• [ ] Blog post written and scheduled
• [ ] Email campaign created and queued
• [ ] Social media assets created
• [ ] Announcement copy finalized
• [ ] Press release prepared
• [ ] Website update