Feature Launch Playbook

A veteran PM-leader's playbook for launching features well, not just shipping them.

Most teams conflate shipping, releasing, and launching. Shipping means engineering work is complete. Releasing means users can access it, even if it is behind a flag at 1 percent. Launching is the discipline of positioning, internal alignment, customer comms, sales enablement, support readiness, rollout strategy, monitoring, and post-launch measurement that turns "feature exists" into "feature lands."

A feature that ships without launching costs you the same engineering investment but captures a fraction of the value. Sales does not know how to sell it. Support does not know how to help with it. Customers do not notice it. The metric you said you would move does not move because nobody knows the feature is there.

This skill is the operational playbook. It assumes you have already written the spec (pm-spec-writing), prioritized it onto the roadmap (roadmap-planning), instrumented it (product-analytics-setup), and possibly tested it (experiment-design). The launch is the next discipline: how to actually get the feature in front of the right users, with the right context, in a way that lets you measure whether it worked.

When to use this skill: planning a launch (any size, any segment), auditing an existing launch process, fixing the "we shipped it but the metric did not move" problem, or building a launch checklist for the team.

What this skill is for

This skill spans the operational launch discipline. It composes with the rest of the Product skill suite.

• pm-spec-writing defines the launch hypotheses; this skill validates them.
• roadmap-planning provides the launch context (what came before, what comes next).
• product-analytics-setup is the instrumentation prerequisite; without it you cannot measure the launch.
• experiment-design and data-warehouse-experimentation provide the methodology for testing whether the launch worked.
• feature-flagging provides the rollout infrastructure this skill depends on.

This skill does not cover pricing decisions, brand campaigns, or full GTM strategy. Those need a marketing team partner; this is the PM operational playbook for the engineering and product side.

The audience is broad: every PM ships features, every PM has launched poorly at least once, every PM benefits from a checklist that stops the worst failure modes from recurring. The voice is veteran PM-leader to PM. Specific, opinionated, honest about what discipline matters at what stage.

Ship vs release vs launch

The keystone distinction. Three definitions.

Shipping means engineering completes the work. Code is on production. No users can access it yet, or only internal users via a flag. The PR is merged and deployed.

Releasing means users can access it. Could be 1 percent rollout, could be 100 percent. The feature is "live" in some technical sense. The flag is on for at least one user.

Launching means positioning, internal alignment, customer comms, sales enablement, support readiness, rollout strategy, monitoring, and post-launch measurement are all in flight. The feature has been introduced to the people who would benefit from it, with the context they need to use it.

The pathology. PMs report "we shipped feature X" when what happened is engineering completed the work. The feature might be released to 1 percent of users with no announcement, no documentation, no sales enablement, no measurement plan. From a value-capture perspective, that is an unlaunched feature.

The discipline. Use precise vocabulary. "Engineering shipped on Tuesday. We are releasing to 25 percent on Thursday. We are launching publicly next month." The vocabulary forces honest accounting of what has and has not happened.

Most "feature failed" diagnoses turn out to be "feature was unlaunched." This skill is structured around the launch dimension because that is where most teams under-invest.

Launch tiers

Not every feature needs the full playbook. Match the work to the feature.

Tier 1 (full launch). Net-new product, major feature reshaping the product narrative, pricing change, breaking change. Full playbook: positioning, all comms channels, sales enablement, customer success briefing, dedicated post-launch measurement, executive announcement.

Tier 2 (focused launch). Meaningful improvement that materially affects user value or competitive positioning. Subset of the playbook: in-app comms, blog post or release note, support readiness, rollout strategy, post-launch measurement.

Tier 3 (release note). Incremental improvement, bug fix made positive, polish. Minimal: changelog entry, release note, light monitoring.

The trap on either side.

• Treating every release as Tier 1 produces comms fatigue. Customers tune out the announcement firehose; your real Tier 1 launches lose signal in the noise.
• Treating every release as Tier 3 produces unlaunched features. The feature ships, the metric does not move, the team concludes "users do not want this" when the actual cause is "users were not told."

Match the tier to the feature. This skill primarily covers Tier 1 and Tier 2. Tier 3 is mostly the changelog discipline; the launch playbook applies but compressed to the changelog entry plus light monitoring.

Detail in references/launch-tier-decision.md.

Pre-launch: positioning

Positioning answers: who is this for, what problem does it solve, why now, and what is the user-visible promise.

The positioning canvas. One page, filled out before any comms drafting.

• Target user. Segment, role, jobs-to-be-done. Specific enough that a sales rep could describe the customer profile in one sentence.
• Problem it solves. Specifically, in user words. Not "we improve productivity"; instead "the customer support manager who needs to triage 200 tickets a day cannot tell which are urgent without opening each one."
• Current alternative. What users do today without this. The status quo is the real competition.
• User-visible promise. One sentence. The promise the user will hear when they encounter the feature in the wild.
• Proof points. Three to five specific capabilities or outcomes. Concrete, not adjectives.
• Anti-positioning. What this is NOT, what it does not try to do. Prevents over-promising.

The most common positioning failure is a vague target user. "It is for PMs" is not a target. "It is for B2B SaaS PMs at companies with 50 to 500 customers who need to coordinate roadmap discussions across engineering and customer success" is a target. The specificity is what lets sales, marketing, and support speak the same language about who this is for.

Detail in references/positioning-canvas.md.

Pre-launch: internal alignment

Stakeholders who need to know before launch.

• Engineering leadership. Capacity for follow-ups, support escalations, post-launch fixes.
• Sales leadership. Revenue forecast updates, deal coaching, pipeline impact.
• Customer success leadership. Proactive customer notifications, deal saves at risk, expansion conversations.
• Marketing leadership. Paid spend coordination, blog calendar, social timing.
• Support leadership. Training, FAQ, escalation paths.
• Executive sponsor. Visibility, public messaging, investor or board reporting.

The discipline. A single internal launch brief, distributed two to four weeks before launch (Tier 1) or one week before (Tier 2). The brief contains a one-page summary, an FAQ, a decision log of choices already made, and the launch calendar. The brief should answer "what do I need to do differently because of this launch."

The most common internal alignment failure: launching without sales knowing. Sales finds out from a customer asking about it. Trust erodes for the next launch. The fix is the launch brief plus a sal