Why launches start upstream
Most launch problems that show up on launch day began months earlier, when a release was scheduled without anyone asking how much the market would care. Sales hears about a capability from a customer; a pricing change goes out as a line in the changelog; two significant launches land in the same fortnight because nobody saw both dates. The product launches hub lists sales hearing about a launch from customers among the common launch problems. Problems like these often come back to the same gap: product marketing heard about the release too late to tier it and plan for it.
The Product Marketing Alliance treats launch management as one of the core responsibilities of the product marketer, and describes tiering as one of the simplest ways to make launches repeatable. Tiering only works if every release reaches the person who tiers it. The product marketing pillar describes the settlement most teams reach with product management: a release calendar shared well ahead, with product marketing joining roadmap discussions rather than reading the output. Launch intake is how that settlement is run week to week.
Intake sits upstream of everything else. The tiers guide sets the criteria and the plan; the product launch playbook starts at a kick-off where the tier is agreed; the measuring launch success guide closes each launch with a review. Intake is what feeds the first of these with releases, in time.
Before you start
Have the tier criteria written down. Intake asks product management questions that come from those criteria, so if the tiers guide's work has not been done, do it first: what triggers each tier, and what scope each tier gets.
Agree the purpose with the head of product, not just with individual product managers. Intake asks product managers for a little work on every release, and it survives only if their manager sees why. The argument that usually works is that intake protects product's releases: a significant capability that is tiered and planned gets adopted, and one that slips out unannounced does not.
Decide where the form and the calendar will live. The best place is wherever product management already plans releases, so that filling in the form is part of scheduling a release rather than a separate chore. Keep this separate from the marketing team's own request intake, which the guide to prioritising marketing work runs as a single front door for requests to marketing; launch intake runs the other way, from product into product marketing.
The steps
Agree which releases product marketing hears about
Write the rule down with product management: every release a customer could notice goes through intake, including fixes, changed behaviour, removals and anything touching price or plans. Purely internal work that changes nothing a customer sees does not. A rule that says "tell us about the important ones" fails, because deciding what is important is the tier decision, and that is the decision intake exists to make.
Build the intake form from the tier criteria
Turn each tier criterion into a question a product manager can answer before the release ships. If a criterion is the share of customers affected, the form asks which customers, plans or segments the release affects. If a criterion is whether the release opens a new segment or revenue stream, the form asks that directly. Add the facts every plan needs: the release in one sentence, the problem it solves, the expected date and how firm it is, what it depends on, and any change to price, packaging or plans. Never add questions that introduce new criteria; if a question matters to the tier, change the criteria first. Where the answer on packaging is yes or not yet known, the guide to deciding which plans get a new feature sets out the options and the evidence for the proposal that goes to the review.
Set the review rhythm with product management
Agree a regular review where product marketing and product management go through new and changed forms together. How often depends on how often the company ships; what matters is that it is regular, short and attended by someone from product who can answer questions. Add it to an existing roadmap or planning meeting where possible, rather than creating another.
Score each release and propose a tier
At the review, score each new release against the tier criteria and propose a tier. The weighted scoring matrix, as its framework page sets out, agrees the weights before any option is scored, backs every score with evidence and treats a narrow gap as a tie to be settled by judgement rather than arithmetic. Applied to releases, the criteria are the tier triggers, the weights reflect what the company's positioning cares about, and the score supports the proposal without making it. Record the reason for each proposed tier in a sentence.
Agree who approves the tier
Write down who decides. The tiers guide suggests product marketing proposes and a small group including the product lead and a marketing leader agrees. A RACI matrix built around the tier decision gives it exactly one accountable role, as the framework requires, with product management consulted and sales, support and channel teams informed. Major-tier decisions may need an executive sponsor; say so in the matrix rather than discovering it at the review.
Put every release on one launch calendar
Every release that went through intake goes on a single launch calendar, with its tier, owner and date, whatever its tier. One calendar shows clashes that separate lists hide: two major launches in the same fortnight, a launch landing in the middle of a seasonal campaign, or a quarter with nothing for sales to talk about. Feed the major and feature launches into the company's campaign calendar, whose launch layer needs the full sequence rather than only live dates.
Set milestones relative to the launch date
For each tier, set the standard milestones as distances from launch day, as the tiers guide recommends, so that the plan survives a moved date: when the plan is opened, when messaging is final, when sales and support are briefed, when the go or no-go review happens. For a major launch, the go-to-market plan template records the first segment, the offer and the gates between phases, and staged launches can use phase-gate reviews to decide whether each phase goes ahead. A major launch is often where the company's go-to-market choices are tested, so the milestones should leave room to make them.
Re-tier when scope or date changes
A tier is a decision about a release as it was described at intake. When the description changes, look again. The usual triggers are a scope cut that removes what made the release significant, a date move that lands it beside another launch, a new segment added to the release, and any new pricing or packaging element. Ask product managers to update the form when any of these happen, and bring changed forms to the next review before the plan moves on.
Log minor and silent releases too
Minor and silent releases still go on the calendar and through intake, in a lighter form. They need a changelog entry, help documentation or a support briefing where the tier says so, and the tutorial on writing release notes and a changelog covers the note that is often a minor release's whole launch. Logging them also catches releases that were scheduled as silent but are not: a change to price, to plans or to something customers rely on is never silent, whatever the engineering effort behind it.
Review intake at each post-launch review
At each post-launch review, ask how the launch came through intake. Did product marketing hear about it in time? Was the tier right, judged by what the market did? Did the date or scope move, and was it re-tiered? The measuring launch success guide sets out the review itself. The share of releases that reached intake before their plan should have started is a useful leading indicatorA measure that moves before the business outcome it is expected to predict, paired with a lagging measure that confirms the outcome later. for the launch process; the outcome KPIsA metric tied directly to an objective. of each launch are the lagging measures. Change the form or the criteria when the reviews keep finding the same gap. Intake is one item on the post-launch reviewThe meeting that closes a launch once its measures have had time to move: goals against results, what worked, what did not, and process changes for the next. agenda, beside the launch's results against its goals.
What the intake form asks
The form is short, answerable by the product manager without a meeting, and built from the tier criteria. The questions below are a starting set; replace the tier questions with the company's own criteria.
| Question | Who answers | Why it is asked |
|---|---|---|
| What is the release, in one sentence a customer would understand? | Product manager | Gives the review a shared description and the first draft of the message |
| What problem does it solve, and for whom? | Product manager | Connects the release to a messaging pillar and a segment |
| Which customers, plans, segments or regions does it affect? | Product manager | Answers the tier criterion on reach |
| Does it open a new segment, market or revenue stream? | Product manager | Answers the tier criterion on new business |
| Does it answer a common reason for lost deals or a competitor's strength? | Product manager, with sales input | Answers the tier criterion on the competitive picture |
| Does it change price, packaging, plans or anything customers rely on? | Product manager | Flags releases that are never silent |
| Does it need customers to change how they work? | Product manager | Flags support, documentation and communication needs |
| Expected date, and how firm is it? | Product manager | Places the release on the calendar and sets the milestones |
| What does it depend on? | Product manager | Shows what could move the date |
| Proposed tier and reason | Product marketing, at the review | Records the decision and why |
| Approved tier, approver and date | Approver | Makes the decision traceable when it is revisited |
A fleet maintenance software sets up intake (illustrative)
Halvorink Fleet catches a silent pricing change
Halvorink Fleet, an invented fleet maintenance software for haulage and delivery firms, had shipped 31 releases in a year, and sales had first heard about 6 of them from customers. Product marketing agreed with the head of product that every customer-visible release would go through a form of 9 questions, built from the company's 5 tier criteria, filled in by the product manager when the release was scheduled. A review was added to the end of the fortnightly roadmap meeting. In the first quarter, 14 releases came through intake: 1 was tiered major, 3 feature, 8 minor and 2 silent. All 14 went on one calendar, with milestones counted back from each date; a major launch at 10 weeks out and a feature launch at 5 weeks out had their sales briefings in the same week, so one was moved. One release, scheduled as silent because it changed how vehicle limits were counted, answered yes to the question about price and plans: some customers would move to a higher plan. It was re-tiered as a feature launch, with a customer notice, a pricing page update and a sales briefing. At the next 3 post-launch reviews, every release had reached intake before its plan was due to start.
The intake routine feeds the plan, and the plan is where the work begins: the launch planning and tiers guide sets out the goals, roles, bill of materials and timeline that follow once a tier is agreed.
Common mistakes
- Asking only about important releases. Deciding what is important is the tier decision; every customer-visible release goes through intake.
- Product marketing filling in the form. The facts come from the people who own them, or the form records guesses.
- Questions that invent new criteria. The form asks what the tier criteria need; change the criteria deliberately, not through the form.
- A score treated as the decision. The matrix supports the proposal; the reason is written in a sentence and someone named approves it.
- Separate calendars for each team. Clashes only show on one calendar with every release on it.
- Milestones tied to calendar dates. Count them back from the launch date so the plan moves with the release.
- Tiers that never change. A scope cut, a date move, a new segment or a pricing element is a reason to look again.
- Silent releases that touch price. A change customers pay for is never silent.
