Launch Tiering Framework Skill
Not every release deserves a full launch. This skill decides how big a launch should be, then scopes the go-to-market effort to match — so big bets get the push they deserve and minor updates don't burn the team or the audience's attention.
What This Skill Produces
- A launch tier (T1 / T2 / T3) with the scoring rationale
- The set of activities and channels appropriate to that tier
- Owners and a timeline
- A right-sized launch checklist and success metrics
Required Inputs
Ask for these if not provided:
- What's launching — the feature/product and who it's for
- Impact signals — revenue potential, strategic importance, audience reach, competitive pressure, customer demand
- Novelty — incremental improvement vs new capability vs new product
- Readiness — GA vs beta, docs, enablement, support readiness
- Constraints — team bandwidth, date pressure, dependencies
- Any house tiering definitions already in use (use them if provided)
Tiering Rubric
Score the launch on impact and novelty; the higher of the two typically sets the tier.
- T1 — Major: new product or flagship capability; strategic; broad audience; competitive stakes. Full GTM.
- T2 — Notable: meaningful new feature; matters to a segment; worth proactive comms. Moderate GTM.
- T3 — Minor: incremental improvement, fix, or narrow feature. Low-effort, in-product + notes.
If readiness lags the tier the impact warrants, flag the gap rather than downgrading silently.
Process
- Score impact and novelty using the signals provided; note the reasoning.
- Assign the tier (higher of impact/novelty), and state what would move it up or down.
- Scope activities to the tier — don't over- or under-invest.
- Assign owners and a timeline across product, PMM, content, sales, support.
- Right-size the checklist and define how you'll measure success at that tier.
Output Format
Launch Tiering — [Launch name]
Recommended tier: [T1 / T2 / T3]
Scoring
| Dimension |
Signal |
Read |
| Impact |
[revenue/strategic/reach/competitive/demand] |
[high/med/low] |
| Novelty |
[incremental / new capability / new product] |
[high/med/low] |
| Readiness |
[GA/beta · docs · enablement · support] |
[ready / gap] |
Rationale: [why this tier] · Would change if: [what flips it]
Activities for [Tier]
| Workstream |
Do |
Skip |
| Positioning/messaging |
[e.g. full narrative vs one-liner] |
[—] |
| Content |
[blog, video, launch post vs release notes only] |
[—] |
| Channels |
[press, email, social, in-app vs in-app only] |
[—] |
| Sales/CS enablement |
[kit + training vs FYI] |
[—] |
| Events |
[webinar/launch event vs none] |
[—] |
Owners & Timeline
| Workstream |
Owner |
Due |
| [Item] |
[role] |
[date] |
Launch Checklist ([tier-sized])
Success Metrics
- [Tier-appropriate: awareness/adoption/pipeline/activation]
Quality Checks
Anti-Patterns
Example Trigger Phrases
- "What launch tier should this feature be?"
- "Right-size the go-to-market for our [feature] launch"
- "Build a launch tiering framework for our team"
- "Plan T2 launch activities and owners for [product]"
1---2name: launch-tiering-framework3description: Tier a product launch (T1/T2/T3) and scope the right go-to-market effort. Use when asked to decide a launch tier, right-size launch activities, build a launch tiering framework, or plan channels and effort proportional to a launch's impact. Produces a tiering recommendation with the scoring rationale, the activities and channels for that tier, owners, and a lightweight launch checklist.4---5
6# Launch Tiering Framework Skill
7
8Not every release deserves a full launch. This skill decides how big a launch should be, then scopes the go-to-market effort to match — so big bets get the push they deserve and minor updates don't burn the team or the audience's attention.
9
10## What This Skill Produces
11
12- A launch tier (T1 / T2 / T3) with the scoring rationale
13- The set of activities and channels appropriate to that tier
14- Owners and a timeline
15- A right-sized launch checklist and success metrics
16
17## Required Inputs
18
19Ask for these if not provided:
20
21- **What's launching** — the feature/product and who it's for
22- **Impact signals** — revenue potential, strategic importance, audience reach, competitive pressure, customer demand
23- **Novelty** — incremental improvement vs new capability vs new product
24- **Readiness** — GA vs beta, docs, enablement, support readiness
25- **Constraints** — team bandwidth, date pressure, dependencies
26- **Any house tiering definitions** already in use (use them if provided)
27
28## Tiering Rubric
29
30Score the launch on impact and novelty; the higher of the two typically sets the tier.
31
32- **T1 — Major:** new product or flagship capability; strategic; broad audience; competitive stakes. Full GTM.
33- **T2 — Notable:** meaningful new feature; matters to a segment; worth proactive comms. Moderate GTM.
34- **T3 — Minor:** incremental improvement, fix, or narrow feature. Low-effort, in-product + notes.
35
36If readiness lags the tier the impact warrants, flag the gap rather than downgrading silently.
37
38## Process
39
401. **Score impact and novelty** using the signals provided; note the reasoning.
412. **Assign the tier** (higher of impact/novelty), and state what would move it up or down.
423. **Scope activities to the tier** — don't over- or under-invest.
434. **Assign owners and a timeline** across product, PMM, content, sales, support.
445. **Right-size the checklist** and define how you'll measure success at that tier.
45
46## Output Format
47
48---
49
50# Launch Tiering — [Launch name]
51
52**Recommended tier:** [T1 / T2 / T3]
53
54## Scoring
55| Dimension | Signal | Read |
56|---|---|---|
57| Impact | [revenue/strategic/reach/competitive/demand] | [high/med/low] |
58| Novelty | [incremental / new capability / new product] | [high/med/low] |
59| Readiness | [GA/beta · docs · enablement · support] | [ready / gap] |
60
61**Rationale:** [why this tier] · **Would change if:** [what flips it]
62
63## Activities for [Tier]
64| Workstream | Do | Skip |
65|---|---|---|
66| Positioning/messaging | [e.g. full narrative vs one-liner] | [—] |
67| Content | [blog, video, launch post vs release notes only] | [—] |
68| Channels | [press, email, social, in-app vs in-app only] | [—] |
69| Sales/CS enablement | [kit + training vs FYI] | [—] |
70| Events | [webinar/launch event vs none] | [—] |
71
72## Owners & Timeline
73| Workstream | Owner | Due |
74|---|---|---|
75| [Item] | [role] | [date] |
76
77## Launch Checklist ([tier-sized])
78- [ ] [Only what this tier needs]
79
80## Success Metrics
81- [Tier-appropriate: awareness/adoption/pipeline/activation]
82
83---
84
85## Quality Checks
86
87- [ ] The tier follows from explicit impact/novelty scoring
88- [ ] Activities match the tier — no full push for a T3, no silence for a T1
89- [ ] Readiness gaps are flagged, not hidden by downgrading
90- [ ] Every workstream has an owner and date
91- [ ] Success metrics fit the tier's ambition
92
93## Anti-Patterns
94
95- [ ] Do not launch everything at T1 — attention and effort are finite
96- [ ] Do not treat a strategic launch as T3 because the team is busy — flag the gap
97- [ ] Do not skip enablement on a tier that sales needs to sell
98- [ ] Do not measure a T3 with T1 metrics (or vice versa)
99- [ ] Do not ignore existing house tier definitions if provided
100
101## Example Trigger Phrases
102
103- "What launch tier should this feature be?"
104- "Right-size the go-to-market for our [feature] launch"
105- "Build a launch tiering framework for our team"
106- "Plan T2 launch activities and owners for [product]"
Mohit Aggarwal