Launch Tier Framework (Tier 1/2/3)

What it is

A classification model that sorts every launch into one of three tiers: Tier 1 (major, cross-functional, externally visible), Tier 2 (significant, single-team-led, moderate cross-functional touch), and Tier 3 (minor, routine, little or no cross-functional involvement), so the process, lead time, and headcount applied to a launch matches its actual scope rather than a default. It answers a question the other frameworks in this category assume is already settled: the 3-/7-/10-Step PMM frameworks and Complete GTM Workflow Stages describe how to run a launch once you have committed to a given level of rigour, but none tells you how much rigour a specific launch warrants. Without a tiering model, teams tend toward one of two failure modes: running the full ten-step process on a routine UI update, burning cross-functional goodwill on work with no revenue stakes, or squeezing a genuinely major launch into the same lightweight timeline as everything else. The 10-Step PMM Process already gestures at this problem in its own pitfalls, naming a "lightweight version" for smaller initiatives; this model is the formal, repeatable tool that decides which launches get that treatment and which get the full sequence, rather than leaving the call to whoever is loudest in a planning meeting.

When to use it

• You are building a quarterly launch calendar and need a shared, defensible way to decide how much process, lead time, and cross-functional resourcing each planned launch gets, before the calendar is set and teams are already committed.
• Every launch currently gets the same treatment regardless of scope. If a routine feature update and a new product line both go through the same six-week cross-functional process, the team is either wasting effort on the former or under-resourcing the latter.
• Leadership or a cross-functional partner (sales, support, legal) is asking why a minor change required so much coordination, or conversely why a major launch felt thin on external visibility and enablement.
• You are onboarding a new PMM and need a shared vocabulary for "how big is this launch" that does not depend on tribal knowledge of what past launches looked like.
• A launch's scope changes materially after it was first planned (a "minor" feature turns out to need a pricing change, or a partner integration falls through), and the team needs a quick way to re-classify it rather than muddle through with the original resourcing.

Ownership

At a scaled company with a specialised PMM team, the Head of Product Marketing or PMM lead typically owns tier assignment itself, per step 6, but a VP Marketing or CRO can veto or reclassify a launch when the tier drives resourcing decisions outside PMM's control, such as ramping a dedicated sales push or committing legal review capacity. At a solo or founding-PMM stage, pre-Series-B, the founding PMM owns tiering outright, since launch scope and cross-functional resourcing have not yet split across separate functions to negotiate between.

How to read it

Score a candidate launch against four criteria, then map the result to a tier. Revenue or strategic impact asks whether the launch opens a new market, product line, or pricing tier (high impact) versus a routine improvement to an existing one (low impact). Cross-functional dependency asks how many functions beyond PMM must be actively briefed and resourced: legal, support, sales enablement, and an executive sponsor for a major launch, versus PMM and one engineering team for a minor one. External visibility and competitive response risk asks whether the launch is likely to draw press, analyst, or competitor attention, versus passing unnoticed outside the existing customer base. Customer-facing change magnitude asks whether current customers need to be told anything beyond a release note, versus needing retraining, a migration guide, or a repositioning of what they are buying. A launch scoring high on most of these criteria is Tier 1: expect an 8 to 12 week lead time, a named executive sponsor, press or analyst briefing, and the full 10-Step PMM Process. A launch scoring high on one or two criteria, typically cross-functional dependency and customer-facing change, but low on external visibility, is Tier 2: a 3 to 4 week lead time, a lightweight version of Steps 4, 5, and 7 of the 10-Step process (positioning statement, message architecture, sales enablement), and no dedicated press motion. A launch scoring low across all four is Tier 3: release notes and, at most, an internal Slack note to support and sales, with no dedicated positioning or enablement work.

How to apply it

1. Score every planned launch against the four criteria at the point it enters the quarterly roadmap, using a simple high/medium/low rating for each rather than a precise numeric formula; the goal is a fast, consistent read, not a spreadsheet exercise.
2. Map the dominant score to a tier and attach that tier's pre-built resourcing template (a checklist of required activities, sign-offs, and a standard lead time) rather than negotiating the process from scratch for every launch.
3. Communicate the tier assignment to cross-functional stakeholders early, ideally at the same meeting the launch is added to the calendar, so sales, support, and legal know what to expect from a Tier 3 launch (essentially nothing beyond a release note) versus a Tier 1 one (a full briefing and enablement cycle).
4. Build the quarterly launch calendar around tier distribution, not just launch count. A calendar with eight "Tier 1" launches in one quarter is almost certainly mis-scored; use the distribution itself as a sense check, and expect Tier 3 to be the largest bucket in a healthy, fast-shipping product organisation.
5. Re-score a launch if its scope changes materially after the initial classification, a pricing change added to what was scored as a routine feature update, for example, rather than leaving it running on its original, now-inadequate resourcing plan.
6. Gate tier assignment through one owner (typically the PMM lead running the launch calendar), so tier is decided against the criteria in step 1, not by whichever team argues hardest for more visibility or, alternatively, tries to avoid process by underselling their launch's scope.
7. Run a short retrospective each quarter: did any Tier 3 launch actually need Tier 2 resourcing, or vice versa? Use the answer to refine the criteria's thresholds, since a fast-growing company's idea of "routine" shifts as its customer base and competitive visibility grow.