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-framework-23description: 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---56# Launch Tiering Framework Skill78Not 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.910## What This Skill Produces1112- A launch tier (T1 / T2 / T3) with the scoring rationale13- The set of activities and channels appropriate to that tier14- Owners and a timeline15- A right-sized launch checklist and success metrics1617## Required Inputs1819Ask for these if not provided:2021- **What's launching** — the feature/product and who it's for22- **Impact signals** — revenue potential, strategic importance, audience reach, competitive pressure, customer demand23- **Novelty** — incremental improvement vs new capability vs new product24- **Readiness** — GA vs beta, docs, enablement, support readiness25- **Constraints** — team bandwidth, date pressure, dependencies26- **Any house tiering definitions** already in use (use them if provided)2728## Tiering Rubric2930Score the launch on impact and novelty; the higher of the two typically sets the tier.3132- **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.3536If readiness lags the tier the impact warrants, flag the gap rather than downgrading silently.3738## Process39401. **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.4546## Output Format4748---4950# Launch Tiering — [Launch name]5152**Recommended tier:** [T1 / T2 / T3]5354## Scoring55| 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] |6061**Rationale:** [why this tier] · **Would change if:** [what flips it]6263## 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] | [—] |7172## Owners & Timeline73| Workstream | Owner | Due |74|---|---|---|75| [Item] | [role] | [date] |7677## Launch Checklist ([tier-sized])78- [ ] [Only what this tier needs]7980## Success Metrics81- [Tier-appropriate: awareness/adoption/pipeline/activation]8283---8485## Quality Checks8687- [ ] The tier follows from explicit impact/novelty scoring88- [ ] Activities match the tier — no full push for a T3, no silence for a T189- [ ] Readiness gaps are flagged, not hidden by downgrading90- [ ] Every workstream has an owner and date91- [ ] Success metrics fit the tier's ambition9293## Anti-Patterns9495- [ ] Do not launch everything at T1 — attention and effort are finite96- [ ] Do not treat a strategic launch as T3 because the team is busy — flag the gap97- [ ] Do not skip enablement on a tier that sales needs to sell98- [ ] Do not measure a T3 with T1 metrics (or vice versa)99- [ ] Do not ignore existing house tier definitions if provided100101## Example Trigger Phrases102103- "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