Launches as a repeatable process
Most companies ship far more often than they launch. A product team may release improvements every week, and only a handful of those releases deserve the market's attention. The trouble starts when there is no agreed way to decide which ones those are. Every product manager believes their release matters, every release gets an announcement, and the audience learns to ignore all of them. Or the opposite happens: nothing is announced properly, and a significant capability ships with a line in the changelog.
A repeatable process solves both problems. It gives the company a shared vocabulary for how big a launch is, a template for what has to be decided, a list of who does what, and a standard review afterwards. The process is boring by design. Its value is that the thinking happens once, in the template, rather than every time a release approaches, and that the people involved know what is expected of them without a fresh negotiation.
The Product Marketing Alliance treats launch management as one of the core responsibilities of the role, and in most companies product marketing is the natural owner because it already sits between the product team that ships and the marketing and sales teams that take the release to market. Owning the process does not mean doing all the work. It means running the plan, holding the dates and making sure nothing important is forgotten.
This section covers launches of products and features by an existing business. Taking an entirely new business or product line to market, with the choice of market, channel and commercial model that involves, is a broader question covered by the go-to-market guide. The glossary defines that wider set of choices as a go-to-market strategyThe plan for how a product or offer reaches and wins its target customers.. The wider product marketing hub shows how launches sit alongside positioning and enablement.
Tiers, plan, readiness, measurement
Each part of a launch process answers a different question.
| Part | The question it answers | Main output | Covered in |
|---|---|---|---|
| Tiering | How much effort does this release deserve? | A tier, agreed with product and marketing leadership | Launch planning and tiers, Running launch intake |
| Planning | What are we trying to change, for whom, with what message and through which channels? | A one-page launch plan and a bill of materials | Launch planning and tiers |
| Readiness | Will sales, support and the product itself be ready on the day? | A readiness check and an internal briefing | This hub, below |
| Measurement | Did the launch change what it was meant to change? | Launch measures by tier and a post-launch review | Measuring launch success |
The parts depend on each other in order. The tier sets the scale of the plan; the plan sets what readiness has to cover; and the goals written into the plan are what measurement reads. A launch measured against goals that were never written down will always look like a success to the people who ran it, which is why the plan comes before anything is produced.
The core guides
Launch planning and launch tiers covers the work before a launch: how to tier releases by impact so that effort matches importance, how to build a plan from goals through audiences and message to channels, who owns which parts, what goes into the bill of materials, and how the timeline runs from pre-launch preparation through launch day to the follow-up. It uses familiar planning frames such as RACE and AIDA to make sure the plan covers the whole path from ReachUnique people who saw an ad. to action rather than stopping at the announcement.
Measuring launch success covers the work after: which KPIA metric tied directly to an objective. measures suit each launch tier, how to read leading signals such as awareness, traffic and demand, how adoption and activation show whether the release is being used, how to estimate the launch's influence on pipeline and revenue without overclaiming, and how to run a post-launch review that improves the next launch.
Read the core guides in that order. Measurement is only as good as the goals the plan set, and planning improves when the team has seen how past launches were judged.
Further guides
Further guides cover the routine that brings releases to product marketing, the launch most releases get, the customers who see a release first, the release that takes something away and the release that reaches customers in stages:
- Running launch intake with product management — a tutorial for an intake form for each release, a regular review that proposes tiers and a launch calendar both teams trust.
- Writing release notes and a changelog — a tutorial for notes customers read: who each note is for, a structure that leads with the change, honest claims and where notes go.
- Running a beta or early-access programme — a tutorial for who to invite, what participants are promised, gathering feedback and proof, and graduating to launch.
- Retiring a feature or product — telling customers: who relies on it, the alternative, a phased timeline, messages by impact and every claim that must change.
- Launching a feature that rolls out gradually — mapping who has it when, choosing when to announce, messages while others wait, sales and support with mixed availability, adoption among those who have it and a paused rollout.
Internal readiness and the sales handover
The most common launch failure is not a weak campaign. It is a customer asking about the new capability and a salesperson or support agent knowing less than the customer does. Internal readiness means that everyone who will be asked about the launch can answer before the market hears of it.
Readiness has three strands. Product readiness confirms the release is genuinely available to the people the launch addresses, in the regions and plans the messaging claims, with documentation published. Support readiness gives the support team the release notesNotes published with a product release telling the people who use it what changed, who has it and from when, written for users, not as ticket titles., the likely questions and a route to escalate what they cannot answer. Sales readiness is the largest strand: a briefing that explains who the release is for, what problem it solves, how to talk about it, how it changes the competitive picture and which existing customers to approach. For larger launches the briefing becomes a training session with updated content, and the sales enablement hub covers how that content is built. Where selected customers use the release before launch, the beta programme tutorial covers what they are promised, how their feedback and proof are gathered, and how the evidence reaches the launch plan.
The handover should happen early enough that sales can rehearse, and late enough that the release is not still changing. Most teams settle on a briefing shortly before launch, followed by a short check-in after the first customer conversations to collect questions the briefing missed. A readiness review a few days before launch, with an explicit go or no-go decision, catches the gaps while there is still time to fix them or move the date.
Launch timing and channels in brief
Timing has two parts: the date, and the sequence around it. The date should avoid clashes with the company's other launches, major industry events where the announcement would be lost, and holiday periods when the audience is absent, unless one of those is the reason to launch. The sequence usually runs from existing customers and internal teams first, through press, analysts and partners where relevant, to the wider market, so that the people closest to the company are never the last to hear.
Channels follow the tier and the audience. A minor release may need only an in-product message, a changelog entry and a note to customer-facing staff. A major launch adds email to customers and prospects, a page on the website, sales outreach, social and paid media, and possibly press and events. The mix should follow where the target audience is in the FunnelModel of the customer journey stages.: existing customers need to know how to use the new capability, prospects need to know why it matters. Before anything goes live, run it through the campaign launch QA checklist so that broken links, missing tracking and inconsistent messages are caught before the audience finds them. Afterwards, judge launch emails on clicks and on adoption of the feature rather than on open rateShare of delivered emails recorded as opened., which mail privacy features inflate.
A field-service software company introduces launch tiers
Copperleaf, which sells job-scheduling software to plumbing and heating firms, announced 26 releases in a year, each with an email and a blog post. Email open rates for release announcements fell from 41% to 19% over the year, and sales said customers asked about features that had been announced months earlier. The product marketer introduced three tiers: two releases a year would get full launches, roughly one a month would get a feature launch with email and in-product messaging, and the rest would appear only in the changelog. In the following year, announcement open rates recovered to 37%, and support tickets asking how to use newly released features fell by a third.
Common launch problems
| Problem | Usual cause | Guide |
|---|---|---|
| Every release gets the same announcement and none are noticed | No launch tiers | Launch planning and tiers |
| Launch day arrives and assets are missing | No bill of materials or owners | Launch planning and tiers |
| Sales hears about the launch from customers | No internal readiness step | This hub, under internal readiness; Running launch intake |
| Nobody can say whether the launch worked | Goals not written into the plan | Measuring launch success |
| Lots of attention, little use of the new feature | Awareness measured, adoption ignored | Measuring launch success |
| A significant capability ships as one line in the changelog | Release notes treated as the launch; no tier decided | Writing release notes and a changelog, Launch planning and tiers |
| Customers read about a new feature they cannot find in their account | Announced to everyone while it is still rolling out in stages | Launching a feature that rolls out gradually |
| Customers find out a feature is going when it disappears | Removal decided without the evidence of who relies on it; one notice for everyone | Retiring a feature or product |
| Broken links and missing tracking on launch day | No pre-launch QA | Campaign launch QA checklist |
| The launch is really a new market entry | Go-to-market decisions treated as launch tasks | Go-to-market guide |
